Re: [CSS21] Proposal for a replacement for section 17.2.1 (table anonymous objects)

On Tue, Jul 20, 2010 at 8:15 PM, fantasai <> wrote:
> On 07/20/2010 05:16 PM, Tab Atkins Jr. wrote:
>> Final proposal for issue 110!  For the purpose of solving this issue
>> for CSS2.1, I propose accepting Fantasai's revised algorithm for
>> table-repair, with a small correction so that it properly handles
>> floated elements inside a table* element:
> Tab, we already accepted the revisions that I wrote up with bz.
> Those are already in Bert's to-edit list.

I'm confused.  Your algorithm explicitly ignores abspos elements (and,
accidentally I think, floats).  If it's already been accepted, then my
making it slightly more explicit shouldn't be controversial, unless
Boris is depending on an accidentally underspecified part of it that
allows us to both think that the text is okay while drawing opposite
conclusions from it.

> Can you repost your proposal as changes from the already-accepted text?
> (And I mean *as changes*, not as "replace all of that with all of this,
> even though most of it is exactly the same".)

Heh, sure.  I like to be thorough, especially when the text I'm
changing isn't actually in a spec yet.

First change, adding a note to the definition of 'consecutive' to
explicitly include floats:
 |   consecutive
 |     Two sibling boxes are consecutive if they are both in flow
 |     (that is, neither are absolute or fixed position)...

Second change, making the step 2 points explicit in the same way:
 |       2.1 If a child C of a 'table' or 'inline-table' box is not a
 |           proper table child and is not absolute or fixed
 |           position,...

Third change, adding an informative note to the end:
 | Note: Absolute and fixed position elements do not participate in
 | the above algorithm in any way.  The static position of absolute
 | or fixed position elements who's parent element is a tabular
 | container is undefined in CSS2.1.


Received on Wednesday, 21 July 2010 04:22:21 UTC