Issue metadata
Sign in to add a comment
|
DevTools: Input.dispatchTouchEvent sometimes loses touches. |
||||||||||||||||||||
Issue descriptionQuickly sending many 'touchStart' and 'touchEnd' commands with Input.dispatchTouchEvent results in some of the touches being lost and the corresponding DOM events are not fired on the page. I tracked this down to https://cs.chromium.org/chromium/src/cc/trees/layer_tree_impl.cc?q=layer_tree_impl.cc&sq=package:chromium&l=1946 When the touches are unsuccessful, all of the touch regions are empty. Returning true here fixes the problem, but I imagine that isn't a good solution.
,
Oct 24 2017
Looking at this again, it appears the touches are only lost on the first frame after a navigation. The test I had written where I was losing touchEnds was flawed.
,
Oct 25 2017
,
Oct 25 2017
DevTools isn't waiting for cc::ProxyMain::BeginMainFrame to finish, and the touch regions are not set up by the time we send our first touchStart.
,
Oct 26 2017
,
Mar 28 2018
|
|||||||||||||||||||||
►
Sign in to add a comment |
|||||||||||||||||||||
Comment 1 by dgozman@chromium.org
, Sep 21 2017