Bug 243131 – document.close, scripts in document.write, and later-defined onload event handlers

• Component: Page Loading
• Status: NEW

[Ahmad Saleem]

Hi Team,

Another test case, which I found in Mozilla Bugzilla to see where for onload Safari behavior is different from other browsers:

*** STEPS TO REPRODUCE ***

1 - Load test URL - https://bug204497.bmoattachments.org/attachment.cgi?id=

>>>> ACTUAL RESULT:

Safari should onAlert dialog window with 777 in it and then after dismissing, it loads body with 'y' in it.

>>>> EXPECTED RESULT:

Firefox Nightly 104 and Chrome Canary 105 does not show 777 dialog window and just load body with 'y' in it.

As per Mozilla bug report - it should show 'Alert' window but I am not sure on the web-specs here but since Safari behavior is different (whether aligned with web-spec or not), I just wanted to raise this bug report.

Thanks

[Ahmad Saleem]

For some reason - test URL in Description / Comment 0 is broken, please use from URL field or below:

Link - https://bug204497.bmoattachments.org/attachment.cgi?id=267050

[Sam Sneddon [:gsnedders]]

(In reply to Ahmad Saleem from comment #0)
> As per Mozilla bug report - it should show 'Alert' window but I am not sure
> on the web-specs here but since Safari behavior is different (whether
> aligned with web-spec or not), I just wanted to raise this bug report.

Pretty sure Firefox and Chrome are right v. HTML today.

That said, I suspect this is more about when HTML says to spin the event loop and when document.close stops parsing than anything else.

[Radar WebKit Bug Importer]

<rdar://problem/97487338>