- From: <bugzilla@wiggum.w3.org>
- Date: Thu, 01 Oct 2009 13:43:01 +0000
- To: public-html-bugzilla@w3.org
http://www.w3.org/Bugs/Public/show_bug.cgi?id=7784
Summary: "cache failure steps" feedback
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
Should the status be changed before dispatching the error event? That would be
more consistent with when the checking and downloading events are dispatched.
(I also get the feeling it would have been better if we had separate states for
networking and the cache, but I guess that is not going to work at this point.)
It would be nice to have a note at step 7 ("If this was a cache attempt,
discard cache group altogether.") that indicates this will change the state of
the object the API talks against to UNCACHED.
--
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:43:02 UTC