Bug 249299 - Check documentElement conditions in parser* DOM mutation methods
Summary: Check documentElement conditions in parser* DOM mutation methods
Status: NEW
Alias: None
Product: WebKit
Classification: Unclassified
Component: DOM (show other bugs)
Version: Safari Technology Preview
Hardware: Unspecified Unspecified
: P2 Normal
Assignee: Nobody
URL:
Keywords: InRadar
Depends on:
Blocks:
 
Reported: 2022-12-14 03:20 PST by Ahmad Saleem
Modified: 2023-01-09 11:04 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-14 03:20:05 PST 
Hi Team,

While going through Blink's commit, I came across a test case where all browsers differ:

Test Case - https://jsfiddle.net/ckqy396n/

Blink's Commit - https://chromium.googlesource.com/chromium/blink/+/806c35622c8a96348b269aa00e00b3f5c4648709

*** Safari Technology 159 & Safari 16.2 ***

document.documentElement.outerHTML: <a></a>
document.childNodes.length: 2
b element: [object HTMLElement]

*** Chrome Canary 110 ***

document.documentElement.outerHTML: <a></a>
document.childNodes.length: 1
b element: null

*** Firefox Nightly 110 ***

Nothing - Nada... No output / alert etc

___

Just wanted to raise this bug to get input whether there is something to fix here or raise web-spec clarification.

Thanks!
Comment 1 Radar WebKit Bug Importer 2022-12-21 03:21:15 PST 
<rdar://problem/103593147>
Comment 2 Ryosuke Niwa 2023-01-09 11:04:12 PST 
It seem sensible to merge this change.