And I reply:
Yes, you are correct. Technically, all of those broswers support
_javascript_, but without the proper DOM support, what use is _javascript_
in a browser for real applications?
DOM level 0 support is very common on both Netscape 2 and IE. DOM level 1 and DOM level 2 is usally the problem.
Look at most books on _javascript_. About 25% or less is dedicated to
actual _javascript_, and the the rest is DOM support.
Yea, but which DOM you talk about. The DOM level 0 which Netscape support in Netscape 2 and 3 (also IE) or the DOM level 1 and 2 which Netscape 7 support? I totaly agree with we need be careful to use DOM level 1 and 2. Even when we use DOM level 0 we need to becareful. For example. IE support document.all but non of the Netscape document.all
And document.all is neither in DOM level 0, 1 or 2.
>From the Netscape compatability testing we peform in the last several years, the biggest problem we face is document.all, and people using obsleted layer support. Also, peoepl need to use "event" in IE and "e" in Netscape to reference to Event.
Pushing any computation onto the client is a really bad idea. Covering
all client tagets cases is a royal pain. If most users can't be counted
on to have their clock and timezone set properly, then all bets are off.
You can always keep thing in the server. That is ok, however, the trade off is the increase of client-server traffic and slow performance. Nothing is impossible, the question is what you want to trade.
