At 08:16 2001-04-05, you wrote:
>However for Netscape, yes you do have to define font attributes for td
>elements. (I believe this is the W3C standard though why they would do
>something so unlike what I'd like is beyond me.)
>I believe that Netscape and some other browsers treat <td></td> like say
><h1></h1> or <b></b> and has a default style for it so that this needs
>to be specifically overridden in your style sheet declarations.
I'm not really sure what you talk about, haven't followed the tread too
good, but when it comes to Tables it's a matter of inheritance not always
working, especially with nested tables. So, it basically is the same
problem with BASEFONT and CSS. Tables don't have an default style. The same
inheritance problem exists with DIV, BTW.
Don't know if BASEFONT is really worth fiddling with. It never was a hit
(or was it?) and is definately going away. Anyway it's definitely going
away. Specifying for example font for in a rule for all concerned
selectors/elements that may occur inside a TABLE or a DIV takes care of the
browser bugs. If BASEFONT crashes it's crashed (or isn't it?).