- From: Mustaq Ahmed via GitHub <sysbot+gh@w3.org>
- Date: Wed, 13 Feb 2019 17:58:27 +0000
- To: public-css-archive@w3.org
Looks like the use-cases we mentioned so far can be solved through the the original point @upsuper mentioned: the content should be responsive to just the viewport. Let me add a different example that seems to need the proposed `pageZoomFactor`. [This threejs demo](https://threejs.org/examples/?q=pointer#misc_controls_pointerlock) "links" the physical movement of the mouse to 3D direction of view, using `movementX/Y` coordinates in PointerLock API. The degree of rotation shouldn't be affected by browser zoom here. Today Chrome [wrongly exposes](https://crbug.com/919921) `movementX/Y` in physical pixel, so it works. But if we make Chrome spec compliant (`movementX/Y` and `screenX/Y` in same coordinate space), there would no way for developers to "link" back to the physical movement of the mouse here. (With `pageZoomFactor` they can because physical-offset is `movementX/Y` times `pageZoomFactor` divided by `devicePixelRatio`, see the diagram above). @upsuper: Do you think this justifies the proposal here? -- GitHub Notification of comment by mustaqahmed Please view or discuss this issue at https://github.com/w3c/csswg-drafts/issues/3538#issuecomment-463301192 using your GitHub account
Received on Wednesday, 13 February 2019 17:58:28 UTC