Re: [w3c/pointerlock] movementX/Y coordinate space (#42)

Can we please get this fixed. `movementX`, `movementY`, and `movementZ` are not reliable at all without consistent units.

For consistency, CSS pixel units will be the best (a user can multiply by devicePixelRatio to convert to physical if they wish). This will align with `px` in CSS which means that mapping `movementX`, for example, to a difference in `width` or `transform` will simply.

The workaround right now is to instead never use `movement*` properties, and calculate the value directly using some math using the `client*` properties.

-- 
Reply to this email directly or view it on GitHub:
https://github.com/w3c/pointerlock/issues/42#issuecomment-1886110941
You are receiving this because you are subscribed to this thread.

Message ID: <w3c/pointerlock/issues/42/1886110941@github.com>