Add speculation rules improvements for Chrome 121 #22262
Merged
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
github-actions
bot
added
data:http 🚠
tunetheweb
reviewed
Feb 22, 2024
html/elements/script.json
Outdated
Comment on lines
936
to
968
| "source_document": { | ||
| "__compat": { | ||
| "description": "<code>source</code> key <code>document</code> value", | ||
| "support": { | ||
| "chrome": { | ||
| "version_added": "121" | ||
| }, | ||
| "chrome_android": "mirror", | ||
| "edge": "mirror", | ||
| "firefox": { | ||
| "version_added": false | ||
| }, | ||
| "firefox_android": "mirror", | ||
| "ie": { | ||
| "version_added": false | ||
| }, | ||
| "oculus": "mirror", | ||
| "opera": "mirror", | ||
| "opera_android": "mirror", | ||
| "safari": { | ||
| "version_added": false | ||
| }, | ||
| "safari_ios": "mirror", | ||
| "samsunginternet_android": "mirror", | ||
| "webview_android": "mirror" | ||
| }, | ||
| "status": { | ||
| "experimental": true, | ||
| "standard_track": true, | ||
| "deprecated": false | ||
| } | ||
| } | ||
| }, |
There was a problem hiding this comment.
@chrisdavidmills we crossed our streams again :-)
I think we can remove this bit as I added this as a url and where parameters in #22188. We're making source: url and source: document optional (and maybe eventually removing it?) as it can be implied from whether url and where exists. Therefore don't think we should add that.
There was a problem hiding this comment.
It's also a bit weird it being its own standalone item...it would make a bit more sense if it were a subitem of source, but no.
I'll remove it.
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Summary
Chrome 121 has added several new features for the Speculation Rules API:
Speculation-RulesHTTP response header, which allows developers to set speculation rules on a page via a response header, without modifying the actual page code. I added a new BCD feature for the header. See https://chromestatus.com/feature/5069400512659456 for more info.sourcekey value,document; the relatedwherekey is already included in the data. See https://chromestatus.com/feature/5112150536749056eagernessfield, which allows developers to set how eagerly they want URLs to be prefetched/prerendered. I added a sub-feature foreagerness. See https://chromestatus.com/feature/5091678266851328.No-Vary-SearchHTTP response header, which is used to indicate whether URL params should be ignored when deciding whether to fetch a page from cache or not. New feature added for the header. See https://chromestatus.com/feature/5071247189213184expects_no_vary_searchfield, which allows developers to report the expected value of theNo-Vary-Searchresponse header in the speculation rules, and use that to determine whether a prefetch would be beneficial or not. New sub-feature added for this field. See https://chromestatus.com/feature/4887338302308352Test results and supporting details
Related issues