Re: [w3c/pointerlock] movementX/Y when moving out of or into an iframe (#16)

>> So if the last event (happened outside of this iframe) is far apart it does see a jump event though the first event that was delivered to this iframe might be near the boundary.

> Ok, well that's not desired,

I thought this was working as intended.  What I believe Navid is saying is that the event inside the new iframe includes all movement that occurred after the last event delivered to the previous frame (still inside the window) but never any more.  So this includes some travel that wasn't over the target frame, but still not a "big jump" with magnitude greater than that in other (non-iframe) cases.  This is exactly what the spec says, and I think what we want.

It was only his initial implementation for the touchscreen case where this wasn't working correctly IMHO.

-- 
You are receiving this because you are subscribed to this thread.
Reply to this email directly or view it on GitHub:
https://github.com/w3c/pointerlock/issues/16#issuecomment-274134453