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 11201 - Hi there, Reading through the HTML5 Offline spec at http://dev.w3.org/html5/spec/offline.html , the spec is not clear on what should happen if the manifest attribute of the html tag is modified during/after the document has loaded. eg, if Javascript is u
Summary: Hi there, Reading through the HTML5 Offline spec at http://dev.w3.org/html5/s...
Status: RESOLVED WORKSFORME
Alias: None
Product: HTML WG
Classification: Unclassified
Component: LC1 HTML5 spec (show other bugs)
Version: unspecified
Hardware: Other other
: P3 normal
Target Milestone: ---
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-11-02 20:06 UTC by contributor
Modified: 2011-08-04 05:17 UTC (History)
4 users (show)

See Also:

Attachments

Description contributor 2010-11-02 20:06:02 UTC 
Specification: http://dev.w3.org/html5/spec/spec.html
Section: http://www.whatwg.org/specs/web-apps/current-work/#top

Comment:
Hi there,

Reading through the HTML5 Offline spec at
http://dev.w3.org/html5/spec/offline.html , the spec is not clear on what
should happen if the manifest attribute of the html tag is modified
during/after the document has loaded.  eg, if Javascript is used during/after
page load to manipulate the manifest attribute using eg
document.getElementsByTagName("html")[0].setAttribute("manifest",
"offline.manifest");  should the browser start firing the 'checking' event and
run through the application cache download process?  Should it ignore it? 
Currently, different browser vendors have different behaviour for this action
and I believe there should be efforts to standardise it.  Personally, I
believe that the browser should be required to start the application cache
download process as soon as the manifest attribute is changed.

Cheers,
Eion

Posted from: 210.54.239.100
Comment 1 Ms2ger 2010-11-03 07:43:34 UTC 
> The manifest attribute only has an effect during the early stages of document
> load. Changing the attribute dynamically thus has no effect (and thus, no DOM
> API is provided for this attribute).
Comment 2 Michael[tm] Smith 2011-08-04 05:17:17 UTC 
mass-move component to LC1