Always commit same-document navigations to the current RenderFrameHost
Step 4 for bug 1125106. This is a subset of the mega-patch in https://chromium-review.googlesource.com/c/chromium/src/+/2462248. A same-document navigation is a request to navigate the currently loaded document to the specified anchor tag from the URL. Renderer-initiated navigations simply perform the scroll operation and update history. Browser-initiated ones are treated as a navigation. However there are many things that could cause the given URL to want to load in a different SiteInstance than what was used for the previous load. But using a different SiteInstance would also mean reloading the document - which means it is no longer a same-document navigation. Previous patches in this series have prevented us from trying to load a same-document navigation when there would be valid reasons to want to do a cross-document navigation. Follow-up patches will introduce CHECK()s in the renderer to show that we are in fact never trying to perform a same-document navigation anymore when we would have required a cross-document navigation (with the exception of navigating a frameset which must fallback to cross- document). R=nasko@chromium.org Bug: 1125106 Change-Id: I3603cb0a3698d9e6241aca4eb8895db4fcdfd139 Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2558760 Commit-Queue: danakj <danakj@chromium.org> Reviewed-by:Nasko Oskov <nasko@chromium.org> Cr-Commit-Position: refs/heads/master@{#833067}
Showing
This diff is collapsed.
Please register or sign in to comment