New issue
Advanced search Search tips

Issue 635674 link

Starred by 2 users
Status: Fixed
Owner: ----
Closed: Aug 2017
Cc:
skobes@chromium.org
vmp...@chromium.org
Components:
EstimatedDays: ----
NextAction: ----
OS: ----
Pri: 3
Type: Bug



Sign in to add a comment

Document the high-level compositor<->paint architecture

Project Member Reported by pdr@chromium.org, Aug 8 2016 
With both spv2 and spv1 codepaths, the compositor/paint architecture is a little confusing to folks outside the paint team. We should better document how it works at a high level, maybe through some header comments or in a readme.

For example, in spv1 both ContentLayerDelegate::paintContents and FrameView::synchronizedPaint call GraphicsLayer::paint but synchronizedPaint does the real work of painting and ContentLayerDelegate::paintContents only copies over the result. In spv2, FrameView::pushPaintArtifactToCompositor handles updating the compositor.
Project Member

Comment 1 by sheriffbot@chromium.org, Aug 9 2017

Labels: Hotlist-Recharge-Cold
Status: Untriaged (was: Available)
This issue has been Available for over a year. If it's no longer important or seems unlikely to be fixed, please consider closing it out. If it is important, please re-triage the issue.

Sorry for the inconvenience if the bug really should have been left as Available. If you change it back, also remove the "Hotlist-Recharge-Cold" label.

For more details visit https://www.chromium.org/issue-tracking/autotriage - Your friendly Sheriffbot

Comment 2 by schenney@chromium.org, Aug 9 2017

Labels: -Hotlist-Recharge-Cold PaintTeamTriaged-20170809 BugSource-Team
Status: Available (was: Untriaged)

Comment 3 by pdr@chromium.org, Aug 9 2017

Status: Fixed (was: Available)
We've been much better at updating the various README.md files lately, and my presentation about property trees in blink is a high level overview of the design today: https://docs.google.com/presentation/d/1ak7YVrJITGXxqQ7tyRbwOuXB1dsLJlfpgC4wP7lykeo/view.

We should continue making presentations and improving documentation of course, but I think we've climbed out of the extremely bad state we were in.
►

Sign in to add a comment