Re: [w3c/uievents] MouseEvent.screenX/Y coordinate space id not clear (#150)

@EiraGe has created an extensive report on [PointerLock coordinate space](https://docs.google.com/document/d/1mYk4qMxBVsFweqFOku2FZvMajejp2Q7XWGIld9ivlXE/edit?usp=sharing) where we observe that all major browsers except Edge expose `screenX/Y` coordinate in DIPs (device independent pixels).  So changing the `screenX/Y` spec to match the reality seems to be the best way forward for this issue.

@smaug----, does it sound like an acceptable solution here?

This is remotely related to this issue but we discussed it here: we also find in the above doc that we currently have no factors (in spec or in browsers) that allows conversion between DIPs and physical/CSS pixels.  We will handle it separately, possibly through the [PointerLock coordinate](https://github.com/w3c/pointerlock/issues/23) thread.  (Note that `devicePixelRatio` is between physical/CSS pixels.)


-- 
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/uievents/issues/150#issuecomment-455258687