16606 - replaceChild(newnode,document) throws wrong exception

Status: VERIFIED FIXED

(Core :: DOM: Core & HTML, defect, P3)

Description

[David Baron :dbaron: (⌚️UTC-5, no longer working on Mozilla)]

DESCRIPTION:  Calling Node.replaceChild(newnode,document) should throw a
NOT_FOUND_ERR rather than a HIERARCHY_REQUEST_ERR because the document is not an
already existing child of Node.  A HIERARCHY_REQUEST_ERR would be appropriate if
document were the first argument and were being inserted.

STEPS TO REPRODUCE:
 * Load http://www.fas.harvard.edu/~dbaron/dom/test/one-core-xml/exceptions
   or http://www.fas.harvard.edu/~dbaron/dom/test/one-core-html/exceptions
 * hit test

ACTUAL RESULTS:
 * the line below the line "Trying helem.replaceChild(pelem,document) :" is
   red.  This line is right before the bold heading starting the tests for
   removeChild().  It currently shows that a HIERARCHY_REQUEST_ERR is being
   thrown.

EXPECTED RESULTS:
 * the line should be green

DOES NOT WORK CORRECTLY ON:
 * Linux, viewer, 1999-10-15-11-M11

Comment 1

[David Baron :dbaron: (⌚️UTC-5, no longer working on Mozilla)]

calling removeChild(document) has the exact same problem.  It should throw
NOT_FOUND_ERR, I think, rather than HIERARCHY_REQUEST_ERR.  removeChild() is
definitely not permitted to throw a HIERARCHY_REQUEST_ERR - it's not among the
listed codes.

The relevant test is the one right below the previous one described - the first
test under the removeChild() section.

Comment 2

[vidur (gone)]

In an attempt to get my bug list in order again, marking all the bugs I have
currently as ASSIGNED.

Comment 3

[vidur (gone)]

Johnny Stenback has a fix for this waiting in his tree.

Comment 4

[Johnny Stenback (:jst)]

The fix is checked in now, marking FIXED.

Comment 5

[Jan Carpenter]

Mass update of qa contact

Comment 6

[Prashant Desale]

QA contact Update

Comment 7

[Prashant Desale]

Updating QA contact to Shivakiran Tummala.

Comment 8

[Sivakiran Tummala]

verified