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

http://www.w3.org/Bugs/Public/show_bug.cgi?id=7978





--- 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:

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


> 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?

http://software.hixie.ch/utilities/js/live-dom-viewer/saved/292

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