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...

I would love to write this guy off... but Allaire isn't exactly a no hope company. Should his words be left to stand? I hope not."

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!

#55 Nav 4

by Anon

Thursday August 12th, 1999 10:13 AM

You are replying to this message

Yeah, in nav4 you can do it with document.layers["idblah"].clip.width or something to that effect. ----News flash---- There is a "new" thread on the various groups about how they will address these issues. Apparently IE does something pretty smart, which is use a separate mechanism which does not clobber the CSS. They use getOffsetLeft() getOffsetTop() or something like that to retrieve those values.

If w3 doesn't come up with a "standard" way of doing this before nav5 comes out, I hope there is at least consideration of IE5's way -- which apparently does not interfere with the official dom. I wish I could comment more about IE5, but I've only used it, not coded for it.