| It better not modify the underlying DOM at all. What makes you think it
will?
Sorry, Boris I was not clear enough.
Example:
Let's say we have standalone paragraph with style
<body>
<p style="display:table-cell">
</body>
As per CSS [1] "display:table-cell" forces change of underlying DOM - UA
*must* create table and row elements.
This action is not a subject of "applying style to the element" but
subject of "transformation of document structure" instead.
Such transformation allowance is in conflict wth CSS selectors.
Example: for the HTML above shall following style selector be in effect for
the paragraph?
body > p { color:red }
(p does not have body as a direct parent anymore, right?)
Other example:
body > p { display:block; }
body > p: hover { display:table-cell; }
Shall UA clear remnants of anonymous cell application (table and row
elements) when mouse will left such paragraph?
And again: after switch into 'hover' state first rule will not be valid for
the P anymore.
To resolve this problem :
1) definition of '>' and '+' selectors should be redefined.
=or=
2) definition of "child element" should be changed (and interpretation of it
by US)
3) table-* values should be deleted.
And I am yet silent about DOM programming interface changes ...
Again there are few *real* and *simple* alternatives todisplay:table-*
One of it is 'flow' attribute mentioned before. It is simple and natural and
will not force to change DOM.
[1] http://www.w3.org/TR/CSS21/tables.html#anonymous-boxes
Andrew Fedoniouk.
http://terrainformatica.com
----- Original Message -----
From: "Boris Zbarsky" <bzbarsky@MIT.EDU>
|
| Andrew Fedoniouk wrote:
| > About dispaly: table-*. Being applied will dramaticly modify underlying
DOM.
|
| It better not modify the underlying DOM at all. What makes you think it
will?
|
| -Boris
|