- From: <bugzilla@jessica.w3.org>
- Date: Tue, 02 Nov 2010 20:06:03 +0000
- To: public-html-bugzilla@w3.org
http://www.w3.org/Bugs/Public/show_bug.cgi?id=11201 Summary: 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 Product: HTML WG Version: unspecified Platform: Other URL: http://www.whatwg.org/specs/web-apps/current-work/#top OS/Version: other Status: NEW Severity: normal Priority: P3 Component: HTML5 spec (editor: Ian Hickson) AssignedTo: ian@hixie.ch ReportedBy: contributor@whatwg.org QAContact: public-html-bugzilla@w3.org CC: mike@w3.org, public-html-wg-issue-tracking@w3.org, public-html@w3.org 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 -- 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 Tuesday, 2 November 2010 20:06:04 UTC