Closed Bug 186679 Opened 22 years ago Closed 22 years ago

CSS links ignored if file extension is not css

Categories

(Core :: CSS Parsing and Computation, defect)

x86
FreeBSD
defect
Not set
normal

Tracking

()

RESOLVED INVALID

People

(Reporter: aangel, Assigned: dbaron)

References

()

Details

User-Agent:       Mozilla/5.0 (X11; U; FreeBSD i386; en-US; rv:1.1) Gecko/20021114
Build Identifier: Mozilla/5.0 (X11; U; FreeBSD i386; en-US; rv:1.1) Gecko/20021114

Mozilla ignores <link rel="stylesheet" ... /> tags where the extension of the
file specified in the href is not css.  Example, I use PHP to generate my CSS
stylesheets.  A stylesheet I have, stylesheets/default.php, is ignored in the
<LINK> tag.  A workaround would be to generate static CSS pages from PHP, but
that defies the whole point of PHP.

Reproducible: Always

Steps to Reproduce:
1. Include a CSS stylesheet using <link rel="stylesheet" type="text/css"
href="somefile.php" />.
2. Include a CSS stylesheet using <link rel="stylesheet" type="text/css"
href="somefile.css" />.

Actual Results:  
1. Stylesheet not applied.
2. Stylesheet applied.

Expected Results:  
Apply the stylesheets named in <link> tags without regard to file extension
Reporter, that's a real easy one : the link isn't valid. Your first stylesheet
is http://web.aquarius.null/stylesheets/fs.php, but that host doesn't exists.
The link http://web.aquarius.null.proxy0.opennic.unrated.net/stylesheets/fs.php
works.

BTW: you still have another problem, because the mime-type isn't text/css, but
text/html. You'll have to generate the Content-Type header in your script too,
because the webserver will turn it automatically in text/html. This will work in
quirks-mode, but not in standards-mode (the mime-type in the link doesn't have
preference).

Happy X-Mas, and stay off the egg-nogg when coding webpages (that's a joke :-).
Status: UNCONFIRMED → RESOLVED
Closed: 22 years ago
Resolution: --- → INVALID
Well alright then. Rather contrary to most browsers, and mind you web.aquarius.null exists. 
You need to log in before you can comment on or make changes to this bug.