7972 2009-10-20 03:18:47 +0000 It appears that the steps listed for what to do when reset() is invoked contain a race condition unless step 1 (checking if already marked) and step 2 (marking the form as locked) are performed atomically together. 2010-10-04 14:49:01 +0000 1 1 1 Unclassified HTML WG pre-LC1 HTML5 spec (editor: Ian Hickson) unspecified Other other RESOLVED WONTFIX http://www.whatwg.org/specs/web-apps/current-work/#the-form-element NE P3 normal LC 1 contributor ian ian mike public-html-admin public-html-wg-issue-tracking public-html-bugzilla oldest_to_newest 28533 0 contributor 2009-10-20 03:18:47 +0000 Section: http://www.whatwg.org/specs/web-apps/current-work/#the-form-element Comment: It appears that the steps listed for what to do when reset() is invoked contain a race condition unless step 1 (checking if already marked) and step 2 (marking the form as locked) are performed atomically together. Posted from: 149.159.142.23 28748 1 ian 2009-10-21 11:26:08 +0000 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 whole thing is running synchronously in the event loop, so there can't ever be anything racing against it as far as I can tell.