W3C home > Mailing lists > Public > www-style@w3.org > October 2004

Re: Box model: min-margin and max-margin, max-padding and min-padding

From: Justin Wood (Callek) <116057@bacon.qcc.mass.edu>
Date: Sun, 03 Oct 2004 03:21:31 -0400
Message-ID: <415FA87B.4080604@bacon.qcc.mass.edu>
To: Andrew Fedoniouk <news@terrainformatica.com>, W3C Style List <www-style@w3.org>

Andrew Fedoniouk wrote:

>| > As per CSS [1] "display:table-cell" forces change of underlying DOM - UA
>| > *must* create table and row elements.
>| No, that's not true.
>| The UA must create table and table-row _boxes_.  These are purely display
>| objects and are not attached to any DOM nodes.
>Thanks, Boris!
>So the following shall clearly say 'boxes' instead of  'objects'.
>  1.. "If the parent P of a 'table-cell' element T is not a 'table-row', an
>object corresponding to a 'table-row' will be generated between P and T.
>This object will span all consecutive 'table-cell' siblings (in the document
>tree) of T. " (http://www.w3.org/TR/CSS21/tables.html#value-def-table-cell)
>Formally speaking elements are objects and boxes can be also objects.
Well a "node" technically is inserted, which is an anonymous node, 
meaning selectors do not match it, nor do they appear in the DOM, thus 
not modifying the DOM...  it is the same concept if in HTML you add an 
inline element, in a spot where the html would expect a block element, 
most browsers have implimented quarks behavior in these cases, so that a 
block elem is placed between them and the block one that is placed is 
not shown in the DOM...

~Justin Wood (Callek)
Received on Sunday, 3 October 2004 07:22:23 UTC

This archive was generated by hypermail 2.3.1 : Monday, 2 May 2016 14:27:15 UTC