W3C home > Mailing lists > Public > www-dom-ts@w3.org > November 2001

Re: Test nodeparentnodenull (DOM level 1)

From: Curt Arnold <carnold@houston.rr.com>
Date: Tue, 20 Nov 2001 23:29:01 -0600
Message-ID: <014d01c1724d$6f15c330$7600a8c0@CurtMicron>
To: <www-dom-ts@w3.org>
Test nodeparentnodenull (DOM level 1)I have corrected this in the CVS.  

I was suprised that this hadn't come up as a failure for some processor on the cast of an Element to a NodeList, however Xerces (and apparently Crimson) implement both NodeList and Element on the same class and the mistaken casts succeeded.  The problem wasn't detected in the ECMAScript bindings since there are no explicit casts and we haven't implemented any return type checking.

The improper type was in the original commit.

  ----- Original Message ----- 
  From: Mary Brady 
  To: Freek de Bruijn ; www-dom-ts@w3.org 
  Sent: Monday, November 19, 2001 10:45 AM
  Subject: Re: Test nodeparentnodenull (DOM level 1)


  Actually in the original test, it is an Element - it appears that the DOM L1 java binding 
  returns an Element from the createElement method that is used for the createdNode 
  variable.

  --Mary
    ----- Original Message ----- 
    From: Freek de Bruijn 
    To: www-dom-ts@w3.org 
    Sent: Monday, November 19, 2001 5:43 AM
    Subject: Test nodeparentnodenull (DOM level 1)


    In the DOM level 1 test nodeparentnodenull, the variable createdNode is declared with type NodeList. I think this should be type Node. The line "<var name="createdNode" type="NodeList"/>" should probably be modified to "<var name="createdNode" type="Node"/>".

    Regards, Freek 
Received on Wednesday, 21 November 2001 00:30:20 GMT

This archive was generated by hypermail 2.2.0+W3C-0.50 : Monday, 6 April 2009 12:58:45 GMT