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

Re: A why on inline rendering

From: Staffan Mhln <staffan.mahlen@telia.com>
Date: Sat, 1 Mar 2003 12:43:36 +0100
Message-ID: <000b01c2dfe7$cc0c6900$28cc41d5@sen>
To: "Michel Suignard" <michelsu@windows.microsoft.com>
Cc: <www-style@w3.org>

Hi Michel,
Thanks for the very helpful answer. Just a two comments this time...


From: "Michel Suignard" <michelsu@windows.microsoft.com>
>Concerning 'text-height' and why its initial value is not 'max-size', you may be surprised to discover >that some browsers use 'auto' (Nav 7.2, I think) while others use 'max-size' (IE6) as initial value.
Yes i was, that is quite interesting.

>Should we add more flexibility concerning adding m/p/b for non-replaced inline elements? Maybe >so. I agree that the different behavior between replaced and non-replaced is not logical. 
Personally i actually believe less flexibility in those areas would be very befinical (but i have little knowledge on what the main use of the more finegrained control in inline rendering is). I do realise this breaks old implementations, but since the current situation is rather complex as it is, i dont think that is such a major issue really. Not that many users will really know that the model changed since the change would occur at such a low level, and while some existing pages would change due to this, the change is likely to be minor. I also believe that the discussions around inline rendering in CSS2 indicates that simplifying the basic model would be very worthwhile. 

Again thanks for the help,
 /Staffan
Received on Saturday, 1 March 2003 06:45:52 GMT

This archive was generated by hypermail 2.2.0+W3C-0.50 : Monday, 27 April 2009 13:54:20 GMT