- From: Mary Brady <mbrady@nist.gov>
- Date: Thu, 1 Nov 2001 10:30:53 -0500
- To: "Mary Brady" <mbrady@nist.gov>, "Arnold, Curt" <Curt.Arnold@hyprotech.com>, <www-dom-ts@w3.org>
- Message-ID: <006c01c162ea$319cbf30$293b0681@HAPPY>
MessageIt appears as though after a new attribute is created with the name "newAttribute", the setAttributeNode(newAttribute) should be on newElement, not testAddress. --Mary ----- Original Message ----- From: Mary Brady To: Arnold, Curt ; www-dom-ts@w3.org Sent: Thursday, November 01, 2001 10:24 AM Subject: Re: Test elementinuseattributeerr (DOM level 1) Hmmm. Not sure -- I'll have to go back and look at what's there for the xml file. I've attached the original java source in case someone else gets to this first. The test was intended to throw an INUSE_ATTRIBUTE_ERR -- errors may have been introduced during translation to xml. --Mary ----- Original Message ----- From: Arnold, Curt To: 'www-dom-ts@w3.org' Sent: Wednesday, October 31, 2001 11:28 AM Subject: RE: Test elementinuseattributeerr (DOM level 1) Good catch. I apparently bungled that one in fixing up undeclared variables where I changed "Element" to "testAttribute" instead of "newElement". I'll have to review the results of this test since I believe that some implementations are throwing an exception. My reading is that the test as written should not throw an exception and the return value setAttr2 should be same as newAttribute. -----Original Message----- From: Freek de Bruijn [mailto:freek@x-hive.com] Sent: Wednesday, October 31, 2001 10:05 AM To: www-dom-ts@w3.org Subject: Test elementinuseattributeerr (DOM level 1) In the DOM level 1 test elementinuseattributeerr, the attribute seems to be added to the same element twice. This should not lead to an INUSE_ATTRIBUTE_ERR. We should probably create another new element and add the attribute to this second element. Regards, Freek
Received on Thursday, 1 November 2001 10:25:35 UTC