Re: [w3c/pointerlock] MovementX/Y for down and up (#15)

I made that design decision in Pointer Lock because I want to reduce the chance of application error. All movements must be delivered to mousemove events, so applications will and can handle movement there. A naive handler would duplicate handling of delta movements if browsers did also include movement data in other events such as mousedown. The absolute positions of mouse events are not at risk of these logical  errors - worst case they would perform duplicate processing. But movementX/Y is typically used in an additive way and the values would be double counted.

-- 
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/15#issuecomment-272600312