365 2003-10-20 19:27:54 +0000 DOM Level 1 Core node value test errors 2003-11-19 06:07:39 +0000 1 1 1 Unclassified DOM TS DOM Level 1 unspecified Other other RESOLVED INVALID P2 normal --- 1 bob carnold oldest_to_newest 817 0 bob 2003-10-20 19:27:54 +0000 hc_nodevalue01, hc_nodevalue05, hc_nodevalue06 each test that the modified value of a node.nodeValue should not change upon setting. Setting the value should according to the referenced specification <http://www.w3.org/TR/1998/REC-DOM-Level-1-19981001/level-one-core#ID-F68D080> throw a NO_MODIFICATION_ALLOWED_ERR exception which causes the tests to fail with an error rather than testing if the value has changed. This test should be rewritten to test for the exception or at least trap the exception before attempting to test the value. 818 1 bob 2003-10-20 19:43:28 +0000 The same error occurs in nodevalue01, nodevalue05, nodevalue06. 831 2 bob 2003-11-03 16:25:20 +0000 Curt, Even though the DOM Level 2 Core spec <http://www.w3.org/TR/DOM-Level-2-Core/core.html#ID-F68D080> does say that if the nodeValue is null, setting it should have no effect and should not therefore throw an exception, the DOM Level 1 Core spec is not clear on this point. Implementations which followed a reaonable interpretation of DOM Level 1 Core would fail while those that followed DOM Level 2 Core would pass which would be kind of odd for DOM Level 1 Core tests. For example, Mozilla 1.5 and prior will fail these tests since they throw the exception but Mozilla 1.6 will pass since the behavior in this case was changed to match the DOM Level 2 Core spec. I believe these tests are more appropriate in DOM Level 2 Core than in DOM Level 1 Core and should be moved there. 863 3 carnold 2003-11-19 01:07:39 +0000 The WG resolution when this was raised earlier was posted to www-dom-ts as http://lists.w3.org/Archives/Public/www-dom-ts/2002Mar/0088.html. The tests reflect that resolution and unless the WG reopens the issue and provides new instructions, I'm marking this bug as invalid.