New issue
Advanced search Search tips
Note: Color blocks (like or ) mean that a user may not be available. Tooltip shows the reason.

Issue 645195 link

Starred by 1 user

Issue metadata

Status: Fixed
Owner:
Closed: Jan 2018
Cc:
Components:
EstimatedDays: ----
NextAction: ----
OS: ----
Pri: 3
Type: Bug



Sign in to add a comment

Process TouchpadFling scroll events on the compositor

Project Member Reported by dtapu...@chromium.org, Sep 8 2016

Issue description

When TouchpadFling gestures are generated the wheel event generation occurs inside the renderer. This causes a performance draw back if there are wheel event listeners in javascript as the entire fling is moved to the main thread causing main thread scrolling.

See:
https://cs.chromium.org/chromium/src/ui/events/blink/input_handler_proxy.cc?q=input_handler_proxy.cc&sq=package:chromium&l=1246

It should be possible that events are sent to the main thread and executed by the fling is then processed on the compositor thread.

Perhaps the event generation (from the fling gesture) should be done in the browser process to make it similar to how this happens on Mac.
 
Cc: flackr@chromium.org vollick@chromium.org
Labels: -Hotlist-ThreadedRendering Hotlist-Threaded-Rendering

Comment 3 by flackr@chromium.org, Jan 24 2017

Labels: -Hotlist-Threaded-Rendering Hotlist-ThreadedRendering
Cc: sahel@chromium.org
Owner: sahel@chromium.org
Status: Fixed (was: Available)
These events have moved to the browser side so they should get processed on the compositor.

Sign in to add a comment