Bug 249299
| Summary: | Check documentElement conditions in parser* DOM mutation methods | ||
|---|---|---|---|
| Product: | WebKit | Reporter: | Ahmad Saleem <ahmad.saleem792> |
| Component: | DOM | Assignee: | Nobody <webkit-unassigned> |
| Status: | NEW | ||
| Severity: | Normal | CC: | rniwa, webkit-bug-importer |
| Priority: | P2 | Keywords: | InRadar |
| Version: | Safari Technology Preview | ||
| Hardware: | Unspecified | ||
| OS: | Unspecified | ||
Ahmad Saleem
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!
| Attachments | ||
|---|---|---|
| Add attachment proposed patch, testcase, etc. |
Radar WebKit Bug Importer
<rdar://problem/103593147>
Ryosuke Niwa
It seem sensible to merge this change.