Ian Thomas wrote: >> kchayka wrote: >>> I just discovered (the hard way) that a patch for >>> http://bugzilla.mozilla.org/show_bug.cgi?id=46225 was checked in on >>> 11/19. My pages, which all pass strict validation, ain't got no styles >>> anymore. :-( Turns out the hosting service has .css files defined as a >>> content type "text/plain" instead of "text/css", so the stylesheets are >>> being ignored. I have contacted them about it, but no reply, yet. >>> >>> Are my only options at this point to: >>> a. use a Transitional DOCTYPE, or, >>> b. assuming they don't change the MIME type, move to another host? >>> >>> And is RFC2318 what I should throw in their face? >>> >>> thanks for any help > > > That depends if your host allows .htaccess files or not. Try creating a > file called .htaccess in the same directory as your css files, with the > following contents (the next line only): > AddType text/css css
This worked! Thank you! > > But try getting them to change the MIME type first. I will definitely keep on them about it, so another poor soul doesn't get nailed by this, too. > Jerry Park wrote: >> However, serving up the wrong mime type did not seem to bother the >> browser. > > Because it didn't check the content-type > >> It just kept me from validating the CSS with a URL (had to >> copy/paste for validation). > Because it did. I see now. The W3C CSS validator didn't complain when I submitted the url of the html page, but barfed on just the .css files. After I put the .htaccess file out there, the validator was cool with it, too. Thank you, Ian. -- To email a reply, remove -ns-. Mail sent to the -ns- address is automatically deleted and will not be read.
