Reuse response's has-cross-origin-redirects #8405
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
3 tasks
abinpaul1
commented
Oct 19, 2022
domenic
reviewed
Oct 20, 2022
annevk
approved these changes
Oct 21, 2022
domenic
added
the
do not merge yet
annevk
pushed a commit
to whatwg/fetch
that referenced
this pull request
Oct 22, 2022
Resource Timing PR: w3c/resource-timing#335. HTML PR: whatwg/html#8405. Follow-up to provide more clarity around filtered responses (which this relies on): #1509.
annevk
removed
the
do not merge yet
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.
Reuse response's has-cross-origin-redirects in place of navigation param's has cross-origin redirects boolean.
Discussion : whatwg/fetch#1468 (comment)
/browsing-the-web.html ( diff )
/infrastructure.html ( diff )