- From: <bugzilla@wiggum.w3.org>
- Date: Tue, 05 Jan 2010 07:31:12 +0000
- To: public-html-bugzilla@w3.org
http://www.w3.org/Bugs/Public/show_bug.cgi?id=8256 Ian 'Hixie' Hickson <ian@hixie.ch> changed: What |Removed |Added ---------------------------------------------------------------------------- Status|NEW |RESOLVED Resolution| |WONTFIX --- Comment #2 from Ian 'Hixie' Hickson <ian@hixie.ch> 2010-01-05 07:31:12 --- 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: Rejected Change Description: no spec change Rationale: The answer is "both"; it starts off synchronous, and goes "into the background" later. The spec seems well-defined already. When submit() is invoked, the submission algorithm is invoked, which means running through a bunch of steps, and which ends with calling the Navigate algorithm, which itself runs through a bunch of steps, including some that switch to being asynchronous. I don't really see what needs clarifying. Just walk through the steps in the spec and it all just falls out, as far as I can tell. -- 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, 5 January 2010 07:31:14 UTC