24659 2014-02-14 05:20:29 +0000 fetch: In the CORS-enabled fetch, the non-normative use of the term "is available" is ambiguous 2015-09-17 08:22:11 +0000 1 1 1 Unclassified WHATWG HTML unspecified Other other RESOLVED FIXED http://www.whatwg.org/specs/web-apps/current-work/#processing-model blocked on dependencies P3 normal Unsorted 24080 1 contributor ian annevk ian mike naesten contributor oldest_to_newest 100575 0 contributor 2014-02-14 05:20:29 +0000 Specification: http://www.whatwg.org/specs/web-apps/current-work/multipage/fetching-resources.html Multipage: http://www.whatwg.org/C#processing-model Complete: http://www.whatwg.org/c#processing-model Referrer: http://www.whatwg.org/specs/web-apps/current-work/multipage/embedded-content-1.html Comment: "The resource is available, it is not a redirect, and its origin is the same origin as origin." How do you get "is available" here? What happens if there's an error in fetching? Posted from: 2001:470:1f07:57:3486:f523:9652:9655 by naesten@gmail.com User agent: Mozilla/5.0 (Windows NT 5.1; rv:24.0) Gecko/20100101 Firefox/24.0 100628 1 ian 2014-02-14 21:33:20 +0000 This is being replaced by http://fetch.spec.whatwg.org/. Is the problem there as well? If not, this will get fixed automatically when I rip this text out and reference that spec instead. 123237 2 annevk 2015-09-17 08:22:11 +0000 https://github.com/whatwg/html/commit/7c5555a16f2920c02244c10756bb2f1a11e87a22