Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Jump to bottom

Introduce nested-navigate to Sec-Fetch-Mode. #22

Closed
mikewest opened this issue Mar 23, 2019 · 1 comment
Closed

Introduce nested-navigate to Sec-Fetch-Mode. #22

mikewest opened this issue Mar 23, 2019 · 1 comment

Comments

@mikewest
Copy link
Member

As discussed (at length!) in #16 and whatwg/fetch#755, it seems reasonable for us to distinguish top-level from nested navigations by splitting the navigate mode into navigate and nested-navigate.
@mikewest
Copy link
Member Author

I landed this change as part of bbd2c9c, somewhat inadvertently. Next time, I'll split it out more clearly. Tests are updating in https://chromium-review.googlesource.com/c/chromium/src/+/1536179 (and web-platform-tests/wpt#16034).

@mikewest mikewest mentioned this issue Mar 23, 2019
Closed
0xedward added a commit to 0xedward/webappsec-fetch-metadata that referenced this issue Nov 16, 2021
@0xedward
Add nested-navigate to list of valid Sec-Fetch-Mode values
ddb6c27 
w3c#22

https://chromium.googlesource.com/chromium/src.git/+/4f7e977e452765b7a7dd41fc47aac690bfeda2da
@0xedward 0xedward mentioned this issue Nov 16, 2021
Closed
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
None yet
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
1 participant
@mikewest