[Webkit-unassigned] [Bug 5926] Assertion failure in HTMLGenericFormElementImpl::removedFromTree

bugzilla-daemon at opendarwin.org bugzilla-daemon at opendarwin.org
Tue Dec 27 13:34:03 PST 2005


------- Additional Comments From opendarwin.org at mitzpettel.com  2005-12-27 13:34 -------
Created an attachment (id=5307)
 --> (http://bugzilla.opendarwin.org/attachment.cgi?id=5307&action=view)
Reduced testcase that triggers the assert even with the patch

This is different from the previous reduction, in that in this case, the input
element ends up belonging to form B, even though it isn't a descendant of form
B. That's also what Firefox thinks should happen.

However, if the input element were programatically inserted at the same place,
then getForm() would be used and it would end up belonging to its ancestor,
form A. Firefox says so too.

I see four options:
1) Decide that the above (Firefox-compatible) behavior is correct, and remove
the assert.
2) Decide that the above (Firefox-compatible) behavior is correct, add have the
parser set some flag(s) on the inputElement to bypass the assert in this
special case.
3) Decide that the above logic is incorrect, and change getForm() to answer
"which form would the parser associate this input element with if it were here
in the first place" (if the question has meaning, and if it's even possible to
answer, it probably involves traversing the entire DOM tree).
4) Decide that the above logic is incorrect, and an input element's form should
always be its ancestor.

Configure bugmail: http://bugzilla.opendarwin.org/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are the assignee for the bug, or are watching the assignee.

More information about the webkit-unassigned mailing list