- From: <bugzilla@jessica.w3.org>
- Date: Thu, 16 Jun 2011 06:53:45 +0000
- To: public-html-bugzilla@w3.org
http://www.w3.org/Bugs/Public/show_bug.cgi?id=12967 Summary: I feel this part is not clear enough. When should the developers call update()? Should they call update() before swapCache()? Must swapCache() be called before reload? I've tried that even without calling swapCache(), once manifest changed, the file will Product: HTML WG Version: unspecified Platform: Other URL: http://www.whatwg.org/specs/web-apps/current-work/#app lication-cache-api 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://www.whatwg.org/specs/web-apps/current-work/multipage/offline.html Section: http://www.whatwg.org/specs/web-apps/current-work/#application-cache-api Comment: I feel this part is not clear enough. When should the developers call update()? Should they call update() before swapCache()? Must swapCache() be called before reload? I've tried that even without calling swapCache(), once manifest changed, the file will get updated after a reload. Posted from: 2620:0:10a0:2:3451:c06d:3bea:9c69 User agent: Mozilla/5.0 (Windows NT 6.1; WOW64) AppleWebKit/535.1 (KHTML, like Gecko) Chrome/13.0.782.24 Safari/535.1 -- 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 Thursday, 16 June 2011 06:53:48 UTC