37610 - CSS font size and color rendered incorrectly

Status: VERIFIED INVALID

(Core :: CSS Parsing and Computation, defect, P3)

Description

[Steevithak]

All of the styles on this page render correctly except one - the headline font
that says "A Turtle's Fancy".  This renders correctly on Netscape 4.7 and
Internet Explorer 5. The style information follows:
.headr  {
   	font-size : 28px;
   	font-family : serif;
   	font-weight : bold;
   	font-style : normal;
   	color : #BF4300;
   }

Comment 1

[Péter Bajusz]

There's a problem with the style.css included in this html.
CSS files should contain just that: CSS.
But style.css is really a html file which the css parser appearently chokes on.

I think it would be a good idea to fix the site.

I don't know wether this bug should be marked INVALID, or made a compatibility
bug for the parser. I'm leaving it for now.
I'll attach the style.css in case it gets changed.

Comment 2

[Péter Bajusz]

Attachment: 'CSS' file that the parser chokes on.

Comment 3

[Péter Bajusz]

*** Bug 37611 has been marked as a duplicate of this bug. ***

Comment 4

[Asa Dotzler [:asa]]

updating component and owner.  changing status to New.

Comment 5

[Pierre Saslawsky]

Péter Bajusz is correct: a CSS file shouldn't contain HTML code.
Marking invalid.

Comment 6

[Steevithak]

The style sheets referenced in bugs 37610 and 37611 have been corrected (the 
extraneous HTML tags were removed) and they now work with Mozilla. Both Netscape 
and IE render the web pages correctly in spite of the faulty style sheets, 
however, so this really should be accounted for in Mozilla to avoid the 
appearance to end users of a Mozilla bug.

Comment 7

[Hixie (not reading bugmail)]

It would be violating the CSS spec to support this.

The spec is very specific about error handling because, on the web, authors tend
to design for browsers, rather than for specs.  If it works in a browser, then
authors figure it should work, and other browsers are then forced to handle
those pages.  This creates an escalating leniency (which becomes very hard to
code) from release to release of browsers.  (Consider the HTML parser as an
example.)  The authors of CSS didn't want CSS to go the way of HTML.

[david: err, sorry... ;-) ]

Comment 8

[David Baron :dbaron: (⌚️UTC-5, no longer working on Mozilla)]

Ian, er, if you're going to quote my comment on bug 37448 any more, could you at
least change the "escalating leniency" to "escalation of leniency".   That's one
of the worst sentences I've written recently...

But wait a second here.  Shouldn't the whole stylesheet work, except for the
first rule?  Is there some auto-detection going on here?

Comment 9

[David Baron :dbaron: (⌚️UTC-5, no longer working on Mozilla)]

This actually works just as it should, so I'm leaving it VERIFIED-INVALID.  The
attachment above has the wrong MIME type.  Only the first rule is ignored.