- From: Boris Zbarsky <bzbarsky@mit.edu>
- Date: Sun, 23 Oct 2005 23:07:39 -0500
- To: www-style Mailing List <www-style@w3.org>
Ian Hickson wrote: > Note though that the fictional tag sequence is just an explanatory > concept, and not an implementation requirement. Understood. But it affects style resolution nevertheless... > The language you mention doesn't affect this; an inline-table on the first > line is still on the first line I had a table, not an inline-table. But I guess the same thing applies... > What would you like the rendering to be? I don't know. I haven't thought of a non-broken solution yet, frankly, hence the original mail. > What UAs generally seem to have done IIRC is made properties that normally > inherit inherit from the ::first-line (and thus have two computed values, > one for each part -- I'm not sure which they return for the DOM), and made > properties that don't normally inherit inherit from the parent element. What Gecko does is to inherit everything from the first-line, but make its decisions on what layout objects to create _before_ any of that happens, so that the first-line can't affect that. Which of course means that the style data and rendering model don't match. ;) Oh, and all this is during initial page layout. On incremental changes the behavior is highly inconsistent, depending on the ordering of changes and exact types of changes... Which is what made me look into this to start with. :( -Boris
Received on Monday, 24 October 2005 04:07:44 UTC