This is an archived snapshot of W3C's public bugzilla bug tracker, decommissioned in April 2019. Please see the home page for more details.

Bug 20951 - FETCH: Instead of the "force same-origin" flag, use CORS-enabled with "No CORS, fail" mode instead
Summary: FETCH: Instead of the "force same-origin" flag, use CORS-enabled with "No COR...
Status: RESOLVED WONTFIX
Alias: None
Product: WHATWG
Classification: Unclassified
Component: HTML (show other bugs)
Version: unspecified
Hardware: Other other
: P3 normal
Target Milestone: 2016 Q1
Assignee: Ian 'Hixie' Hickson
QA Contact: contributor
URL: http://www.whatwg.org/specs/web-apps/...
Whiteboard:
Keywords:
Depends on:
Blocks:
 
Reported: 2013-02-11 15:50 UTC by contributor
Modified: 2013-11-19 22:00 UTC (History)
3 users (show)

See Also:

Attachments

Description contributor 2013-02-11 15:50:30 UTC 
Specification: http://www.whatwg.org/specs/web-apps/current-work/
Multipage: http://www.whatwg.org/C#processing-model
Complete: http://www.whatwg.org/c#processing-model

Comment:
Instead of the force same-origin flag can we not use No CORS, fail instead?

Posted from: 207.218.72.65
User agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10_8_2) AppleWebKit/537.30 (KHTML, like Gecko) Chrome/26.0.1403.0 Safari/537.30
Comment 1 Ian 'Hixie' Hickson 2013-03-27 23:32:54 UTC 
It's identical, right? So this is just an editorial change?

Affects text in workers and document.load().

I don't have a big objection in principle, but it doesn't seem like progress. :-)
Comment 2 Anne 2013-03-28 05:58:29 UTC 
Yes. The progress would be that there is one less distinct-looking algorithm going around.

The whole architecture around fetching is very much ad-hoc and not super clear so anything we can do to improve that is a win.
Comment 3 Ian 'Hixie' Hickson 2013-11-19 22:00:09 UTC 
Turns out in both cases where I could do this, I use the "synchronous flag", which my version of "potentially CORS-enabled fetch" doesn't support. So I'll just wait until I integrate with the fetch spec.