7783 2009-10-01 13:23:03 +0000 appcache download events 2010-10-04 14:49:02 +0000 1 1 1 Unclassified HTML WG pre-LC1 HTML5 spec (editor: Ian Hickson) unspecified PC Linux RESOLVED WONTFIX NE P2 normal --- 1 annevk ian ian mike public-html-admin public-html-wg-issue-tracking public-html-bugzilla oldest_to_newest 27969 0 annevk 2009-10-01 13:23:03 +0000 Why is there first an event called downloading while the progress events seem sufficient to determine everything? If we need downloading, wouldn't it be better to provide a networking API similar to media elements and XMLHttpRequest. I.e. with loadstart, progress, error/abort/load, and loadend? 28485 1 ian 2009-10-18 23:05:21 +0000 '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.