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

SV: Multiple potential exceptions: nodereplacechildnewchilddiffdo cument

From: Dimitris Dimitriadis <dimitris.dimitriadis@improve.se>
Date: Wed, 22 Aug 2001 19:32:02 +0200
Message-ID: <9F67DC27F4CCD311ABA600508B6A66A44A6CE7@VXOIMP1>
To: "'Curt Arnold'" <carnold@houston.rr.com>, www-dom-ts@w3.org
Given the opportunity:
To simplify administration and reporting to the WG, could all mails that
pertain to ambiguities in the spec be prefixed with [Spec ambiguity] in the

-----Ursprungligt meddelande-----
Från: Curt Arnold [mailto:carnold@houston.rr.com]
Skickat: den 22 augusti 2001 19:29
Till: www-dom-ts@w3.org
Ämne: Multiple potential exceptions: nodereplacechildnewchilddiffdocument

nodereplacechildnewchilddiffdocument.xml is a strange case.  
It calls Node.replaceChild with a old node that is not a child of the target
node and attempts to replace it with a node that isn't part of this
document.  So it could conceivable throw either NOT_FOUND_ERR or
WRONG_DOCUMENT_ERR depending on which condition it tested first.  I don't
believe there is anything in the DOM spec that would prescribe which
exception code should take precedence and DOMTSML doesn't have a construct
to support an ambiguous exception code.
The test is internally inconsistant since the description says
The "replaceChild(newChild,oldChild)" method raises a 
WRONG_DOCUMENT_ERR DOMException if the "newChild" was
created from a different document than the one that 
created this node.

But the test checks for NOT_FOUND_ERR.  I'm going to make the body
consistent with the description.
Received on Wednesday, 22 August 2001 13:40:37 UTC

This archive was generated by hypermail 2.3.1 : Tuesday, 6 January 2015 20:34:03 UTC