- From: <bugzilla@jessica.w3.org>
- Date: Tue, 14 Jun 2011 07:41:02 +0000
- To: public-html-bugzilla@w3.org
http://www.w3.org/Bugs/Public/show_bug.cgi?id=12289 Ian 'Hixie' Hickson <ian@hixie.ch> changed: What |Removed |Added ---------------------------------------------------------------------------- Status|NEW |RESOLVED Resolution| |NEEDSINFO --- Comment #2 from Ian 'Hixie' Hickson <ian@hixie.ch> 2011-06-14 07:41:01 UTC --- EDITOR'S RESPONSE: This is an Editor's Response to your comment. If you are satisfied with this response, please change the state of this bug to CLOSED. If you have additional information and would like the editor to reconsider, please reopen this bug. If you would like to escalate the issue to the full HTML Working Group, please add the TrackerRequest keyword to this bug, and suggest title and text for the tracker issue; or you may create a tracker issue yourself, if you are able to do so. For more details, see this document: http://dev.w3.org/html5/decision-policy/decision-policy.html Status: Did Not Understand Request Change Description: no spec change Rationale: I don't understand. Could you elaborate? As far as I can tell in the spec, 'suspend' is only fired in one situation, which is when the download is suspended. I guess technically a browser could decide to not download any more content at the same time as it has received the last byte but before realising it, but that's a pretty obscure edge case that doesn't seem worth mentioning in the non-normative summary table. -- 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 Tuesday, 14 June 2011 07:41:09 UTC