Re: [w3c/pointerlock] movementX/Y to be double instead of long (#24)

Maybe the type is correct by there might be some sort of rounding/flooring happen for that. For example in Chrome we do that for MouseEvents for compat reasons. So even though the type is double the numbers that are exposes are long. But we thought since pointerevents are new we just expose the double version of the number.

-- 
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/24#issuecomment-392572233

Received on Monday, 28 May 2018 17:10:46 UTC