Cross-Browser Layers, Part One
Subject:   Articles like these are frustrating...
Date:   2001-11-18 15:36:03
From:   darknerd

I am a complete newbie to the world of DHTML, and man, can I tell you it's a nightmare. A lot of code out there is for NS4 and IE4, and the whole notion of cross-browser is a complete hoax.

I would be really useful if the author brushed up on W3C DOM and started adding articles with this in mind for several reasons:

  1. the code will be alot cleaner as in many cases the MS All DOM can be ignored, as W3C ID DOM is supported.

  2. Newbies getting involved these days will all too often come across W3C.

  3. Older browsers are multi-lingual retarded. Later browsers support Unicode more effectively. This leaves little choice for those wanted to create multi-lingual (namely Chinese, Japanese, Korean) pages with DHTML, but to use newer browsers with adequate Unicode support. These newer browsers (IE5+, NS6+, Mozilla) support
    Unicode and W3C standards.

  4. There are accessibility features with newer browsers due to W3C standards. This can help those that are blind for example, browse the net.

  5. Using object oriented Java Scripting, one can easily wrap older hoky code into a W3C DOM-like class, thus using a single DOM. :-). This makes the code look very clean, and only one logic is used (no forks), but yet maintains true bugwards compatibility

  6. As I started scouring the net, I found it frustrating that code did not work for one browser or the other. It was so frustrating. However, when I came across the rare snippets of W3C code, it always worked (except on NS4). And now with NS6, I never touch NS4.

    Lastly, I would not completely trust browser statistics. Microsoft automaps their integrated browser to go to MSN and other sources from within IE. MS then marks up the statistics for their search site and web browser is being used.