OvermindDL1

@icefoxen Does that include the mouse cursor in exclusive mode? Having an absolute position doesn't make sense for exclusive mode. Things like many games as one example will absolutely require...

That is a long-time vanilla MC bug, was not fixed in 1.8 either, unsure about after that. There was a mini-mod going around at some point that ASM'd it fixed...

Hmm ,interesting, this is a patch that could be added to DragonAPI.

For note, the dash you put in the post here is not ascii (it is indeed a UTF-8 en-dash in this case, but github 'unifies' everything to utf-8 in posts...

If you debug in sending it on the server side pre-serialization is it parsed into a rust `String` and then sent over or is it kept as a javascript string...

This would be useful, allow a swipe-back back to the central point (with perhaps a small variance allows for the other direction) to close the underlay.

To be specific, can work around it by iterating over the elements in a dom-repeat after it fills them (though can be slow), or can also use a calculated property...

Not fully tested yet, but it looks like this might also happen if a swipe is given a direction one way, but not the other (like being able to swipe...

> Also, can you reproduce that here : http://vguillou.github.io/webcomponents/swipe-action/demo/ I cannot reproduce it there, interesting, wonder if it is something due to the webcomponents website then, hrmm... Yeah still happens...

> If you can provide more information, I'd be interested! :-) I'll play around with it as I get time to see if I can figure out what is up,...