Issue metadata
Sign in to add a comment
|
Coalescing wrong events from different pointer type |
||||||||||||||||||||||
Issue descriptionWhen we are coalescing touch events or mouse events, we did not check their pointer type and pointer id. Since we start supporting the stylus input and they are constructed as mouse events or touch events, we should check the ID and pointer type when coalescing mouse events or touch events.
,
Jun 29 2018
The following revision refers to this bug: https://chromium.googlesource.com/chromium/src.git/+/e129b20fd90c0c118cfb11f0811c44ca50f9b1e5 commit e129b20fd90c0c118cfb11f0811c44ca50f9b1e5 Author: Lan Wei <lanwei@chromium.org> Date: Fri Jun 29 18:31:28 2018 Check the pointer id and pointer type when coalescing When we coalesce the touch events or mouse events, we should check their pointer id and pointer type, so we do not coalesce events from stylus inputs with events from other input sources. Bug:857209 Change-Id: I157ca5047047bb812564382f49e316bee9f88f19 Reviewed-on: https://chromium-review.googlesource.com/1117633 Commit-Queue: Lan Wei <lanwei@chromium.org> Reviewed-by: Navid Zolghadr <nzolghadr@chromium.org> Reviewed-by: Timothy Dresser <tdresser@chromium.org> Cr-Commit-Position: refs/heads/master@{#571557} [modify] https://crrev.com/e129b20fd90c0c118cfb11f0811c44ca50f9b1e5/ui/events/blink/blink_event_util.cc [modify] https://crrev.com/e129b20fd90c0c118cfb11f0811c44ca50f9b1e5/ui/events/blink/blink_event_util_unittest.cc
,
Jul 3
|
|||||||||||||||||||||||
►
Sign in to add a comment |
|||||||||||||||||||||||
Comment 1 by monor...@bugs.chromium.org
, Jun 29 2018