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 10206 - A single manifest file pre page will be problematic for web authoring programmers like myself, and Lib developers like jQuery. It will cause all types of problems with mash-ups of various providers of web apps on a single page. Can U please consider addin
Summary: A single manifest file pre page will be problematic for web authoring program...
Status: RESOLVED DUPLICATE of bug 9482
Alias: None
Product: WHATWG
Classification: Unclassified
Component: HTML (show other bugs)
Version: unspecified
Hardware: Other other
: P3 normal
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:
Depends on:
Blocks:
 
Reported: 2010-07-20 06:09 UTC by contributor
Modified: 2013-03-19 23:26 UTC (History)
5 users (show)

See Also:

Attachments

Description contributor 2010-07-20 06:09:05 UTC 
Section: http://www.whatwg.org/specs/web-apps/current-work/#offline

Comment:
A single manifest file pre page will be problematic for web authoring
programmers like myself, and Lib developers like jQuery. It will cause all
types of problems with mash-ups of various providers of web apps on a single
page. Can U please consider adding to the HTML5 spec the ability to allow for
more than one manifest file per page. It could follow the same logic of using
multi css files. (filed for Robert Stack)

Posted from: 98.248.33.53 by ian@hixie.ch
Comment 1 Ian 'Hixie' Hickson 2010-09-08 06:44:03 UTC 
Seems like a reasonable thing to consider for v2, if we decide the manifest feature is worth keeping.

In the meantime, you can work around this using iframes, I believe.


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: Marking LATER for now, as per comments above.
Comment 2 Michael[tm] Smith 2013-01-24 07:51:28 UTC 
This bug was cloned to create HTML WG bug 19021.
Comment 3 Ian 'Hixie' Hickson 2013-03-19 23:26:29 UTC 

*** This bug has been marked as a duplicate of bug 9482 ***