- From: <bugzilla@jessica.w3.org>
- Date: Fri, 16 Mar 2012 06:42:56 +0000
- To: public-html-bugzilla@w3.org
https://www.w3.org/Bugs/Public/show_bug.cgi?id=16399
Summary: 'reset the form owner' algorithm issue
Product: HTML WG
Version: unspecified
Platform: All
OS/Version: All
Status: NEW
Severity: normal
Priority: P2
Component: HTML5 spec (editor: Ian Hickson)
AssignedTo: ian@hixie.ch
ReportedBy: tkent@chromium.org
QAContact: public-html-bugzilla@w3.org
CC: mike@w3.org, public-html-wg-issue-tracking@w3.org,
public-html@w3.org
http://www.whatwg.org/specs/web-apps/current-work/multipage/association-of-controls-and-forms.html#reset-the-form-owner
If we follow this algorithm, a form control which is not in a document tree AND
not in any form orphan tree can be associated to a form element.
Example:
<html>
<body>
<form id=f1>
</form>
<script>
var input1 = document.createElement('input'); // form owner is null.
input1.setAttribute('form', 'f1'); // Need 'reset the form owner'.
// The owner form of input1 should be f1 according to the specification.
// f1.elements should contain input1, but document-order is undefined for
input1.
</script>
Proposal:
Fix the following sentence:
3. If the element has a form content attribute, then run these substeps:
==>
3. If the element has a form content attribute and is in a Document subtree,
then run these substeps:
--
Configure bugmail: https://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 Friday, 16 March 2012 06:42:58 UTC