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 16394 - Form-associated elements with non-ancestor form owners should be reset when owner is removed from the tree
Summary: Form-associated elements with non-ancestor form owners should be reset when o...
Status: RESOLVED WORKSFORME
Alias: None
Product: HTML WG
Classification: Unclassified
Component: HTML5 spec (show other bugs)
Version: unspecified
Hardware: All All
: P2 normal
Target Milestone: ---
Assignee: Edward O'Connor
QA Contact: HTML WG Bugzilla archive list
URL:
Whiteboard:
Keywords:
Depends on:
Blocks:
 
Reported: 2012-03-15 23:52 UTC by Adam Klein
Modified: 2012-10-02 23:20 UTC (History)
5 users (show)

See Also:


Attachments
Test case (235 bytes, text/html)
2012-03-15 23:52 UTC, Adam Klein
Details

Description Adam Klein 2012-03-15 23:52:11 UTC
Created attachment 1102 [details]
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.
Comment 1 contributor 2012-07-18 06:58:12 UTC
This bug was cloned to create bug 17831 as part of operation convergence.
Comment 2 Edward O'Connor 2012-10-02 23:20:59 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: As described in <https://www.w3.org/Bugs/Public/show_bug.cgi?id=17831#c1>, the spec already does this.