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 7972 - 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.
Summary: It appears that the steps listed for what to do when reset() is invoked conta...
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-10-20 03:18 UTC by contributor
Modified: 2010-10-04 14:49 UTC (History)
4 users (show)

See Also:

Attachments

Description contributor 2009-10-20 03:18:47 UTC 
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
Comment 1 Ian 'Hixie' Hickson 2009-10-21 11:26:08 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 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.