Android: hovering stylus events arrive as WebMouseEvents, others as WebTouchEvent |
||||||
Issue descriptionThis is done at a lower level to support stylus hover events since touches can't hover: https://code.google.com/p/chromium/codesearch#chromium/src/content/public/android/java/src/org/chromium/content/browser/ContentViewCore.java&l=1652 This means, hovering stylus and touching stylus appear differently at EventHandler level! If we want a consistent pointerId, this has to be unified. I recall Edge that changes pen pointerId with each touch. How would they support hovering pen?
,
Mar 8 2016
In this case we have to have a way to understand that PlatformMouseEvent belongs to the same pen that comes as PlatformTouchEvent. Basically if the id of those events in pointerproperties for those different events are set the same we just automatically give it the same pointer id. If not we cannot give them the same id as they may belong to two different pens on the screen. Right? Although I'm not sure what is the underlying id for the pen events and whether it is set at all or not.
,
Mar 8 2016
Also Issue 591473 seems related.
,
Mar 8 2016
Yes, Issue 591473 covers only the pointerType part of it. This bug is about fixing the bigger issues on the Blink side. Id matching problem is one of them. There could be issues with suppressed touchmoves vs unsuppressed mousemoves. To me, this bugs and Issue 587550 together look like a motivation to explore a non-TouchEvent path for mouse & pen events in Android.
,
Jun 29 2016
,
Jun 29 2017
This issue has been Available for over a year. If it's no longer important or seems unlikely to be fixed, please consider closing it out. If it is important, please re-triage the issue. Sorry for the inconvenience if the bug really should have been left as Available. If you change it back, also remove the "Hotlist-Recharge-Cold" label. For more details visit https://www.chromium.org/issue-tracking/autotriage - Your friendly Sheriffbot
,
Jun 29 2017
Mustaq, is this still relevant? Could you please re-triage?
,
Jun 29 2017
Platform events are now gone, but the same problem exists through WebInputEvents. Assigning to myself.
,
Jan 7
mustaq@ we have the same situation on Windows. We do get the pen events as both mouseevents and touchevents but since their underlying is the same it doesn't cause any issue in Blink. Is this not the case on Android?
,
Jan 7
Hmm, I thought events coming from two different paths can't share a common pointerId at the very least. Any chance we expose a constant id (=1 as if "mouse") so the issue is partially hidden? Or may be we even merge the event streams back with a common pointerId != 1? It was never an issue in Android, I guess because hoverable pen is rare. |
||||||
►
Sign in to add a comment |
||||||
Comment 1 by mustaq@chromium.org
, Mar 4 2016