-
Notifications
You must be signed in to change notification settings - Fork 328
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
Drafting the patches to HTML #106
Comments
Notes:
|
How about Worker and SharedWorker? |
I filed whatwg/html#95 on HTML. I hope to work on this soonish, but it seems some more groundwork in Fetch is required first. |
whatwg/html#144 is a rewrite of the text in the HTML Standard. It also addresses workers. Review would be appreciated. |
Note that #126 will change what we do for navigation requests @dstockwell. I think this should be closed since it's no longer relevant. @jakearchibald? |
It's amusing that github wants to give me credit for all blink commits, but that was actually @horo-t |
Ah, @horo-t should probably add "[email protected]" to his GitHub email addresses to rectify that. |
Happy to close this |
Current: mode: "no-cors" credentials: "same-origin" redirect: "follow" With this patch: mode: "same-origin" credentials: "include" redirect: "manual" Spec Issue: whatwg/fetch#106 BUG=522873 Review URL: https://codereview.chromium.org/1320023005 git-svn-id: svn://svn.chromium.org/blink/trunk@202013 bbb929c8-8fbe-4397-9dbb-9b2b20218538
Given the recent confusion on navigation, now sounds like the right time to draft up a table, or patches for fetches.
Happy to do the work here, but @wanderview, you said you had a list of things that fetch to use as a starting point?
The text was updated successfully, but these errors were encountered: