Second touchmove event is marked cancelable |
||
Issue descriptionNavigate to: output.jsbin.com/begolep Notice that you get two touch moves after the touch start that are cancelable. I believe this is an issue I caused because when we get the second touchmove if we haven't received the gesture scroll update the event will be sent as cancelable. See: https://cs.chromium.org/chromium/src/content/browser/renderer_host/input/passthrough_touch_event_queue.cc?l=142 tdresser@ any ideas here?
,
Mar 31 2017
The following revision refers to this bug: https://chromium.googlesource.com/chromium/src.git/+/887c78b39f27eccd42ec308d1b899efc2a8f7a49 commit 887c78b39f27eccd42ec308d1b899efc2a8f7a49 Author: dtapuska <dtapuska@chromium.org> Date: Fri Mar 31 22:55:24 2017 Adjust cancelabilty of touchmoves that are queued when scroll start occurs. Generalize the coalescing callback to be a visit of the queue. Treat TouchScrollStart as a separate path in here. BUG= 700407 Review-Url: https://codereview.chromium.org/2788203002 Cr-Commit-Position: refs/heads/master@{#461262} [modify] https://crrev.com/887c78b39f27eccd42ec308d1b899efc2a8f7a49/content/renderer/input/main_thread_event_queue.cc [modify] https://crrev.com/887c78b39f27eccd42ec308d1b899efc2a8f7a49/content/renderer/input/main_thread_event_queue_task.h [modify] https://crrev.com/887c78b39f27eccd42ec308d1b899efc2a8f7a49/content/renderer/input/main_thread_event_queue_task_list.cc [modify] https://crrev.com/887c78b39f27eccd42ec308d1b899efc2a8f7a49/content/renderer/input/main_thread_event_queue_unittest.cc
,
Apr 3 2017
|
||
►
Sign in to add a comment |
||
Comment 1 by tdres...@chromium.org
, Mar 13 2017