New issue
Advanced search Search tips

Issue 852464 link

Starred by 1 user
Status: Available
Merged: issue 836884
Owner: ----
Cc:
danakj@chromium.org
weiliangc@chromium.org
enne@chromium.org
chrishtr@chromium.org
Components:
EstimatedDays: ----
NextAction: ----
OS: ----
Pri: 2
Type: Task

Blocking:
issue 595843



Sign in to add a comment

[cc/ui] Generate and use LayerList as part of Property tree building on main thread

Project Member Reported by weiliangc@chromium.org, Jun 13 2018 
Main thread cc still has a Layer Tree. When pushing properties to compositor thread the iterator walks the layer tree.

Instead should generate a list of layer when property tree is built.

Ideally that layer list would only be layers that has content.

Comment 1 by chrishtr@chromium.org, Jun 13 2018

Mergedinto: 836884
Status: Duplicate (was: Available)
This is a consequence of the BlinkGenPropertyTrees project.

Comment 2 by weiliangc@chromium.org, Jun 13 2018 

Mostly focused on behavior of TreeSynchronizer and LayerListIterator classes. Maybe this would be a separate task?

And ui::compositor would still need PropertyTreeBuilder (which should add generation of layer list as well)?

Comment 3 by chrishtr@chromium.org, Jun 13 2018 

Re ui::compositor: yes. The PropertyTreeBuilder will end up being just
for that client of cc.

Comment 4 by weiliangc@chromium.org, Jun 13 2018 

Was thinking of this when looking at SetHideLayerAndSubtree. That is used by ui::compositor to try skipping over layers, and right now tree synchronizer would still walk the entire tree.

Comment 5 by weiliangc@chromium.org, Jun 13 2018

Status: Available (was: Duplicate)
Summary: [cc/ui] Generate and use LayerList as part of Property tree building on main thread (was: [cc] Generate and use LayerList as part of Property tree building on main thread)
Going to de-dup, and adding ui to title to hopefully reduce confusion.
►

Sign in to add a comment