This is an archived snapshot of W3C's public bugzilla bug tracker, decommissioned in April 2019. Please see the home page for more details.
Back to bug 24659
| Who | When | What | Removed | Added |
|---|---|---|---|---|
| ian | 2014-02-14 21:33:20 UTC | CC | ian | |
| ian | 2014-02-21 22:14:30 UTC | Whiteboard | blocked on integration with fetch spec | |
| ian | 2014-05-15 23:00:57 UTC | Summary | "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? | fetch: In the CORS-enabled fetch, the non-normative use of the term "is available" is ambiguous |
| ian | 2014-09-25 23:02:30 UTC | Depends on | 24080 | |
| Whiteboard | blocked on integration with fetch spec | blocked on dependencies | ||
| annevk | 2015-09-17 08:22:11 UTC | Status | NEW | RESOLVED |
| CC | annevk | |||
| Resolution | --- | FIXED |
Back to bug 24659