W3C home > Mailing lists > Public > public-html-bugzilla@w3.org > July 2012

[Bug 17688] New: Specification should be clearer about when the downloading of the application cache starts. "These events are delayed until after the load event has fired." is a bit misleading. The chrome developer team interprets it as: Start downloading all resources f

From: <bugzilla@jessica.w3.org>
Date: Wed, 04 Jul 2012 08:39:43 +0000
To: public-html-bugzilla@w3.org
Message-ID: <bug-17688-2486@http.www.w3.org/Bugs/Public/>
https://www.w3.org/Bugs/Public/show_bug.cgi?id=17688

           Summary: Specification should be clearer about when the
                    downloading of the application cache starts. "These
                    events are delayed until after the load event has
                    fired." is a bit misleading. The chrome developer team
                    interprets it as: Start downloading all resources f
           Product: HTML WG
           Version: unspecified
          Platform: Other
               URL: http://www.whatwg.org/specs/web-apps/current-work/#dow
                    nloading-or-updating-an-application-cache
        OS/Version: other
            Status: NEW
          Severity: normal
          Priority: P3
         Component: other Hixie drafts (editor: Ian Hickson)
        AssignedTo: ian@hixie.ch
        ReportedBy: contributor@whatwg.org
         QAContact: public-html-bugzilla@w3.org
                CC: mike@w3.org


Specification:
http://www.whatwg.org/specs/web-apps/current-work/multipage/offline.html
Multipage: http://www.whatwg.org/C#downloading-or-updating-an-application-cache
Complete: http://www.whatwg.org/c#downloading-or-updating-an-application-cache

Comment:
Specification should be clearer about when the downloading of the application
cache starts. "These events are delayed until after the load event has fired."
is a bit misleading. The chrome developer team interprets it as: Start
downloading all resources from the manifest file as soon as the page loads,
but just delay the events until onload event has been fired. The Firefox team
is actually delaying the download of all resources from the manifest file
until the onload event has been fired. Outcome in Chrome: Delay between
ondownloading and oncache event is minimal(in my testcase 34ms) and in firefox
the actual time it took to download all resources. Chromes approach makes
these events basically useless, because they are almost at the same time and
appcaching is not cancelable. With a better specification, this issue could be
solved.

Posted from: 90.146.74.58 by simon.schatka@compuware.com
User agent: Mozilla/5.0 (Windows NT 6.1; WOW64) AppleWebKit/536.11 (KHTML, like
Gecko) Chrome/20.0.1132.47 Safari/536.11

-- 
Configure bugmail: https://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 Wednesday, 4 July 2012 08:39:44 GMT

This archive was generated by hypermail 2.2.0+W3C-0.50 : Wednesday, 4 July 2012 08:39:45 GMT