[VizLayers] Push basic display tree updates Pushes basic tree metadata as well as the transform property tree. Subsequent CLs will add layers and other property trees. This also corrects a few minor issues in display tree lifecycle: - Pushing the tree from the client will update its "needs first draw" bit in the scheduler so we don't trigger an endless stream of redundant BeginFrames after one activation. - Don't push a frame ack back to the client for frames submitted by LayerContextImpl. - Display tree teardown no longer tries to clean up state related to tiles or UI resources, which display trees don't manage. Bug: 40902503 Change-Id: I2a1216e5da2a83c0d73a724c6a548e08aea8e3ac Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/5588471 Reviewed-by: Nasko Oskov <nasko@chromium.org> Reviewed-by: Victor Miura <vmiura@chromium.org> Reviewed-by: Ken Rockot <rockot@google.com> Reviewed-by: Jonathan Ross <jonross@chromium.org> Commit-Queue: Ken Rockot <rockot@google.com> Cr-Commit-Position: refs/heads/main@{#1312030}
Chromium is an open-source browser project that aims to build a safer, faster, and more stable way for all users to experience the web.
The project's web site is https://www.chromium.org.
To check out the source code locally, don't use git clone! Instead, follow the instructions on how to get the code.
Documentation in the source is rooted in docs/README.md.
Learn how to Get Around the Chromium Source Code Directory Structure.
For historical reasons, there are some small top level directories. Now the guidance is that new top level directories are for product (e.g. Chrome, Android WebView, Ash). Even if these products have multiple executables, the code should be in subdirectories of the product.
If you found a bug, please file it at https://crbug.com/new.