New issue
Advanced search Search tips

Issue 764122 link

Starred by 1 user

Issue metadata

Status: Assigned
Merged: issue 613219
Owner:
Components:
EstimatedDays: ----
NextAction: ----
OS: ----
Pri: 2
Type: Bug



Sign in to add a comment

DevTools: Input.dispatchTouchEvent sometimes loses touches.

Project Member Reported by einbinder@chromium.org, Sep 11 2017

Issue description

Quickly 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.

 
Owner: dgozman@chromium.org
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.
Description: Show this description
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.
Mergedinto: 613219
Status: Duplicate (was: Assigned)
Owner: einbinder@chromium.org
Status: Assigned (was: Duplicate)

Sign in to add a comment