- From: <bugzilla@jessica.w3.org>
- Date: Thu, 15 Mar 2012 23:52:11 +0000
- To: public-html-bugzilla@w3.org
https://www.w3.org/Bugs/Public/show_bug.cgi?id=16394 Summary: Form-associated elements with non-ancestor form owners should be reset when owner is removed from the tree 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: adamk@chromium.org QAContact: public-html-bugzilla@w3.org CC: mike@w3.org, public-html-wg-issue-tracking@w3.org, public-html@w3.org Created attachment 1102 --> https://www.w3.org/Bugs/Public/attachment.cgi?id=1102 Test case In http://www.whatwg.org/specs/web-apps/current-work/multipage/association-of-controls-and-forms.html#attr-fae-form, I think a new line ought to be added to the rules governing when the form owner must be reset. Something on the order of: "When a tree containing a form-associated element and its form owner changes such that they are no longer in the same tree, reset the form owner of that element" This is to handle the case where the parser has caused a form control to be owned by a form which is not an ancestor. When that non-ancestor form is removed from the document, the form owner ought to be reset. It's not currently in WebKit (though after a GC it _is_ reset), but is in Firefox and Opera. Test case attached. -- 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 Thursday, 15 March 2012 23:52:15 UTC