Stylesheets and IE

Forum Moderators: travelin cat

Message Too Old, No Replies

Stylesheets and IE

keyplyr

4:13 am on Jan 8, 2003 (gmt 0)

I was emaild by a MAC user that said NN had no problems, but IE was not finding my external CSS. The user said he copied the page and stylesheet, removed the preceeding slash and was then able get the CSS. Example:

I had: <link rel="stylesheet" type="text/css" href="/css/stylesheet.css">

He changed to: <link rel="stylesheet" type="text/css" href="css/stylesheet.css">

I read that the MAC version of IE5 and IE5.1? have only partial support for CSS1 and CSS2, but the preceeding slash is, to my knowledge, correct.

Can anyone explain more about this?

Nick_W

8:41 am on Jan 8, 2003 (gmt 0)

I can't explain it but I can confirm that you are correct. IE for Mac is a disaster for StyleSheets, it has many, many failings unfortunately.

You may have to do a little browser sniffing if this is a big portion of your audience :(

Nick

BjarneDM

6:20 am on Jan 10, 2003 (gmt 0)

there's nothing wrong with the URL given in the <link>.

I too am using root-relative href-attributes in my <link rel="stylesheet" ...> and am having no problems getting them to load in IE 5.2 under MacOS X ; neither when accessing them as through localhost when testing nor in the public production on the proper web-server.

But I do agree with Nick_W : CSS support under IE on Mac is definitely buggy :-( ; I'm happy to see Safari on the shelf, and Safari will just have to iron out some bugs, and it'll be quite ready to supplant IE.

yamya

1:00 am on Jan 14, 2003 (gmt 0)

I think that providing the full URL eliminates the problem

keyplyr

7:19 am on Jan 14, 2003 (gmt 0)

I think that providing the full URL eliminates the problem - yamya

Thank you, yes.

But as an edu resource, I've had issues with FP users (and others) pulling the site down to desktop. This calls every last file in the domain at once! Twice now, schools have been pulling the site down and using PowerPoint (or whatever) for classroom viewing. The relative paths in the <head> help to significantly reduce this bandwidth abuse.