15704 2012-01-25 03:27:16 +0000 HTMLFormElement::elements broken for forms outside a document 2012-05-07 23:47:52 +0000 1 1 1 Unclassified HTML WG HTML5 spec unspecified All All RESOLVED FIXED P2 normal --- 1 tkent ian adamk ian mike Ms2ger mtanalin public-html-admin public-html-wg-issue-tracking public-html-bugzilla oldest_to_newest 63092 0 tkent 2012-01-25 03:27:16 +0000 http://dev.w3.org/html5/spec/Overview.html#dom-form-elements > The elements IDL attribute must return an HTMLFormControlsCollection rooted at the Document node, whose filter matches listed elements whose form owner is the form element, ... The specification says "rooted at the Document", so ::elements fo a <form> not in the document tree should be empty. However, IE, Firefox, Opera, and WebKit return non-empty collections for ::elements. <script> var f1 = document.createElement('form'); f1.appendChild(document.createElement('input')); alert(f1.elements.length); </script> This code alerts '1' with major browsers though it should be '0' because <input> is not in the Document tree. I personally like the current definition of the specification, but it's not compatible. 63096 1 mtanalin 2012-01-25 11:22:48 +0000 I tend to consider current implementations' behavior more correct. A form contains its elements regardless of whether the form is attached to document. So probably "rooted at the Document node" part (which is both unreasonable and inconsistent with implementations) should be just removed from the spec. 65524 2 ian 2012-03-14 17:05:18 +0000 We could also say that orphan nodes or nodes in orphan subtrees shouldn't be associated. 65545 3 mtanalin 2012-03-14 18:16:33 +0000 (In reply to comment #2) For me, purpose and conclusion of this comment are unclear. Could you be more informative and verbose? 65652 4 tkent 2012-03-16 06:24:28 +0000 (In reply to comment #2) > We could also say that orphan nodes or nodes in orphan subtrees shouldn't be > associated. Yeah, it would be very simple, and I like it. But it's not compatible with existing browsers, and I'm afraid it will break existing web sites. If we changed the specification to match the existing browsers, the spec would be: ... return an HTMLFormControlCollection rooted at the Document node if the form element is in the document tree, otherwise return an HTMLFormControlCollection rooted at the form element, ... because we need to handle form controls with 'form' content attributes. 67436 5 ian 2012-05-07 22:33:21 +0000 looks like we need to reset the form owner of everyone in the form if the form's ancestor chain changes. 67440 6 ian 2012-05-07 23:31:58 +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: Accepted Change Description: see diff given below Rationale: Concurred with reporter's comments. 67441 7 contributor 2012-05-07 23:32:17 +0000 Checked in as WHATWG revision r7093. Check-in comment: Try to match implementations better. http://html5.org/tools/web-apps-tracker?from=7092&to=7093 67443 8 contributor 2012-05-07 23:47:52 +0000 Checked in as WHATWG revision r7094. Check-in comment: Try to match implementations better. http://html5.org/tools/web-apps-tracker?from=7093&to=7094