Jeremy Allaire on the Death of Mozilla
Saturday July 31st, 1999
Tony Gorman has news of some interesting statements from Allaire Corporation's Jeremy Allaire. Tony writes:
"Jeremy Allaire of ColdFusion fame has gone on record saying that ColdFusion no longer supports the Netscape browser. In this month's issue of the UK Internet magazine 'Webspace', JA states that 'Netscape is dead and so is the Mozilla project'. Tough words for fans of the Netscape browser. He goes on to argue that widespread of DHTML has been held back by Netscape's idiosyncratic implementation and only Microsoft offers a useful platform...
Webspace apparently doesn't have a website, so I can't confirm this. However, if it is true, Jeremy's statements show an appalling lack of understanding of the status of DHTML at this point in time. IE's DHTML isn't standards compliant (neither is Communicator 4.6's DHTML) and thus any judgement regarding it must be tempered by the fact that much of the "usefulness" is probably derived from MS proprietary extensions that no other browser maker should feel obligated to duplicate. Maybe some of you more knowledgable people out there could give some background on how IE's current DOM implementation is lacking in terms of standards compliance.
UPDATE:Jeremy Allaire has a response in our forums, so be sure to check it out. Thanks Jeremy!
#44 DHTML does not exist in mozilla currently
Wednesday August 4th, 1999 11:33 AM
You are replying to this message
There is no such thing as DHTML support in Mozilla. Why? Because you _cannot_ access the widht,height,position, etc CSS properties of elements _unless_ you specify them yourself. THat is, you cannot say:
<div id="mydiv" style="position: relative" onclick="dump(this.style.XXXXX)">code</div>
This is terrible in my opinion, and many other people's, including Brendan Eich according to some posts I've seen of his criticizing the W3's oversimplified DOM. Until the DOM, or some actual "DHTML" standard that builds upon the DOM is made, it doesn't appear that DHTML will exist in Mozilla.
I don't know how it is in IE5, but I'd bet they "embraced and extended" the w3 dom and made it work their own way...anyone know?