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 7685 - States of ApplicationCache objects are inconsistent with application caches
Summary: States of ApplicationCache objects are inconsistent with application caches
Status: CLOSED NEEDSINFO
Alias: None
Product: HTML WG
Classification: Unclassified
Component: pre-LC1 HTML5 spec (editor: Ian Hickson) (show other bugs)
Version: unspecified
Hardware: PC All
: P2 normal
Target Milestone: ---
Assignee: Ian 'Hixie' Hickson
QA Contact: HTML WG Bugzilla archive list
URL: http://dev.w3.org/html5/spec/Overview...
Whiteboard:
Keywords:
Depends on:
Blocks:
 
Reported: 2009-09-21 17:08 UTC by Nikunj Mehta
Modified: 2010-10-04 13:59 UTC (History)
4 users (show)

See Also:

Attachments

Description Nikunj Mehta 2009-09-21 17:08:23 UTC 
The spec lists only four states of an application cache - idle, checking, downloading, and obsolete. However, an ApplicationCache object has more states.
[[
  const unsigned short UNCACHED = 0;
  const unsigned short IDLE = 1;
  const unsigned short CHECKING = 2;
  const unsigned short DOWNLOADING = 3;
  const unsigned short UPDATEREADY = 4;
  const unsigned short OBSOLETE = 5;
  readonly attribute unsigned short status;
]]

There are two states here that are not referenced in the spec text - uncached and updateready. uncached is never mentioned in the text except in the IDL. updateready is mentioned as an event but appears nowhere as a status.
Comment 1 Ian 'Hixie' Hickson 2009-09-29 07:45:39 UTC 
I don't understand where you would want them to appear... they are defined, and used for the value of the "status" attribute:

   http://www.whatwg.org/specs/web-apps/current-work/#dom-appcache-status

What more is needed?
Comment 2 Nikunj Mehta 2009-09-29 16:16:52 UTC 
A result of application cache being distinct from ApplicationCache