W3C home > Mailing lists > Public > www-dom@w3.org > October to December 1998

Conflicts between EMCAScript bindings and DOM Level 0?

From: Eric House <ehouse@Eng.Sun.COM>
Date: Tue, 8 Dec 1998 10:32:58 -0800 (PST)
To: www-dom@w3.org
Message-ID: <Pine.SOL.3.96.981208101528.8366C-100000@gratioit>
As an example: DOM "Level 0" provides an attribute on Document called
"images" that is an array.  The ECMAScript bindings provide an attribute
on Document called "images" that is an HTMLCollection.

If I'm writing a script, is there a way of indicating to the UA which
I mean shy of setting the <SCRIPT> element's 'type' tag?

And if I'm writing a UA/browser and want to provide reasonable default
behaviour in the absence of a 'type' tag, do I have to choose between
ignoring ECMAScript and breaking most legacy scripts?  Surely there's a
better way I've not thought of.


--Eric House

|  Eric House                                                              |
|     "Document Services" team, Browser 3.0; Sun Microsystems              |
Received on Tuesday, 8 December 1998 13:33:05 UTC

This archive was generated by hypermail 2.3.1 : Tuesday, 20 October 2015 10:46:05 UTC