W3C home > Mailing lists > Public > www-dom@w3.org > April to June 2001

RE: DOM 3 Core: Overlap with JAXP, Document order of attributes, getChildElementsByTagName, Exceptions

From: Jeff Yates <PBWiz@mail.pbwizard.com>
Date: Wed, 16 May 2001 14:50:24 -0400
Message-Id: <200105161450.AA134676640@mail.pbwizard.com>
To: "Arnold, Curt" <Curt.Arnold@hyprotech.com>, <PBWiz@mail.pbwizard.com>, "Fred L. Drake, Jr." <fdrake@acm.org>
CC: "'www-dom@w3.org'" <www-dom@w3.org>
Fred,

>  This example seems to indicate that an implementation which follows
> the W3C bindings doesn't need any additional functions.  So let's
> avoid the extra method.
>    Perhaps Curt is using a non-conforming implementation? 

I believe the problem is that there is no conforming implementations built into a browser as yet.  The closest I have run into is Mozilla and it has it's bugs.  The one that applies to this is that the DOM constructors are NOT exposed until an object of that type is constructed first.

Example:

The Range object constructor is not exposed until you create one first.

//example code
alert( Boolean( Range ) );  //alerts false;
document.createRange();
alert( Boolean( Range ) );  //alerts true;

This is a major weakness.

Jeff.

--
Jeff Yates
e-mail:    PBWiz@PBWizard.com
Homepage:  http://www.PBWizard.com

--
Received on Wednesday, 16 May 2001 14:50:34 GMT

This archive was generated by hypermail 2.2.0+W3C-0.50 : Friday, 22 June 2012 06:13:48 GMT