Ok, I'm trying to be a good little boy and create a site that doesn't
use frames :) Things were going along decently until I uploaded what
little I have done so far to the web server (that is, things were
displaying pretty well on my local machine - not perfect, but we'll get
to that later).

So here's the site: http://www.wesleyumc-vinton.org/beta/index.html

This page displays pretty good in IE, but all the graphics and styles
are gone in Firefox, though it works on my local system. Can anyone
tell me what is Firefox's problem? I have validated it at W3C on my
local system and it says that there is a parse error at

#menu_graphic { background-image: url(img/menu.jpg); background-repeat:
no-repeat; height: 432px; width: 170px; }

but I'm not clear on what this means. I can't see an error myself. I
also tried validating it at the server but it only says something about
an unknown mime type, that I don't understand either.

Secondly, when you look at the page in IE, you'll notice that the text
in the menu links is a little bit off - 1 pixel actually. Home is
positioned fine, Action is a pixel off, Learning is 2 pixels off, etc.
When I look at this on my local system with Firefox, the links are
positioned correctly.

Is there a trick I haven't learned yet to making the position of this
list items appear in the same place in both browsers without creating
separate stylesheets?

Thanks for any help...

AJ

AJBopp wrote:
> Ok, I'm trying to be a good little boy and create a site that doesn't
> use frames :) Things were going along decently until I uploaded what
> little I have done so far to the web server (that is, things were
> displaying pretty well on my local machine - not perfect, but we'll get
> to that later).
>
> So here's the site: http://www.wesleyumc-vinton.org/beta/index.html
>
> This page displays pretty good in IE, but all the graphics and styles
> are gone in Firefox, though it works on my local system. Can anyone
> tell me what is Firefox's problem? I have validated it at W3C on my
> local system and it says that there is a parse error at
>
> #menu_graphic { background-image: url(img/menu.jpg); background-repea
t:
> no-repeat; height: 432px; width: 170px; }
>
> but I'm not clear on what this means. I can't see an error myself.

This is from your style sheet:
.menu
/* Set the properties of the menu frame on the left side */

#menu_graphic

Take out the comment between .menu and #menugraphic and you won't get
that error

Thanks! That eliminates one problem. Now if I could just get teh CSS to
render in Firefox! :)

AJ

AJBopp wrote:
> Thanks! That eliminates one problem. Now if I could just get teh CSS to
> render in Firefox! :)
>
> AJ
>
It must be something to do with your server.
Here's the same page on my server and it works fine in Firefox
http://www.reenie.org/test/test3/

AJBopp wrote: 

meltedown  <groups2@reenie.org> wrote:
> It must be something to do with your server.
> Here's the same page on my server and it works fine in Firefox
> http://www.reenie.org/test/test3/

Yep. The file http://www.wesleyumc-vinton.org/beta/style1.css is being sent
as application/octet-stream rather than as text/css.
--
Darin McGrew, mcgrew@stanfordalumni.org, http://www.rahul.net/mcgrew/
Web Design Group, darin@htmlhelp.com, http://www.HTMLHelp.com/

"Entering Yosemite National Park: laws of gravity strictly enforced"

Darin McGrew wrote:
> AJBopp wrote:
> 
>
>
> meltedown  <groups2@reenie.org> wrote:
> 
>
>
> Yep. The file http://www.wesleyumc-vinton.org/beta/style1.css is being sen
t
> as application/octet-stream rather than as text/css.

How do you know ? Is there some way of telling what its being sent as ?

Ok, I'm a newbie but this is too weird for words. Why does
http://www.wesleyumc-vinton.org/beta/index.html not render correctly in
FF, but
http://www.wesleyumc-vinton.org/index.html renders OK? Especially since
the CSS in the second case is really crappy and full of errors? (my
first effort at it).

AJBopp <ajbopp@XXXXXXXXXX> wrote:
> Ok, I'm a newbie but this is too weird for words. Why does
> http://www.wesleyumc-vinton.org/beta/index.html not render correctly in
> FF, but
> http://www.wesleyumc-vinton.org/index.html renders OK? Especially since
> the CSS in the second case is really crappy and full of errors? (my
> first effort at it).

Do they both trigger the same layout mode? Badly broken documents usually
work better in the quirks layout mode of modern browsers.

But you should start by fixing the (X)HTML and CSS errors, and by
configuring your server to send the correct Content-Type header for your
style sheets.
--
Darin McGrew, mcgrew@stanfordalumni.org, http://www.rahul.net/mcgrew/
Web Design Group, darin@htmlhelp.com, http://www.HTMLHelp.com/

"Entering Yosemite National Park: laws of gravity strictly enforced"

AJBopp wrote:

> Ok, I'm a newbie but this is too weird for words. Why does
> http://www.wesleyumc-vinton.org/beta/index.html not render correctly in
> FF, but

Error: The style sheet http://www.wesleyumc-vinton.org/beta/style1.css
was not loaded because its MIME type, "application/octet-stream", is not
"text/css".

> http://www.wesleyumc-vinton.org/index.html renders OK? Especially since
> the CSS in the second case is really crappy and full of errors? (my
> first effort at it).

<http://jigsaw.w3.org/css-validator/....org/index.html>

You need to remove the
<style type="text/css">
from that style sheet.

Use the Web Developer's Toolbar with Firefox, and you can find things
like this in .. double-quick time.
http://chrispederick.com/work/webdeveloper/

--
-bts
-Warning: I brake for lawn deer

Beauregard T. Shagnasty wrote:
> AJBopp wrote:
>
> 
>
>
> Error: The style sheet http://www.wesleyumc-vinton.org/beta/style1.css
> was not loaded because its MIME type, "application/octet-stream", is not
> "text/css".
>
> 
>
>
> <http://jigsaw.w3.org/css-validator/....org/index.html>
>
> You need to remove the
> <style type="text/css">
> from that style sheet.
>
> Use the Web Developer's Toolbar with Firefox, and you can find things
> like this in .. double-quick time.
> http://chrispederick.com/work/webdeveloper/
>
I have the web develepers toolbar and I use it all the time. Its really
handy.  When I look at  AJBopp's site in FF, it doesn't load the css.
But when I click on "edit css" it loads fine.  I can then see the
contents of the page as well as the css in the editor.

However, when I try to look at the style sheet in firefox, it thinks its
an application and tries to download it, instead of simply viewing it,
obviously because the mime type is wrong. But what I would like to know
is how do you get the error that tells you the mime type is
application/octet-stream ?

Inquiring minds want to know !