[Bug 13167] Using an existing application cache without having a master entry in the application group (cache the master entry)

http://www.w3.org/Bugs/Public/show_bug.cgi?id=13167

Ian 'Hixie' Hickson <ian@hixie.ch> changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
             Status|NEW                         |RESOLVED
                 CC|                            |ian@hixie.ch
         Resolution|                            |WONTFIX

--- Comment #2 from Ian 'Hixie' Hickson <ian@hixie.ch> 2011-08-09 21:52:33 UTC ---
EDITOR'S RESPONSE: This is an Editor's Response to your comment. If you are
satisfied with this response, please change the state of this bug to CLOSED. If
you have additional information and would like the editor to reconsider, please
reopen this bug. If you would like to escalate the issue to the full HTML
Working Group, please add the TrackerRequest keyword to this bug, and suggest
title and text for the tracker issue; or you may create a tracker issue
yourself, if you are able to do so. For more details, see this document:
   http://dev.w3.org/html5/decision-policy/decision-policy.html

Status: Rejected
Change Description: no spec change
Rationale: 

There's a simple way to do it: list the file in the manifest and give it a
manifest="" attribute pointing to the manifest.

We can't just fetch the file from the network then use the files from the
cache, because the files from the cache could be a year old by the time the
user goes to the page, and in that case the page is highly likely to completely
break if it's fetched in this way. This is a problem with FALLBACK-enabled
resources also, but there's no obvious workaround for those cases.

-- 
Configure bugmail: http://www.w3.org/Bugs/Public/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are the QA contact for the bug.

Received on Tuesday, 9 August 2011 21:52:39 UTC