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

> 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.

Forget about my original implementation. I raised this issue when I was trying to write a [test](https://github.com/w3c/web-platform-tests/pull/4571) (for the new implementation) and realized I really cannot rely on the sum of all movementX of the events received by the inner iframe to be the width of the frame when pointer spans the whole iframe. It could be any number less or greater than the width depending on how fast/slow I go in or out of the iframe. That is why I put that <10 magnitude for that test. The jump is definitely not more that what the outer frame would see if there were no innerframe at all. But I was wondering if even that jump is desired for the innerframe or not.

-- 
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-274138030