RE: Issue 1: Font-weight and headings

Exactly.  IE3 had this problem as well.  IE4, on the other hand, works
as if all default rendering properties (e.g., the boldness of <STRONG>)
go into the cascade of properties ON THAT ELEMENT, just as if they were
specified at the beginning of the user stylesheet, which is pretty much
what the CSS1 spec recommends, if I'm interpreting it correctly (we
could just put all those rules IN the user stylesheet - but then if
someone deleted their user ss, we'd be in big trouble.  No thanks.)

With that in mind, I would like to suggest that IE3 and Navigator are
""wrong", and IE4 is "right".  Really, they're just two different
interpretations of how intrinsic HTML support is handled, but I believe
IE4's is much more intuitive.

Chris Wilson
"Stylesheets guy"
Internet Explorer Team

> -----Original Message-----
> From:	E. Stephen Mack []
> Sent:	Sunday, July 27, 1997 2:38 AM
> To:
> Subject:	Re: Issue 1: Font-weight and headings
> David Perell wrote:
> >By that logic, this one declaration:
> >
> >  BODY { 12pt/13pt normal sans-serif }
> >
> >should have the effect of rendering the entire document in 12pt/13pt
> >normal sans-serif, including all the headings. Fortunately, that's
> not
> >the case.
> Actually, I just tested this in Navigator 4.01.  I think you
> left off the "font:" property there, but Navigator doesn't understand
> that anyway.  When I use:
> BODY { font-size: 8pt; }
> Navigator 4.01 applies this font size to every element, including
> H1 and H2 elements.
> >Reader/default style declarations are not overcome by inheritance,
> only
> >by contrary declarations.
> So, that seems to be the problem -- the engineers at Netscape
> missed the same thing that I missed: inherited values don't
> outweigh initial/default UA style sheet values.
> Houston, we have a problem.
> -- 
> E. Stephen Mack <>

Received on Monday, 28 July 1997 09:49:24 UTC