Implement scroll latching and metrics of ScrollingCoordinator with blink property trees |
||||||||||
Issue descriptionScrollingCoordinator is the a grabbag of logic for sending scroll-related data from blink to cc. This needs to be rewritten to work with blink property trees where PaintArtifactCompositor is responsible for sending scroll-related data to cc. Some examples of the data that we need to plumb through the new compositing codepath: Set cc::ScrollNode::overscroll_behavior with BlinkGenPropertyTrees Set cc::ScrollNode::snap_container_data with BlinkGenPropertyTrees Make scroll latching work with BlinkGenPropertyTrees Make scrollbar animations work with BlinkGenPropertyTrees Make position constraints work with BlinkGenPropertyTrees Make scroll metrics work with BlinkGenPropertyTrees ⛆ |
|
|
,
May 24 2018
,
May 24 2018
I've split everything but latching and metrics into issue 846414 - this bug will track the scroll latching and metrics parts. pdr@, I took a quick glance inside ScrollingCoordinator and didn't see anything obviously related to latching or metrics. Do you remember where these came from?
,
May 25 2018
,
May 25 2018
,
May 25 2018
,
May 25 2018
I took a look at latching and don't see anything that we need to change. The scroll metrics I was referring to are things like ScrollManager::RecordScrollRelatedMetrics. I am not sure if anything needs to be done there.
,
May 25 2018
I will check the scroll related metrics with the flag on to make sure that everything is recorded properly.
,
Aug 14
Both scroll latching and scroll related metrics for touch/wheel scroll/fling on main/Impl work properly. |
|||||||
►
Sign in to add a comment |
||||||||||
Comment 1 by bokan@chromium.org
, Apr 26 2018