W3C home > Mailing lists > Public > www-style@w3.org > September 2010

Re: Action Item: Fix Float Positioning Rules for floats in run-ins

From: Boris Zbarsky <bzbarsky@MIT.EDU>
Date: Wed, 22 Sep 2010 16:59:47 -0400
Message-ID: <4C9A6E43.6090003@mit.edu>
To: Stephen Zilles <szilles@adobe.com>
CC: "www-style@w3.org list" <www-style@w3.org>
On 9/22/10 4:46 PM, Stephen Zilles wrote:
> [SZ] Good question. Since (I believe) the intent of a "run-in" is to make the content within it become part of the block (or list item) it runs into, then I would paint the run-in as it were part of that block (or list item). I believe that is the intent of saying in 9.2.3 Run-in boxes that "A is rendered as an 'inline' element at the start of B's principal box."

Yes, but now we're talking about floats that are kids of the run in. 
And Appendix E section E.2 item 5 says:

   All non-positioned floating descendants, in tree order.

(note that "tree order" here talks about traversal of the rendering 
tree, but nothing actually defines where floats go in the rendering 
tree, if anywhere at all, and some will claim that there isn't even a 
rendering tree).  I think the spec is _trying_ to say that in this testcase:

   <span style="display: run-in">
     <span style="float: left" id="one"></span>
   </span>
   <span style="float: left" id="two"></span>
   <div></div>

The float with id="one" should paint after the float with id="two".  But 
it needs some reading between the lines (and could _really_ use some 
tests in the test suite).

-Boris
Received on Wednesday, 22 September 2010 21:36:53 GMT

This archive was generated by hypermail 2.3.1 : Tuesday, 26 March 2013 17:20:31 GMT