W3C home > Mailing lists > Public > public-html-bugzilla@w3.org > August 2011

[Bug 13168] Creating or using an existing application cache without caching the master entry

From: <bugzilla@jessica.w3.org>
Date: Wed, 10 Aug 2011 00:52:08 +0000
To: public-html-bugzilla@w3.org
Message-Id: <E1Qqx1k-00046j-Qg@jessica.w3.org>
http://www.w3.org/Bugs/Public/show_bug.cgi?id=13168

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-10 00:52:07 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: If you don't need the page to be accessible while offline, which you
presumably don't in the given use case, then using a manifest is pointless: you
can just rely on the regular HTTP cache.

-- 
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 Wednesday, 10 August 2011 00:52:14 UTC

This archive was generated by hypermail 2.3.1 : Wednesday, 7 January 2015 16:31:16 UTC