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 8256 - [gs] Is form.submit() async or sync? I don't see where this is defined. From my reading it should be sync, as it should just run the steps to completion.
Summary: [gs] Is form.submit() async or sync? I don't see where this is defined. From ...
Status: RESOLVED WONTFIX
Alias: None
Product: HTML WG
Classification: Unclassified
Component: pre-LC1 HTML5 spec (editor: Ian Hickson) (show other bugs)
Version: unspecified
Hardware: Other other
: P3 normal
Target Milestone: LC
Assignee: Ian 'Hixie' Hickson
QA Contact: HTML WG Bugzilla archive list
URL: http://www.whatwg.org/specs/web-apps/...
Whiteboard:
Keywords: NE
Depends on:
Blocks:
 
Reported: 2009-11-10 16:43 UTC by contributor
Modified: 2010-10-04 13:59 UTC (History)
6 users (show)

See Also:

Attachments

Description contributor 2009-11-10 16:43:20 UTC 
Section: http://www.whatwg.org/specs/web-apps/current-work/#the-form-element

Comment:
[gs] Is form.submit() async or sync? I don't see where this is defined. From my reading it should be sync, as it should just run the steps to completion.

Posted from: 88.131.66.80
Comment 1 Geoffrey Sneddon 2009-11-10 17:59:29 UTC 
It's async in Opera, Firefox, and Chromium. The spec should probably make it clear this should be async.
Comment 2 Ian 'Hixie' Hickson 2010-01-05 07:31:12 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: 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.