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

Thanks @scheib, that makes it very concrete and I agree completely.  I don't see any good reason why event c would need to have movementX/Y==0 so I'd prefer we leave things as spec'd.

I think the only challenge here is that @NavidZ was trying to test events c and v in relative isolation from the other events.  I don't think that makes sense.  The only way to validate that the movement in events c and v are correct is to communicate with the parent frame somehow (so one frame or the other knows about the b-c and u-v delta).

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