NEW310261
Same-origin navigation after BFCache restore should not fire navigateerror 
https://bugs.webkit.org/show_bug.cgi?id=310261
Summary Same-origin navigation after BFCache restore should not fire navigateerror
Noam Rosenthal
Reported 2026-03-19 00:59:20 PDT
Steps to reproduce: navigate to a new document (e.g. using navigate()) go back, asserting that BFCache took place Perform a same-document navigation (e.g. history.pushState) Actual results: navigateerror was fired, and the original navigate().finished promise rejects, as if the new pushState() aborted the original navigate(). Expected results: navigatesuccess should fire, and the original navigate().finished promise should hang. See https://github.com/whatwg/html/pull/12024 and its WPT
Attachments
Add attachment proposed patch, testcase, etc.
Radar WebKit Bug Importer
Comment 1 2026-03-26 01:00:14 PDT
<rdar://problem/173388887>
Note You need to log in before you can comment on or make changes to this bug.