Netscape 6 — 2001 – A Spaced Odyessy

As I predicted back on 13 March last year, Netscape has made good on their intent and produced the next-generation browser known as Netscape 6.

And you know something? I think it's pretty to look at and fun to play with.

Netscape is touting "6" as a 'revolutionary new browser'... "... maybe even an IE killer." (These statements were taken from the Netscape site on 1 January 2001. Hence, my headline of "Spaced Odyessy".

I'm not making the pun to be cute. I'm making it because there's a big problem with this browser that's causing many web builders fits of frustration. The problem is that in cases where Netscape Communicator 4.7 could run most of the DHTML scripting that was purposely created for Internet Explorer 4 through 5.5, Netscape 6 literally ignores a lot of the DHTML code and, in many cases, takes CSS laid-out pages and smashes images and elements into the left margin of the browser window.

As a retort to the scripting problem, some web designers have taken a blood oath to give up on and forget Netscape. Or, in having to necessarily work with Netscape 6, designers are turning their backs on CSS and DHTML and, once again, locking up their pages within nested tables and creating animations with either Flash^®, Live Motion^® or drop-in Java applets.

Well, I suppose that's okay if we all want to make Macromedia and Adobe happy and at the same time a few other companies that produce Java applet-building programs. But hey! What happened to web standards? Why hasn't Netscape 6 drawn closer to performing like Internet Explorer 5.5? Why aren't any and all browsers marching to the beat of the same drummer in their interpreting of web page scripting?

From the point of view, I suppose, of the idealist scripter who's continually monitoring every machination made by the World Wide Web Consortium, what's taking place with the four main browsers is tantamount to treason. 'Four' browsers? Yes, there's Internet Explorer, Netscape, Opera and AOL. Each has its own methodology of operation; two are the major contenders; one is a wannabe and the remaining is playing a serious game of catch-up. So, the question begs: Why don't the four browsers render web scripting identically and in so doing conform to 'standardization'? The answer is quite simple -- there's no money to be made in being identical to the competition.

Understand one thing so that it's crystal clear in your thoughts: Netscape 6 does not want to do things the same as Internet Explorer. It wants to do things 'better' and differently. This is the only way Netscape 6 will ever have viability in the marketplace. It has to offer a marketable alternative to what's presently being offered by Internet Explorer.

Next page....