W3C home > Mailing lists > Public > public-html-bugzilla@w3.org > October 2009

[Bug 7783] appcache download events

From: <bugzilla@wiggum.w3.org>
Date: Sun, 18 Oct 2009 23:05:21 +0000
To: public-html-bugzilla@w3.org
Message-Id: <E1MzeoT-0004qF-N4@wiggum.w3.org>
http://www.w3.org/Bugs/Public/show_bug.cgi?id=7783


Ian 'Hixie' Hickson <ian@hixie.ch> changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
             Status|NEW                         |RESOLVED
         Resolution|                            |WONTFIX




--- Comment #1 from Ian 'Hixie' Hickson <ian@hixie.ch>  2009-10-18 23:05:21 ---
'downloading' is separate from 'progress' so that you don't have to continually
check whether or not you've gotten the first 'progress' yet. You just have one
event to set up your progress bar (or whatever), and others to update it.

The events you list aren't used because they're not fine-grained enough. What
would be 'loadstart' is split between 'checking' and 'downloading', what would
be the various ending events is split between 'noupdate', 'cached',
'updateready', 'obsolete', and 'error'. I reused the event names that made
sense, and made new ones up elsewhere.


-- 
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 Sunday, 18 October 2009 23:05:23 GMT

This archive was generated by hypermail 2.2.0+W3C-0.50 : Sunday, 18 October 2009 23:05:23 GMT