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

@ RByers, @scheib
Why do we have movementX/Y set to zero for down and up events? I mean those events can have different coordinates from their last move events in general (isn't it the case?) and these attributes seem to be generic and capable of being set even when pointerlock is inactive.
So can we extend the definition to also have a correct value for down and up events?

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