Consider using WM_POINTER instead of WM_TOUCH for touch events
Categories
(Core :: Widget: Win32, enhancement)
Tracking
()
| Tracking | Status | |
|---|---|---|
| firefox137 | --- | fixed |
People
(Reporter: edgar, Assigned: saschanaz)
References
Details
Attachments
(1 external file)
This is what Chromium does for touch events, https://source.chromium.org/chromium/chromium/src/+/master:ui/base/ui_base_features.cc;l=123-126;drc=1b9416763d475710d789915060b4c90d025ff61b?originalUrl=https:%2F%2Fcs.chromium.org%2F
WM_POINTER provides some additional information that is not able to get from WM_TOUCH for pointer events.
| Assignee | ||
Comment 1•1 year ago
•
|
||
Note that consuming WM_TOUCH changes the coordinates of mouse cursor too; consuming WM_POINTER seems to make coordinates of each input device independent.
| Assignee | ||
Comment 2•1 year ago
|
||
| Assignee | ||
Comment 3•1 year ago
|
||
So consuming WM_POINTER does have the expected result of not changing mouse cursor position. But it seems this needs some APZ layer change as WM_POINTER do not collect multi touch pointers for us as WM_TOUCH does; each touch pointer will be reported independently. Currently just dispatching event for each pointer somehow deactivates the earlier but still active touch pointers.
| Assignee | ||
Comment 4•1 year ago
|
||
Actually we already have a workaround and it works for this case too.
Updated•1 year ago
|
Comment 6•1 year ago
|
||
| bugherder | ||
Description
•