17831 2012-07-18 06:58:08 +0000 Form-associated elements with non-ancestor form owners should be reset when owner is removed from the tree 2012-09-26 22:09:48 +0000 1 1 1 Unclassified WHATWG HTML unspecified Other other RESOLVED WORKSFORME P3 normal Unsorted 1 contributor ian adamk ian mike tkent contributor oldest_to_newest 70132 0 contributor 2012-07-18 06:58:08 +0000 This was was cloned from bug 16394 as part of operation convergence. Originally filed: 2012-03-15 23:52:00 +0000 Original reporter: Adam Klein <adamk@chromium.org> ================================================================================ #0 Adam Klein 2012-03-15 23:52:11 +0000 -------------------------------------------------------------------------------- Created attachment 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. ================================================================================ 74593 1 ian 2012-09-26 22:05:48 +0000 adamk: Why isn't this handled by "When an element is removed from a Document resulting in a form-associated element and its form owner (if any) no longer being in the same home subtree, then the user agent must reset the form owner of that form-associated element." ? 74594 2 adamk 2012-09-26 22:09:48 +0000 (In reply to comment #1) > adamk: Why isn't this handled by "When an element is removed from a Document > resulting in a form-associated element and its form owner (if any) no longer > being in the same home subtree, then the user agent must reset the form owner > of that form-associated element." ? You're right, that takes care of it (marking as resolved). I think I must have missed how that sentence opens: "When an element..." rather than "When a form-associated element..." (as the rest of the sentences in that section do).