Bug 264068 – Don't let 'dispatchChildRemovalEvents' conflict while removing node reference with a node in different document

• Status: NEW
• Component: DOM

[Ahmad Saleem]

Hi Team,

While going through Blink's commit, I came across failing test case:

Test Case: https://jsfiddle.net/L2ewu96t/show

^ fails in STP182 but passes in Firefox Nightly 121 and Chrome Canary 121.

Blink Commit: https://chromium.googlesource.com/chromium/blink/+/108683ca37c76cd4a422c4d4a64a989a600dd761

^ From quick looks, it is not possible for me to merge this.

Thanks!

[Karl Dubost]

so not sure, the test is well done.

Safari. FAIL

assert_equals(
  "NotFoundError: The object can not be found here.", 
  "NotFoundError: Failed to execute 'appendChild' on 'Node': The node to be removed is no longer a child of this node. Perhaps it was moved in response to a mutation?"
)


Firefox. PASS

but with assert not ran. 


Chrome. PASS

assert_equals(
   "NotFoundError: Failed to execute 'appendChild' on 'Node': The node to be removed is no longer a child of this node. Perhaps it was moved in response to a mutation?",    "NotFoundError: Failed to execute 'appendChild' on 'Node': The node to be removed is no longer a child of this node. Perhaps it was moved in response to a mutation?"
)



So Chrome and WebKit seems to have the same behavior but a different error message.
Firefox is probably not going to the error, because it is doing the steps. 


This needs a better test. :)

[Radar WebKit Bug Importer]

<rdar://problem/118145980>