Editorial review: Add speculationrules request.destination#40357
Merged
hamishwillee merged 4 commits intoJul 16, 2025
Merged
Conversation
Contributor
Author
|
@domenic, do you think this needs anything else? |
Contributor
|
Preview URLs Flaws (3)Note! 1 document with no flaws that don't need to be listed. 🎉 URL:
(comment last updated: 2025-07-16 00:10:39) |
domenic
reviewed
Jul 15, 2025
Co-authored-by: Domenic Denicola <d@domenic.me>
Contributor
Author
|
Technical review done, cheers @domenic. @hamishwillee can I get you to sign off on this one? |
This file contains hidden or 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
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.
Description
As requested in #40289, this PR adds information to MDN about the
speculationrulesrequest destination type.See https://wicg.github.io/nav-speculation/speculation-rules.html#fetch for the specification.
Browser compat information TBC.
Motivation
Additional details
Related issues and pull requests
Fixes #40289.