W3C home > Mailing lists > Public > public-html-bugzilla@w3.org > October 2009

[Bug 7978] Form foster parenting introduces extra space to layout

From: <bugzilla@wiggum.w3.org>
Date: Mon, 26 Oct 2009 14:52:29 +0000
To: public-html-bugzilla@w3.org
Message-Id: <E1N2Qvt-00089N-Iy@wiggum.w3.org>

--- Comment #11 from Simon Pieters <simonp@opera.com>  2009-10-26 14:52:29 ---
(In reply to comment #9)
> So I'm trying to understand the change linked to in comment 6.  What behavior
> does it give for the following document:
>   <body>
>     <table>
>       <form><tr><td><input name="one"></td></tr></form>
>       <form><tr><td><input name="two"></td></tr></form>
>     </table>
>     <input name="three">
>     <form><input name="four"></form>
>     <input name="five">
>   </body>
> ?  What does the DOM look like?

Like this XML:

       <form/><tbody><tr><td><input name="one"/></td></tr>
       <form/><tr><td><input name="two"/></td></tr>
     <input name="three"/>
     <form><input name="four"/></form>
     <input name="five"/>

> Which input is associated with which form?

Same as before. "three" and "five" aren't associated with any form; "one",
"two" and "four" are associated with the form you'd expect.

> How does that compare to what UAs do currently?


In this case it seems to match old Gecko, WebKit and Opera (even though Opera
has a different strategy for dealing with forms in tables currently). The
association should match IE, too.

Configure bugmail: http://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 Monday, 26 October 2009 14:54:42 UTC

This archive was generated by hypermail 2.3.1 : Wednesday, 7 January 2015 16:30:41 UTC