Handle the null fetch client case #175
Merged
Conversation
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
If referrer is left as "client" (the default) and there's no fetch client, the spec is currently broken. Instead, have it return no referrer. The most prominent null client case is browser UI navigations, although there are possibly others where the browser creates a new window independently.
domfarolino
approved these changes
Jun 6, 2025
|
Going through my open PRs; ping on merging this? |
mikewest
approved these changes
Oct 4, 2025
|
Thanks! |
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.
If referrer is left as "client" (the default) and there's no fetch client, the spec is currently broken. Instead, have it return no referrer.
The most prominent null client case is browser UI navigations, although there are possibly others where the browser creates a new window independently.
Preview | Diff