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

Re: [CSS 2.1] Run-ins running into table and/or sub-table elements

From: Boris Zbarsky <bzbarsky@MIT.EDU>
Date: Thu, 02 Sep 2010 22:57:59 -0400
Message-ID: <4C806437.4070402@mit.edu>
To: www-style@gtalbot.org
CC: "www-style@w3.org" <www-style@w3.org>
On 9/2/10 8:48 PM, "Gérard Talbot" wrote:

 > http://www.w3.org/TR/CSS21/visuren.html#run-in

That section has been substantially rewritten.  Sadly, the editor's 
draft is not public, but the relevant text after the rewrite is:

   Let B be the first of A's following siblings that is
   neither floating nor absolutely positioned nor has
   'display: none'. If B exists and has a specified value
   for 'display' of 'block' or 'list-item' and is not replaced,
   then A is rendered as an 'inline' element at the start of B's
   principal box.

> What happens when
> - a run-in runs into a table element (display: table)?
> - a run-in runs into a table-row-group element (display: table-row-group)
> - a run-in runs into a table-header-group element (display:
> table-header-group)
> - a run-in runs into a table-footer-group element (display:
> table-footer-group)
> - a run-in runs into a table-row element (display: table-row)
> - a run-in runs into a table-cell element (display: table-cell) Shouldn't
> the run-in be converted into an inline box? .. and become the first inline
> box of such table cell?
 > - a run-in runs into a table-caption element (display: table-caption)
 > Shouldn't the run-in be converted into an inline box? .. and become the
 > first inline box of such table-caption?
 >

None of those can happen, per the above text.  In all such cases the 
run-in becomes a block.

-Boris
Received on Friday, 3 September 2010 02:58:33 GMT

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