Re: [w3c/uievents] Mouse coordinates represented in CSS pixels do not account for retina displays with window.devicePixelRatio > 1 (#40)

To be clear, the specific proposal here is to update the spec to take in the extension which has been in [CSS OM View](https://www.w3.org/TR/cssom-view-1/#extensions-to-the-mouseevent-interface) for the past 10 years. That is, make  `MouseEvent` and `MouseEventInit` coordinates `double` not `long`.

Separately it's open for discussion what the spec should say (if anything) about when platforms may want to constrain themselves to sending only integer values. For the past 10 years, Chromium has had the `MouseEvent` accessors truncate the values to integers, while the `PointerEvent` (which derives from `MouseEvent`) accessors do not. This was done as a compat mitigation and may or may not still be necessary today.


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

Message ID: <w3c/uievents/issues/40/2248304744@github.com>