Bug 249619 - Document::nodeWillBeRemoved() should handle node in different document
Summary: Document::nodeWillBeRemoved() should handle node in different document
Status: RESOLVED INVALID
Alias: None
Product: WebKit
Classification: Unclassified
Component: DOM (show other bugs)
Version: Safari Technology Preview
Hardware: Unspecified Unspecified
: P2 Normal
Assignee: Nobody
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2022-12-19 17:03 PST by Ahmad Saleem
Modified: 2022-12-19 19:48 PST (History)
2 users (show)

See Also:

Attachments
Add an attachment (proposed patch, testcase, etc.)

Note You need to log in before you can comment on or make changes to this bug.
Description Ahmad Saleem 2022-12-19 17:03:45 PST 
Hi Team,

While going through DOM bugs, I came cross following failing test in Safari 16.2 and Safari Technology Preview 160:

Test Case - https://jsfiddle.net/926wnqvg/

^It passes Chrome Canary 111 and Firefox Nightly 110.

Blink Commit - https://chromium.googlesource.com/chromium/src.git/+/48227c770ed61333226a41c6d054ba06e863668e

I will not be able to do this fix and would appreciate if someone else can take it up.

Thanks!
Comment 1 Ryosuke Niwa 2022-12-19 19:48:21 PST 
This is only failing in WebKit because the test assumes very specific exception message. We're still throwing the same exception (NotFoundError) as Blink.