commit | b082d3309844bbbac26a5f4af42043ec875ba687 | [log] [tgz] |
---|---|---|
author | Lingqi Chi <lingqi@chromium.org> | Fri Nov 29 16:24:28 2024 |
committer | Chromium LUCI CQ <chromium-scoped@luci-project-accounts.iam.gserviceaccount.com> | Fri Nov 29 16:24:28 2024 |
tree | a44f3e35912202c4843545fa3350b6e8a16c73b2 | |
parent | c246bcc072ade3680c63e2107f75a4d511281ecf [diff] |
[Prerender] Add a feature to enable lazy loading image for invisible pages. Before this CL, all image with loading=lazy attribute will be loaded if they are on invisible pages, including prerendering. This is a trade-off between loading as many resources as possible for invisible pages and saving as many resources are possible for invisible pages as the viewport they are in is invisible. The pros for the latter are: (credit to barrypollard@) - saving users' network bandwidth. - let the renderer processes focus on the most important work when they are invisible to reduce contention. - saving website's resources as some prerender pages may never be shown to users. Specification does not set restriction for UA, so we'd like to try another path, to respect this attribute for prerendering pages and all invisible pages. This CL adds a three-valued feature parameter to allow us to experiment and find the best behavior. Bug: 381110833 Change-Id: I0899423d906b4b65b2d10545930e7218c3f2fc7a Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/6055522 Reviewed-by: Domenic Denicola <domenic@chromium.org> Reviewed-by: Hiroki Nakagawa <nhiroki@chromium.org> Commit-Queue: Lingqi Chi <lingqi@chromium.org> Cr-Commit-Position: refs/heads/main@{#1389836}
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.