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 418 - noderemovechild07 can raise NO_MODIFICATION
Summary: noderemovechild07 can raise NO_MODIFICATION
Status: REOPENED
Alias: None
Product: DOM TS
Classification: Unclassified
Component: DOM Level 3 (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-12 14:49 UTC by Andrew Clover
Modified: 2005-03-09 19:35 UTC (History)
0 users

See Also:

Attachments
Fix for noderemovechild07 (482 bytes, patch)
2003-12-12 14:51 UTC, Andrew Clover 		Details
Removes existing doctype, tolerates NOT_SUPPORTED_ERR (2.98 KB, patch)
2004-01-06 16:20 UTC, Curt Arnold 		Details
Real patch, previous patch is for bug 417 (1.76 KB, patch)
2004-01-06 16:53 UTC, Curt Arnold 		Details

Description Andrew Clover 2003-12-12 14:49:43 UTC 
level3/core/noderemovechild07:

Tries to remove a Document node from a Notation node, expecting 'not found'.
But notations are read-only, so NO_MODIFICATION_ALLOWED_ERR is
just as possible.
Comment 1 Andrew Clover 2003-12-12 14:51:04 UTC 
Created attachment 95 [details]
Fix for noderemovechild07

Try to remove document from itself instead. Not readonly so should only raise
NOT_FOUND as intended.
Comment 2 Curt Arnold 2004-01-06 16:20:39 UTC 
Created attachment 165 [details]
Removes existing doctype, tolerates NOT_SUPPORTED_ERR
Comment 3 Curt Arnold 2004-01-06 16:53:22 UTC 
Created attachment 167 [details]
Real patch, previous patch is for bug 417
Comment 4 Andrew Clover 2005-03-09 19:35:55 UTC 
Reopening as the same root problem also affects noderemovechild04,
noderemovechild05 in level3/core. Same fix is desirable.