This is an archived snapshot of W3C's public bugzilla bug tracker, decommissioned in April 2019. Please see the home page for more details.

Bug 406 - L1 invalidnodetype tests may also raise NOT_FOUND_ERR
Summary: L1 invalidnodetype tests may also raise NOT_FOUND_ERR
Status: RESOLVED FIXED
Alias: None
Product: DOM TS
Classification: Unclassified
Component: DOM Level 1 (show other bugs)
Version: unspecified
Hardware: All All
: P2 normal
Target Milestone: ---
Assignee: Philippe Le Hegaret
QA Contact:
URL:
Whiteboard:
Keywords:
Depends on:
Blocks:
 
Reported: 2003-12-10 17:21 UTC by Andrew Clover
Modified: 2004-01-06 17:11 UTC (History)
0 users

See Also:

Attachments
hc_node[...]invalidnodetype patch (3.52 KB, patch)
2003-12-10 17:23 UTC, Andrew Clover 		Details
Simpler fix (3.05 KB, patch)
2004-01-06 12:09 UTC, Curt Arnold 		Details

Description Andrew Clover 2003-12-10 17:21:52 UTC 
The following tests:

level1/core/hc_nodeinsertbeforeinvalidnodetype
level1/core/hc_nodereplacechildinvalidnodetype

require the implementation to raise HIERARCHY_REQUEST_ERR. However, the
refChild/oldChild argument passed is not a child of the parent node, so a
NOT_FOUND_ERR is an equally valid response.
Comment 1 Andrew Clover 2003-12-10 17:23:51 UTC 
Created attachment 87 [details]
hc_node[...]invalidnodetype patch

Fix, ensures the right parent node is used.

NB: works on my Python setup, has *not* been tested with the Java TS framework.
Comment 2 Curt Arnold 2004-01-06 12:09:31 UTC 
Created attachment 163 [details]
Simpler fix