- From: Ian Hickson <ian@hixie.ch>
- Date: Sun, 10 Jan 2010 04:18:22 +0000 (UTC)
On Sat, 9 Jan 2010, Joseph Pecoraro wrote: > > > On Thu, 17 Dec 2009 22:44:01 +0100, Ian Hickson <ian at hixie.ch> 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? > > On Dec 17, 2009, at 5: 24PM, 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 Dec 18, 2009, at 7: 51AM, 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. > > Mike's suggestion sounds good. > > Is this in the queue to be added or could this have been forgotten about? > There was a change around the time this email thread occurred that > clarified that the download process should be performed in the > background, but nothing about the events. It's in the queue -- sorry for the delay in answering e-mails; I'm trying to get through the W3C HTML WG Bugzilla queue first, and that is taking longer than I expected. -- Ian Hickson U+1047E )\._.,--....,'``. fL http://ln.hixie.ch/ U+263A /, _.. \ _\ ;`._ ,. Things that are impossible just take longer. `._.-(,_..'--(,_..'`-.;.'
Received on Saturday, 9 January 2010 20:18:22 UTC