Revert "[renderblocking] Implement render-blocking on preload links" This reverts commit 7ca253a5c1e0340e78ddacba91e927c927fb3086. Reason for revert: Found a better to implement it, which is closer to the spec and also covers both preload and modulepreload links Original change's description: > [renderblocking] Implement render-blocking on preload links > > This patch: > > 1. Plumbs BlockingAttribute to LinkLoadParameters and HTMLPreloadScanner > so that they can tell if a link preload should be render-blocking > > 2. Use the BlockingAttribute value to set RenderBlockingBehavior in the > FetchParameters of the link preload, and use it to decide whether the > resource should be added to RenderBlockingResourcePreloader > > This patch doesn't implement render-blocking for link header preloads, > which will be left for follow-up work. > > Bug: 1271296 > Change-Id: Iedabdea370691f7f93072bc7e8f47fe93728d106 > Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/3514642 > Reviewed-by: Mason Freed <masonf@chromium.org> > Reviewed-by: Joey Arhar <jarhar@chromium.org> > Commit-Queue: Xiaocheng Hu <xiaochengh@chromium.org> > Cr-Commit-Position: refs/heads/main@{#980778} Bug: 1271296 Change-Id: Idbf3f49af07376442a4e6970e701783c9876be05 Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/3526564 Reviewed-by: Joey Arhar <jarhar@chromium.org> Bot-Commit: Rubber Stamper <rubber-stamper@appspot.gserviceaccount.com> Commit-Queue: Xiaocheng Hu <xiaochengh@chromium.org> Cr-Commit-Position: refs/heads/main@{#981419}
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.