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

The spec requires zeros at window boundaries because the user agent can't know what the relative motion of the pointer was. However, it does know this when crossing iframe boundaries and I think we should provide the movementX/Y values. The spec doesn't address this specifically, but I think implicitly allows this fine.

However, let me know if in the code you see this to not be true, or if there's something else I'm missing.

The actual goal is that when entering iframes the movementX/Y values are usable and don't represent a large jump in value. E.g exiting an iframe at the top center, and then re-entering slowly from the right edge should show only a small leftward motion in movementX. 

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