New issue
Advanced search Search tips

Issue 924196 link

Starred by 1 user

Issue metadata

Status: Assigned
Owner:
Cc:
EstimatedDays: ----
NextAction: ----
OS: Chrome
Pri: 1
Type: Bug-Regression



Sign in to add a comment

Incorrect touchpad even sequence on ChromeOS

Project Member Reported by sahel@chromium.org, Today (11 hours ago)

Issue description

Chrome Version: 73.0.3674.0
OS: ChromeOS

What steps will reproduce the problem?
(1)Navigate to any scrollable site
(2)scroll/fling in up and down directions a few times.

What is the expected result?
We should receive ET_SCROLL_FLING_CANCEL events each time the user puts their fingers on touchpad, and ET_SCROLL_FLING_START each time the user lifts their fingers. The correct event sequence should be:
(ET_SCROLL_FLING_CANCEL, (ET_SCROLL)xN, ET_SCROLL_FLING_START)xM
i.e. between an ET_SCROLL event and its previous ET_SCROLL_FLING_START, we should receive a ET_SCROLL_FLING_CANCEL event.

What happens instead?
Sometimes no ET_SCROLL_FLING_CANCEL arrives when the user puts their fingers on touchpad and ET_SCROLL arrives right after ET_SCROLL_FLING_START.

I added logs to https://cs.chromium.org/chromium/src/ui/events/event_dispatcher.cc?gsn=ack_result&g=0&l=193 to check the arriving events.


 

Comment 1 by sahel@chromium.org, Today (11 hours ago)

Cc: afakhry@chromium.org sahel@chromium.org bleung@chromium.org adlr@chromium.org
Labels: -Pri-3 Pri-1
Owner: sheckylin@chromium.org
Status: Assigned (was: Untriaged)
Marking it as a P1 since incorrect event sequence cascades to incorrect scroll sequences and event hit testing.

ccing people from issue 889707:
+bleung@chromium.org, adlr@chromium.org, afakhry@chromium.org

sheckylin@ would you please help with triaging the issue if it is not the root cause of issue 889707.

Comment 2 by afakhry@chromium.org, Today (9 hours ago)

Cc: sadrul@chromium.org tdres...@chromium.org
sadrul@ or tdresser@ please help triage.

Comment 3 by sheckylin@chromium.org, Today (2 hours ago)

Hi, I am unsure if this is the root cause of issue 889707, but it seems very much likely to be if the issue happens only on Pixelbook.

Sign in to add a comment