20951 2013-02-11 15:50:30 +0000 FETCH: Instead of the "force same-origin" flag, use CORS-enabled with "No CORS, fail" mode instead 2013-11-19 22:00:09 +0000 1 1 1 Unclassified WHATWG HTML unspecified Other other RESOLVED WONTFIX http://www.whatwg.org/specs/web-apps/current-work/#processing-model P3 normal 2016 Q1 1 contributor ian annevk ian mike contributor oldest_to_newest 82908 0 contributor 2013-02-11 15:50:30 +0000 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 85068 1 ian 2013-03-27 23:32:54 +0000 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. :-) 85078 2 annevk 2013-03-28 05:58:29 +0000 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. 96551 3 ian 2013-11-19 22:00:09 +0000 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.