[Bug 28029] Mouse coordinates represented in CSS pixels do not account for retina displays with window.devicePixelRatio > 1.

https://www.w3.org/Bugs/Public/show_bug.cgi?id=28029

Boris Gjenero <boris.gjenero@gmail.com> changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
                 CC|                            |boris.gjenero@gmail.com

--- Comment #2 from Boris Gjenero <boris.gjenero@gmail.com> ---
Note that movementX and movementY values described in the pointer lock API are
also affected:
https://dvcs.w3.org/hg/pointerlock/raw-file/default/index.html#extensions-to-the-mouseevent-interface

There is the same loss of precision as with position plus there is also the
possibility that slow movement gets rounded to zero and ignored. It may be
possible to slowly move the mouse as far as you want without causing any
movement to be reported. I can reproduce this in Firefox 35 when using
increased layout.css.devPixelsPerPx. A browser could work around this by
accumulating sub-pixel motion, but floating point values are a better solution.

-- 
You are receiving this mail because:
You are the QA Contact for the bug.

Received on Sunday, 15 February 2015 05:19:53 UTC