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

Giovanni Campagna wrote:
>> If desired, we could probably make display compute to none in cases like
>> this instead of having the rule about throwing out the box.  It probably
>> doesn't matter much either way; all that's affected is what the DOM style
>> APIs return for the relevant nodes; the rendering is the same either way.
> As a general rule, finding the computed value of a property does not
> require laying out the page, so this point should change only the used
> value. This is the reason we have specified, computed, used and actual
> values, differently from CSS2.0.

There is no need for layout here.  All the rule would say is that 
computed display is none if the computed display of the node's parent is 
'table-column' and that it's none if the specified value is not 
'table-column' and the parent's display is 'table-column-group'.  This 
is no worse than the behavior of "display: inherit" in that all it needs 
is the computed display of the parent and the specified display of the 
child to decide on the computed display value of the child.


Received on Sunday, 31 May 2009 14:03:19 UTC