Bug 310261
| Summary: | Same-origin navigation after BFCache restore should not fire navigateerror | ||
|---|---|---|---|
| Product: | WebKit | Reporter: | Noam Rosenthal <noam> |
| Component: | History | Assignee: | Nobody <webkit-unassigned> |
| Status: | NEW | ||
| Severity: | Normal | CC: | webkit-bug-importer |
| Priority: | P2 | Keywords: | InRadar |
| Version: | WebKit Nightly Build | ||
| Hardware: | Unspecified | ||
| OS: | Unspecified | ||
Noam Rosenthal
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
<rdar://problem/173388887>