- From: Ian Hickson <ian@hixie.ch>
- Date: Wed, 13 Jan 2010 01:35:29 +0000 (UTC)
On Thu, 17 Dec 2009, Joseph Pecoraro wrote: > > > > We could delay the application cache download process so that it > > doesn't start until after the 'load' event has fired. Does anyone have > > an opinion on this? > > It seems pointless to provide hooks in the API that allow for a "custom > interface", when fundamentally they may never be triggered in an > otherwise compliant user agent. On Thu, 17 Dec 2009, Michael Nordman wrote: > > I don't think we'd have to delay the update job, just the delivery of > any events associated with the appcache until 'load' has happened to get > the desired effect. On Fri, 18 Dec 2009, Anne van Kesteren wrote: > > I believe we (Opera) found this is what at least some implementations > are doing now and we do this as well. What Michael suggested makes sense > and I suppose as the effects are indistinguishable in the end that > (delaying either the events or the download process) should be fine. Done. All the events fired during the update process are delayed if the Document whose ApplicationCache they are targetting hasn't loaded yet. -- Ian Hickson U+1047E )\._.,--....,'``. fL http://ln.hixie.ch/ U+263A /, _.. \ _\ ;`._ ,. Things that are impossible just take longer. `._.-(,_..'--(,_..'`-.;.'
Received on Tuesday, 12 January 2010 17:35:29 UTC