Re: Netscape Irritant (was: Document managment etc)

Funny,


I knew about the css missing thing, but just recently walked into another
problem.  Damn I thought - my personal slave ;) must have had the directory
wrong.  Couldn't find the problem though.  Page was inside a frameset, with
the CSS as it should be in the specific page (noone would do it
differently).  Though when I started trying to fix some things, I only
managed to get it to work by putting the CSS in a directory in relation to
the parent frameset OR the page's own directory.

Very weird.  And yes, I found it irritating.  But so what? I have a brand
new car that keeps falling apart and will be getting rid of it very soon.
But NN4 is still out there and whatever you think or do, it'll be there for
quite some time still.  It's better to take it on than to let it go.  Now
let's be honest, what fun would there be without Netscape? ;)

Oh, if anyone knows of the above problem with the CSS, let me know!


- Kayjey -


----- Original Message -----
From: Larry Coats <lcoats(at)gte.net>
To: <ezrasf(at)yahoo.com>
Cc: 'HWG-technique Mailing List (E-mail)' <hwg-techniques(at)hwg.org>
Sent: Thursday, October 18, 2001 7:02 AM
Subject: Re: Netscape Irritant (was: Document managment etc)


> Ezra S F wrote:
>
> > One of the things I hate most about Netscape is how in handles included
> > files. Even after 2 years, if a CSS files is missing, then you are
> > prevented from seeing a web site at all.
>
>
> Hmmm. I never knew that. I just did a quick test, and right you are.
>
>
> > One of my first designs for a main page had to be scrapped because
> > Netscape on the Mac went to a JS file instead of the home page. Showed
> > the source of the file instead of the real deal. Naturally the boss was
> > on a Mac using Netscape.
> >
> > It did teach me to test on Macs :)
>
>
> This one was a server problem rather than a browser problem, and bites
> NN3 on the PC as well. The server wasn't serving your JS file up as
> content-type x-application/javascript. I've had to have several
> different ISPs set this up for me - many of them don't realize that this
> is the proper content-type for JS files, but they were all happy to fix
> it for me and it always cured the problem. IE never pays any attention
> to the content-type, but rather tries to figure out the content-type
> based on the contents. NN4 (at least on the PC) also can figure out that
> it's a JS file even though the server is sending down the wrong
> content-type.
>
> Larry Coats
>
>
>

HWG hwg-techniques mailing list archives, maintained by Webmasters @ IWA