It always work that way. You get something working all nice and happy in IE. Everything is great. You open it up in netscape and crash and burn. But if you use one version .01 less with netscape it works fine. Then .02 less it doesnt work at all again. STAB DIE DIE STAB!

They did send me a free shirt in the mail today and a couple of cd's with netscape on it.

You want an even funnier example?

If I could some scripts on a page and few it in IE, it works fine, it's great, it just, works... but if I open it in Netscape, if my script tag includes language="javascript 1.0" it breaks, if I change that to "javascript 1.1" it works, but if I change it to "javascript 1.2" is breaks again... considering I didn't actually read every single flippin' line of the 1.X JavaScript changelogs, and considering that my actual scripts have changed at all, I have to use whatever works in the version line... stupid NS pos... ok so I had a point when I started and I still know what I mean but I doubt it makes any sense now, hehe, oopsies... :)

holy crap I can't spell!! hehe

Brad, we need an "Edit Old Comments" option ( with some unchangable icon or something that the comment was editted )

Half of my javascript book just explains compatibility issues. Most of is directly stating Netscape is the problem. Yeah, the versions are out there, but Netscape doesn't seem to follow much of a standard.

And how the hell did Netscape 6 get "most accurate as per the standards" award?! I almost shot myself when I read that 'cause it means that 80% of us poor developers have apparently been doing it /ALL WRONG/! >:(

*grumpy*

Proof that Netscape engineers are true AOL people now.

"If it's not broken on my screen, it's not broken."