commit | df487ceb6910509c0356972ce6b46ce09d12d5cb | [log] [tgz] |
---|---|---|
author | Hiroki Nakagawa <nhiroki@chromium.org> | Thu Sep 01 04:36:40 2022 |
committer | Chromium LUCI CQ <chromium-scoped@luci-project-accounts.iam.gserviceaccount.com> | Thu Sep 01 04:36:40 2022 |
tree | 37ce0624d6ee963337d371fb4fcbac148bc31451 | |
parent | 65184af075ba475d47c69c0b0cb055c6253cf31e [diff] |
SpeculationRule: Implement "target_hint" for prerendering This CL implements "target_hint" for Speculation Rules based on the following spec PR: https://github.com/WICG/nav-speculation/pull/173 - This CL propagates "target_hint" from blink/ to content/browser/, but the browser process doesn't use this information yet. Follow-up CLs will implement the part. This half-baked implementation is still spec compatible as this information is just a hint and browser implementation is allowed to ignore them. - The spec requires the browser to accept the "valid browsing context name or keyword"[1] as the hint. As the initial step, this CL only supports "_blank" and "_self". If unsupported names or keywords are specified in the prerender rules, the rules are treated as no hint. - When "target_hint" is specified in prefetch rules, the rules are ignored. [1]https://html.spec.whatwg.org/C/#valid-browsing-context-name-or-keyword Bug: 1354049 Change-Id: Ia4a876e11e814f2dcc86c7dc19bef31b813c33ae Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/3833323 Reviewed-by: Domenic Denicola <domenic@chromium.org> Reviewed-by: Dominick Ng <dominickn@chromium.org> Reviewed-by: Lingqi Chi <lingqi@chromium.org> Commit-Queue: Hiroki Nakagawa <nhiroki@chromium.org> Reviewed-by: Kouhei Ueno <kouhei@chromium.org> Reviewed-by: Jeremy Roman <jbroman@chromium.org> Cr-Commit-Position: refs/heads/main@{#1041915}
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.