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

> If the page doesn't see the mousemoves outside its window, the only feasible solution seems to be to compute the offsets from the last event the page knows about when the mouse comes back. The iframe case seems no different.

I think the Iframe case is fundamentally different from the window case for the following reason:
- Iframes can be used when composing an application in a way transparent to the user.  It's often not part of the user's mental model of switching applications when the mouse moves between frames.
- `mouseleave` events are not sent to the outer frame when the mouse moves into the boundaries of a containing frame.  So from the code in the outer frame's perspective, the mouse hasn't "left" at all.

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