- From: <bugzilla@wiggum.w3.org>
- Date: Thu, 01 Oct 2009 13:23:03 +0000
- To: public-html-bugzilla@w3.org
http://www.w3.org/Bugs/Public/show_bug.cgi?id=7783
Summary: appcache download events
Product: HTML WG
Version: unspecified
Platform: PC
OS/Version: Linux
Status: NEW
Severity: normal
Priority: P2
Component: HTML5 spec bugs
AssignedTo: dave.null@w3.org
ReportedBy: annevk@opera.com
QAContact: public-html-bugzilla@w3.org
CC: ian@hixie.ch, mike@w3.org, public-html@w3.org
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?
--
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 Thursday, 1 October 2009 13:23:06 UTC