Some overlapping navigation/traversal cases cause the outer frame to get reloaded

• Component: Page Loading
• Status: NEW ---

[Domenic Denicola]

In https://github.com/whatwg/html/issues/6927 we are investigating the general non-interoperable area of overlapping navigations and traversals, e.g. history.back(); history.back() or location.href = "#1"; location.href = "?2", or mixes thereof.

This is a big mess in general and the spec isn't helpful. However, some cross-browser testing revealed a couple of interesting cases where WebKit seems to definitely be doing the wrong thing:

- https://wpt.fyi/results/html/browsers/browsing-the-web/overlapping-navigations-and-traversals/tentative/cross-document-traversal-same-document-traversal.html?label=master&label=experimental&aligned&q=overlapping-navigations
- https://wpt.fyi/results/html/browsers/browsing-the-web/overlapping-navigations-and-traversals/tentative/same-document-nav-cross-document-traversal.html?label=master&label=experimental&aligned&q=overlapping-navigations

or in wpt.live form

- http://wpt.live/html/browsers/browsing-the-web/overlapping-navigations-and-traversals/tentative/cross-document-traversal-same-document-traversal.html
- http://wpt.live/html/browsers/browsing-the-web/overlapping-navigations-and-traversals/tentative/same-document-nav-cross-document-traversal.html

For these two tests, WebKit somehow manages to reload the *outer* page. But nothing in the test should be able to cause this; all traversals and navigations should be taking place in the inner frame.

It might be worth investigating these cases, ahead of investigating the general interop problem around overlapping navigations/traversals.

[Radar WebKit Bug Importer]

<rdar://problem/82878605>