Move more functionality into ResolveFrameData Move DisplayResourceProvider resource code and surface damage code into ResolvedFrameData. This lets resource lifetime be linked to resolved frame lifetime automatically. This also centralizes the surface damage calculations in ResolvedFrameData since it holds the inputs for that. Bug: 1126147 Change-Id: Ie3221d9661eef844f00439d3fa9f1f16155289ea Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/3656289 Reviewed-by: Bo Liu <boliu@chromium.org> Reviewed-by: Peter McNeeley <petermcneeley@chromium.org> Commit-Queue: Kyle Charbonneau <kylechar@chromium.org> Cr-Commit-Position: refs/heads/main@{#1017304}
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.