Convert Touch's coordinates from long to double
Categories
(Core :: DOM: Events, defect, P5)
Tracking
()
People
(Reporter: smaug, Unassigned)
References
Details
|
||
Comment 1•5 years ago
|
||
Bulk-downgrade of unassigned, >=3 years untouched DOM/Storage bug's priority.
If you have reason to believe this is wrong, please write a comment and ni :jstutte.
I believe this is should be reprioritized.
Chrome, Edge, and IE are using doubles for pointer event coordinates, don't know about Safari.
This breaks accurate mouse input on high DPI devices, which are becoming ubiquitous. It's a real problem, not just a "nice to have". Basically, you can't even implement a drawing/painting app on high DPI.
Unless I'm missing some obscure compat flag.
Some discussion here:
https://github.com/w3c/uievents/issues/40
|
|
||
Comment 3•3 years ago
|
||
Bringing this to your attention, Hsin-Yi. Thanks!
|
||
Comment 4•3 years ago
|
||
(In reply to Jens Stutte [:jstutte] from comment #3)
Bringing this to your attention, Hsin-Yi. Thanks!
Thanks Jens. Will take a look with the team.
|
|
||
Updated•3 years ago
|
|
|
||
Comment 5•3 years ago
|
||
(In reply to bplu4t2f from comment #2)
I believe this is should be reprioritized.
Chrome, Edge, and IE are using doubles for pointer event coordinates, don't know about Safari.
This breaks accurate mouse input on high DPI devices, which are becoming ubiquitous. It's a real problem, not just a "nice to have". Basically, you can't even implement a drawing/painting app on high DPI.
Unless I'm missing some obscure compat flag.
Some discussion here:
https://github.com/w3c/uievents/issues/40
This bug is talking about "touch event", but it looks to me that comment 2 was raising interests for changes to pointer events, which inherits mouse events. https://github.com/w3c/uievents/issues/40 is still not resolved, and I filed bug 1833963 for tracking the pointer events/mouse events changes, which should be resolved after there's a conclusion on the spec issue.
Description
•