Forum Moderators: open
What could cause this?
I've seen a stall like this happen on a linked css. The css was hideously formatted (not by me!). This may or may not be your problem.
Download Topystyle Pro and cleanup and validate your css with it.
Also, one of the best things you can do is run your code through the W3C validator.
If all of the above says your code is ok, then it's Netscape 4.08. It is pretty ancient. Anybody using that is probably not buying what your selling if they can't afford to upgrade their computer from x386.
I would sweat a little more about 4.7, but only if your audience includest Los Alamos Lab, government workers, senior citizens, or people who aren't internet saavy. I'm not being sarcastic.
NS 4.08 is pretty much safe to ignore.
In other words, test it against NS 4.7 and judge it against that. (If it was a JS error it would show up on your NS or IE browser as an error message).
[edited by: martinibuster at 5:12 am (utc) on Mar. 19, 2003]
For some reason NS seems to choke on CSS.
Here's the way I undertand it. Netscape first created something called "javascript style sheets" or JSS. When JSS was not adopted as a standard and CSS came in, Netscape kludged their CSS engine on top of their JSS engine in a big pile of spaghetti code.
If you turn off JavaScript in Netscape 4.x you will also turn off stylesheets -- they are interlinked all the way. So lousy stylesheet code can generate some nasty javascript looping off stage in NN4.x. Wasn't fixed until NN 6.
[jigsaw.w3.org...]