Prerender: record destination for resource loading blocked by client I'm wondering the reason why we need to cancel prerendering during loading resources and which resources would be blocked. This CL adds a histogram to track it. Bug: 1445438 Change-Id: I1b70ccc8ed83b264399c2be975f4ea24ed76ef8f Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/4592157 Reviewed-by: Hiroki Nakagawa <nhiroki@chromium.org> Reviewed-by: Takashi Toyoshima <toyoshim@chromium.org> Commit-Queue: Lingqi Chi <lingqi@chromium.org> Cr-Commit-Position: refs/heads/main@{#1154303}
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.