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 9339 - " Until the manifest is changed, those pages will not be fetched from the server again." WHAAAA? In order to get the benefits of app cached images and scripts and css, I have to have HTML pages that are never updated with fresh info, except when I change
Summary: " Until the manifest is changed, those pages will not be fetched from the ser...
Status: RESOLVED NEEDSINFO
Alias: None
Product: HTML WG
Classification: Unclassified
Component: pre-LC1 HTML5 spec (editor: Ian Hickson) (show other bugs)
Version: unspecified
Hardware: Other other
: P3 normal
Target Milestone: LC
Assignee: Ian 'Hixie' Hickson
QA Contact: HTML WG Bugzilla archive list
URL: http://www.whatwg.org/specs/web-apps/...
Whiteboard:
Keywords:
Depends on:
Blocks:
 
Reported: 2010-03-26 15:17 UTC by contributor
Modified: 2010-10-04 14:28 UTC (History)
4 users (show)

See Also:

Attachments

Description contributor 2010-03-26 15:17:37 UTC 
Section: http://www.whatwg.org/specs/web-apps/current-work/#a-sample-manifest

Comment:
" Until the manifest is changed, those pages will not be fetched from the
server again." WHAAAA? In order to get the benefits of app cached images and
scripts and css, I have to have HTML pages that are never updated with fresh
info, except when I change the manifest, and then everything is updated?
That's just crazy!!

Posted from: 67.188.133.45
Comment 1 Ian 'Hixie' Hickson 2010-04-02 06:10:34 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: Did Not Understand Request
Change Description: no spec change
Rationale: I don't understand. Could you elaborate? The offline application cache mechanism is intended for caching offline applications, where the dynamic data is data, not in the HTML. If all you want is to benefit from caching of common resources, you don't need this, just use HTTP caching.