-
Couldn't load subscription status.
- Fork 373
Editorial: Add guidelines for external specs about CORS, cross-origin isolation and TAO #1806
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.
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
base: main
Are you sure you want to change the base?
Conversation
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Looks great, thanks so much!
Co-authored-by: Dominic Farolino <[email protected]>
Co-authored-by: Dominic Farolino <[email protected]>
Co-authored-by: Dominic Farolino <[email protected]>
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Thanks for writing this!
|
@annevk care to take a look? |
Add a section to "using fetch elsewhere" that describes in a nutshell what new standards that invoke fetch should take
into the consideration when integrating with the same-origin policy protections enforced in the Fetch standard.
(See WHATWG Working Mode: Changes for more details.)
Preview | Diff