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 9482 - appcache: listing multiple manifests in manifest="", or inclusions in appcache manifest files
Summary: appcache: listing multiple manifests in manifest="", or inclusions in appcach...
Status: RESOLVED WONTFIX
Alias: None
Product: WHATWG
Classification: Unclassified
Component: HTML (show other bugs)
Version: unspecified
Hardware: Other other
: P3 enhancement
Target Milestone: Unsorted
Assignee: Ian 'Hixie' Hickson
QA Contact: HTML WG Bugzilla archive list
URL: https://www.w3.org/Bugs/Public/show_b...
Whiteboard:
Keywords:
: 10206 (view as bug list)
Depends on:
Blocks:
 
Reported: 2010-04-10 23:12 UTC by contributor
Modified: 2014-09-25 23:00 UTC (History)
5 users (show)

See Also:

Attachments

Description contributor 2010-04-10 23:12:15 UTC 
Section: http://www.whatwg.org/specs/web-apps/current-work/#attr-html-manifest

Comment:
multi-manifest R needed. The URLs can be separated with a common(manifest
="content.manifest,structure.manifest,scripts.manifest"). Having more then one
manifest cache file would allow separation control of cache. Many websites and
apps can use multi-manifest to create better unnecessary reCasheing of urls in
a single manifest file. This would have great benefits on lowing net traffic,
server load, and the user agent load. Possible eliminating a power-plant or
two of world energy demand. Robert from zoshe.com

Posted from: 67.80.231.240
Comment 1 Ian 'Hixie' Hickson 2010-04-13 08:28:20 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: This is something that would make sense to investigate in a future version, but for now we should keep this simple to see if browsers can reliably implement it.
Comment 2 public-rdfa-wg 2013-01-24 06:51:11 UTC 
This bug was cloned to create HTML WG bug 19048.
Comment 3 Ian 'Hixie' Hickson 2013-03-18 22:57:41 UTC 
We should delay this until after we've worked on the new system, to see if this gets obsoleted by it.
Comment 4 Ian 'Hixie' Hickson 2013-03-19 23:26:29 UTC 
*** Bug 10206 has been marked as a duplicate of this bug. ***
Comment 5 Ian 'Hixie' Hickson 2014-09-25 23:00:54 UTC 
ServiceWorkers will handle this.