MozillaZine

Mozilla Dispenses with Old, Proprietary DOM

Monday June 14th, 1999

The Mozilla team has decided to forgo backwards compatibility with Netscape's proprietary DOM so they can throw their full efforts behind proper DOM Level 1 support for Mozilla's first release. Click here to read more at News.com, or here to read the thread from the newsgroup.

Thanks to Kovu for the news.


#32 Re:Mozilla Dispenses with Old, Proprietary DOM

by SomeSmartAss

Thursday June 17th, 1999 7:14 AM

You are replying to this message

"but since old browsers don't support CSS it would force them to make a seperate page for the old and new browser (wouldn't that suck???)."

That's kinda what were doing now with DOM anyways. The main focus of Mozilla, since going full bore with the gecko engine, has been to correctly implement the standards in its rendering engine. The other, proprietary stuff was a bonus. But when push comes to shove, and deadlines are looming, it HAS to be the standards that win over proprietary implimentations. This is simply because Mozilla is NOT Netscape, never was, never will be. Sure, it was born of Netscape, and Netscape is basing their next generation browser on Mozilla code, but they are two distinct entities, and will, over time, grow farther and farther apart. It isn't "thier" proprietary DOM, it's a non-standard proprietary DOM. 'sides, according to the news posting, Netscape will put a lot of effort to try and ease us web developers into WC3 DOM code.

and I quote :

6) For those developers who need to continue to support apps on both the Nav4 DOM and the W3C DOM during the transition period or who need to upgrade existing Nav4 DOM apps to Nav5 and the W3C DOM, Netscape will be releasing TechNotes, sample code, and View Source articles showing how to do this.

7) We'll be holding a CodeStock shortly to start educating developers about the W3C DOM.

8) We'll be making educational presentations available for free, 24x7 access as streaming audio presentations at media.netscape.com.

9) We will also be encouraging tool vendors to provide full support for Gecko, Nav5, and W3C standards such as HTML 4.0, CSS1, and DOM1 to ease cross-browser development.