Bug 221546

Summary: history.back() in a new tab incorrectly loads its parent page in the same tab, instead of closing it
Product: WebKit Reporter: potassium634iodide828
Component: HistoryAssignee: Nobody <webkit-unassigned>
Status: NEW    
Severity: Major CC: achristensen, beidson, smoley, webkit-bug-importer
Priority: P2 Keywords: InRadar
Version: Safari 14   
Hardware: iPhone / iPad   
OS: iOS 14   
See Also: https://bugs.webkit.org/show_bug.cgi?id=221547
Attachments:
Description Flags
demonstration video of this bug none

potassium634iodide828
Reported 2021-02-08 05:47:16 PST
Created attachment 419580 [details] demonstration video of this bug Safari version: Safari 604.1 iOS version: iOS 14.2 Sample URL: https://ss1.xrea.com/ango.g3.xrea.com/jkkn/safari_bug2.html Step to reproduce the issue: 1. Open a new tab via target="_blank" 2. history.back() Expected results: history.back() should do nothing (like other browsers) or close the new tab (just like the back button at the bottom left) Actually results: history.back() loads its parent page in the same tab, and doesn't close the new tab. As a result, the tabs look like they are duplicated. Please check the attached video. Note: This bug might be related to Issue 8980387: https://feedbackassistant.apple.com/feedback/8980387
Attachments
demonstration video of this bug (7.15 MB, video/mp4)
2021-02-08 05:47 PST, potassium634iodide828 		no flags
Details
View All Add attachment proposed patch, testcase, etc.
potassium634iodide828
Comment 1 2021-02-08 05:53:12 PST
*Note: This bug might be related to Bug 221547: https://bugs.webkit.org/show_bug.cgi?id=221547
Radar WebKit Bug Importer
Comment 2 2021-02-15 05:48:16 PST
<rdar://problem/74347369>
Smoley
Comment 3 2021-02-15 20:00:51 PST
Thanks for filing, I can reproduce this on iOS 13.6.1 and the latest 14.4 beta.
potassium634iodide828
Comment 4 2021-02-23 17:29:35 PST
I wrote another sample code here: https://ss1.xrea.com/ango.g3.xrea.com/jkkn/safari_bug_sample.html Please feel free to use this sample in debugging Bug 221546 and Bug 221547.
Note You need to log in before you can comment on or make changes to this bug.