>Hi Dragan,
>Yea I guess that's a solution. :) I used to use NS back before 4.0. About the only thing I do with it these day's is test code against it. I really consider it more of a thorn in the side. Having to modify code so it will display properly (read somewhat properly)in NS is a PITA. I don't intend on starting a IE verse's NS debate here, but according to the stats I keep on web site's I've built, less than 10% of the hits come from NS browsers. Seem's like a lot of extra work in workarounds for that < 10%. Not to mention, is NS security any better than IE?? Which was the real issue.
>
>I'm not really sure what the difference in active scripting and javascript is. I use javascript in some sites for client side data validation and it still works fine with active scripting disabled in IE 5.5sp2.


Since Netscape has declared Mozilla as open source, version 6 (just between these messages I switched to 6.2) has had pretty much the same attention of the computing community as other open source projects. Besides, it is used as a default browser under Linux, and I'm sure the guys there are watching closely. Here's what they say on the NS website http://home.netscape.com/security/index.html - pretty much it seems the flaws they had were left in version 4.x, and NS6 seems to be fine.

When Microsoft call something ActiveThis or ActiveThat, it seems to mean it's some sort of a fat client thing, i.e. downloaded and running on client side. I really don't have the time to learn all of their buzzwords and new names for old things.