W3C home > Mailing lists > Public > www-style@w3.org > February 2003

RE: A why on inline rendering

From: Michel Suignard <michelsu@windows.microsoft.com>
Date: Mon, 24 Feb 2003 13:39:58 -0500 (EST)
Message-ID: <84DD35E3DD87D5489AC42A59926DABE901032D21@WIN-MSG-10.wingroup.windeploy.ntdev.microsoft.com>
To: Staffan Mhln <staffan.mahlen@telia.com>
Cc: <www-style@w3.org>

You may want to read the following document to see latest thoughts on the subject at http://www.w3.org/TR/css3-linebox/
(an update should be available soon, but the part describing 'text-height', 'line-height' and 'line-stacking-strategy' have been fairly stable.)


-----Original Message-----
From: Staffan Mhln [mailto:staffan.mahlen@telia.com] 

I'd like to know why non-replaced inline rendering works the way it does. The archives have many interesting discussions on how it is done, but i failed to find explanations on why. 

To try and clarify my questions somewhat; what is the advantage of having non-replaced inline nodes height dependant on font-height rather than children height (that is, including margin/padding/border etc)? Further, what is the advantage of having line-boxes not always being as high as the contents within them?

Any pointers would be greatly appreciated,
Received on Tuesday, 25 February 2003 11:43:18 UTC

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