This is an archived snapshot of W3C's public bugzilla bug tracker, decommissioned in April 2019. Please see the home page for more details.

Bug 7783 - appcache download events
Summary: appcache download events
Alias: None
Product: HTML WG
Classification: Unclassified
Component: pre-LC1 HTML5 spec (editor: Ian Hickson) (show other bugs)
Version: unspecified
Hardware: PC Linux
: P2 normal
Target Milestone: ---
Assignee: Ian 'Hixie' Hickson
QA Contact: HTML WG Bugzilla archive list
Keywords: NE
Depends on:
Reported: 2009-10-01 13:23 UTC by Anne
Modified: 2010-10-04 14:49 UTC (History)
4 users (show)

See Also:


Description Anne 2009-10-01 13:23:03 UTC
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?
Comment 1 Ian 'Hixie' Hickson 2009-10-18 23:05:21 UTC
'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.