Another Firefox issue with CSS

[John Brandt]

I have a new design using CSS to position the menu bar as opposed to
tables. It validates HTML transitional, CSS and looks fine in IE and
Opera. Firefox on the otherhand does not seem to be able to find the
external CSS.

Any suggestions?

http://www.mainecite.org

Thanks

jeb

 

[brucie]

In alt.html John Brandt said:

CSS and looks fine in IE and Opera. Firefox on the otherhand does not
seem to be able to find the external CSS.

nothing wrong with FF, its ignoring the css file as it should.

your server is misconfigured to send css files as text/html. css should
be sent as text/css. contact your host to fix it.

 

[Beauregard T. Shagnasty]

In alt.html John Brandt said:


nothing wrong with FF, its ignoring the css file as it should.

your server is misconfigured to send css files as text/html. css
should be sent as text/css. contact your host to fix it.

Aw brucie, ya beat me to it. :-(

Well, then for John, you can reduce your banner graphic to about 16KB
instead of the 82KB it currently is.

 

[John Brandt]

Wow. You know, I saw a statement to that effect on one of the
validator sites and I figured it was a glitch. I have never heard of
this type of server issue. Learn something new every day.

We are running this site on a FirstClass server so I'm not sure this
will be easy to figure out. I'll pass this on to our "server guy" and
see if he can figure out how to change this.

Thanks for this response. I was pulling the few remaining hairs out of
my head.

jeb

 

[Dylan Parry]

http://www.mainecite.org

Nothing to do with the original question, but what is the logic behind
having the "d" link towards the top of the page? Does it have some sort
of accessibility benefit?

 

[Sybren Stuvel]

John Brandt enlightened us with:

You know, I saw a statement to that effect on one of the validator
sites and I figured it was a glitch.

Now you know not to ignore things, even if it appears like a glitch

I have never heard of this type of server issue. Learn something new
every day.

I've seen it before - very annoying. I've also seen sites where HTML
is served as text/plain...

Sybren

 

[John Brandt]

Well, then for John, you can reduce your banner graphic to about 16KB
instead of the 82KB it currently is.

Thank you for this advice and taking the time to make the new file.

jeb

 

[Toby Inkster]

Nothing to do with the original question, but what is the logic behind
having the "d" link towards the top of the page?

In general d-links are used to provide lengthy descriptions of non-text
content, such as graphics. The kind of thing longdesc would do if it were
supported by any browsers.

Does it have some sort of accessibility benefit?

In this case, it seems rather pointless. A description of the banner image
doesn't help you understand the page content any better.

 

[John Brandt]

Nothing to do with the original question, but what is the logic behind
having the "d" link towards the top of the page? Does it have some sort
of accessibility benefit?

Toby is correct in his description of the "little d." As you could
telll by reading throught the site, Maine CITE's mission is related to
assistive technology and accessibilty. We are always trying to the
make the site as accessible as possible and use it as a "model" so to
speak. That was the primary reason for updating the design to use CSS
for positioning as opposed to layout tables - I've heard the
criticisms in this NG.

Anyway, it is alway a work in progress and we go beyond some of the
accessibility standards out there (e.g. WAI, Section 508, etc.).

jeb

 

[John Brandt]

John Brandt enlightened us with:

Now you know not to ignore things, even if it appears like a glitch



I've seen it before - very annoying. I've also seen sites where HTML
is served as text/plain...

Sybren

Looks like we got it to work, My "server guy" had noticed the problem
and it was related to the FirstClass server doing strange things. We
have fixed the settings and will be alerting the support group for the
FirstClass server so others don't have the same problem.

Regarding the recognition of the interpretation of the validator info.
I almost didn't see it. It noted that the CSS file was essentially
fine. The notation about the text/htm text/css issue could have been
easily missed.

Thanks for helping me to learn.

jeb

 

[Sybren Stuvel]

John Brandt enlightened us with:

Looks like we got it to work
Good!

My "server guy" had noticed the problem and it was related to the
FirstClass server doing strange things.

Not all that First Class, is it?

Regarding the recognition of the interpretation of the validator
info. I almost didn't see it. It noted that the CSS file was
essentially fine. The notation about the text/htm text/css issue
could have been easily missed.

Perhaps you could send a suggestion to the W3C Validator team, telling
them how easy it is to miss such an important error.

Thanks for helping me to learn.

NP!

Sybren