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 7684 - ApplicationCache object can be empty but not an application cache
Summary: ApplicationCache object can be empty but not an application cache
Status: CLOSED INVALID
Alias: None
Product: HTML WG
Classification: Unclassified
Component: pre-LC1 HTML5 spec (editor: Ian Hickson) (show other bugs)
Version: unspecified
Hardware: All 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:00 UTC by Nikunj Mehta
Modified: 2010-10-04 14:45 UTC (History)
4 users (show)

See Also:

Attachments

Description Nikunj Mehta 2009-09-21 17:00:38 UTC 
Overview:
By definition an application cache has to have at least one resource. However, when an ApplicationCache object is fetched it could be empty, i.e., not have any resources.

Steps to reproduce:

1. Create an HTML document without a manifest="" attribute
2. In an onload script, get the value of window.applicationCache 

Actual results:

1. an ApplicationCache object with no items

The spec text containing definition of application cache should be changed to allow empty application cache.
Comment 1 Ian 'Hixie' Hickson 2009-09-29 07:44:16 UTC 
There's no application cache in that example. The ApplicationCache object would have its status attribute set to UNCACHED.
Comment 2 Nikunj Mehta 2009-09-29 16:17:25 UTC 
A result of application cache being distinct from ApplicationCache