Arjun Ray wrote: > > On Wed, 01 Nov 2000 17:43:27 -0500, > fantasai <[EMAIL PROTECTED]> wrote: > > It's not quite "strictly a how-to-do-CSS issue". Its strictly a > > how-to-render-this-code issue. > > Oh great. I just *love* moving goalposts! So, you're saying that Ian > Hickson had it wrong when he wrote: > > : But we're not trying to do type assertion. We are trying to work out > : if the author was expecting a backwards-compatible rendering or a > : CSS-based strict rendering. > I'm not saying that at all. As Ian said, the difference is in whether Mozilla emulates legacy rendering or whether it uses its native behavior-- that of a CSS-based browser. You assumed that this meant it's interpretation of CSS; well, that's included, but not the whole story. There are many behavior specifics defined in the CSS specs (e.g. line height) that are not defined in HTML and which are contrary to legacy rendering. Mozilla compensates for these differences with a Quirks mode. > But all this is moot anyway. I'm done with this discussion. Very well.
