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 24659 - fetch: In the CORS-enabled fetch, the non-normative use of the term "is available" is ambiguous
Summary: fetch: In the CORS-enabled fetch, the non-normative use of the term "is avail...
Status: RESOLVED FIXED
Alias: None
Product: WHATWG
Classification: Unclassified
Component: HTML (show other bugs)
Version: unspecified
Hardware: Other other
: P3 normal
Target Milestone: Unsorted
Assignee: Ian 'Hixie' Hickson
QA Contact: contributor
URL: http://www.whatwg.org/specs/web-apps/...
Whiteboard: blocked on dependencies
Keywords:
Depends on: fetch
Blocks:
  Show dependency tree / graph
 
Reported: 2014-02-14 05:20 UTC by contributor
Modified: 2015-09-17 08:22 UTC (History)
4 users (show)

See Also:

Attachments

Description contributor 2014-02-14 05:20:29 UTC 
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
Comment 1 Ian 'Hixie' Hickson 2014-02-14 21:33:20 UTC 
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.