Bug 243124

Summary: New tab is stuck in page loading about:blank while onload is called to close tab
Product: WebKit Reporter: Ahmad Saleem <ahmad.saleem792>
Component: Page LoadingAssignee: Nobody <webkit-unassigned>
Status: RESOLVED CONFIGURATION CHANGED    
Severity: Normal CC: achristensen, ap, beidson, bfulgham, cdumez, karlcow, rniwa, webkit-bug-importer
Priority: P2 Keywords: BrowserCompat, InRadar
Version: Safari 15   
Hardware: Mac (Apple Silicon)   
OS: macOS 12   
URL: https://bug395634.bmoattachments.org/attachment.cgi?id=280317

Description Ahmad Saleem 2022-07-22 17:48:35 PDT 
Hi Team,

Thanks for doing good job continuously.

While trying to dig through onload related test cases to determine some bug in Webkit, I came across another test case from Mozilla Bugzilla, where Safari just get stuck in page loading state:

Test Case URL - https://bug395634.bmoattachments.org/attachment.cgi?id=280317

*** STEPS TO REPRODUCE ***

1. Load Test Case URL
2. Press "Click Me"

ACTUAL RESULT:

New tab will open with about:blank and it will be in loading state.

EXPECTED RESULT:

Chrome opens this test case and new tab with about:blank but Firefox does not open new tab and close abruptly on this testcase

Ideally, I think Chrome behavior is better rather than being stuck in page loading and showing progress bar that it is loading.

________

I hope this will get your attention and will be fixed.

Thanks - Keep going!!
Comment 1 Karl Dubost 2022-07-25 00:07:12 PDT 
Ahmad, which bug was it on Mozilla Bugzilla?
Comment 2 Ahmad Saleem 2022-07-25 01:26:11 PDT 
(In reply to Karl Dubost from comment #1)
> Ahmad, which bug was it on Mozilla Bugzilla?

Here you go - https://bugzilla.mozilla.org/show_bug.cgi?id=395634
Comment 3 Radar WebKit Bug Importer 2022-07-25 09:19:39 PDT 
<rdar://problem/97553475>
Comment 4 Ahmad Saleem 2023-02-02 16:36:11 PST 
I tested this on WebKit Trunk based on 259744@main and using run-safar --release and the new tab does not go to loading state. I consider this as fixed.

I am going to mark this as "RESOLVED CONFIGURATION CHANGED". Thanks!