commit | 055a3549f4b1410a93b85a5931cfe1ecc7b2b00f | [log] [tgz] |
---|---|---|
author | William Liu <liuwilliam@chromium.org> | Sun Apr 02 17:21:19 2023 |
committer | Chromium LUCI CQ <chromium-scoped@luci-project-accounts.iam.gserviceaccount.com> | Sun Apr 02 17:21:19 2023 |
tree | 9e026ade16a1902120472d63e49ff75cf01b1da7 | |
parent | 82d5e77eacab0abc5e2c7447c5350447a03b7b10 [diff] |
[navigation-transitions]: Cache screenshots for navigation entries Introduce NavigationEntryScreenshot, which preserves a screenshot on the current NavigationEntry when the user is navigating away from it. The stored screenshot will later be used to present the user with a preview, when the user navigates back to this page. The caching mechanism is composed of the screenshot, the cache and a global manager. The global manager lives on the BrowserContext and is responsible for memory budgeting. The cache lives on the primary NavigationController which owns the NavigationEntry where the screenshot is stashed. This CL contains the impl of caching, retrieving and eviction of the screenshots with unittests. The cache is not integrated with the navigation thus no browsertest. The code resides in `//content/browser/renderer_host/` because no need to access WebContents. [Updated] DD/Explainer (chromium access): https://docs.google.com/document/d/1-7TatVjSL4n-RNyvN_MWdFoOiR6YJ1BjvJKgvym_ArU Feature EngDoc: https://docs.google.com/document/d/1H99XZHdAWNfbfboHbGdMB97k81AzAxVtPSizAjO2Poc/ PRD (google access): https://docs.google.com/document/d/1JMWzArv0VR-G4xx3a5ku8N5np8mDeGSuvR95kZc8ynY/ Bug: 1415332, 1413521 Change-Id: Icc3b2aa7b5b36ed460ad2ddd1ff5f645a38d2835 Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/4245857 Reviewed-by: Kyle Charbonneau <kylechar@chromium.org> Commit-Queue: William Liu <liuwilliam@chromium.org> Reviewed-by: Avi Drissman <avi@chromium.org> Cr-Commit-Position: refs/heads/main@{#1125127}
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.