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 17688
| Who | When | What | Removed | Added |
|---|---|---|---|---|
| myfacebook | 2012-07-04 09:29:03 UTC | CC | myfacebook | |
| ian | 2012-07-18 18:40:28 UTC | Component | other Hixie drafts (editor: Ian Hickson) | HTML |
| Product | HTML WG | WHATWG | ||
| QA Contact | public-html-bugzilla | contributor | ||
| ian | 2012-08-09 15:48:35 UTC | Status | NEW | RESOLVED |
| CC | ian | |||
| Resolution | --- | WONTFIX | ||
| myfacebook | 2013-04-16 06:49:58 UTC | Status | RESOLVED | REOPENED |
| Resolution | WONTFIX | --- | ||
| ian | 2013-06-03 23:30:22 UTC | Target Milestone | Unsorted | 2013 Q3 |
| ian | 2013-07-24 19:56:06 UTC | Status | REOPENED | NEW |
| Target Milestone | 2013 Q3 | 2014 Q4 | ||
| Summary | Specification should be clearer about when the downloading of the application cache starts. "These events are delayed until after the load event has fired." is a bit misleading. The chrome developer team interprets it as: Start downloading all resources f | appcache: Events fire at a weird time | ||
| ian | 2014-05-07 17:35:58 UTC | Target Milestone | 2014 Q4 | Unsorted |
| ian | 2014-07-25 20:10:39 UTC | CC | adrianba, ap, eoconnor, eric, franko, michaeln, mjs, Ms2ger, roc, simonp | |
| ian | 2014-09-05 21:55:23 UTC | Status | NEW | RESOLVED |
| Resolution | --- | FIXED |
Back to bug 17688