Add renderer-side CHECK()s that we don't perform invalid same-doc navs
Step 6 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 should only be performed when the commit will happen in the currently loaded document. The renderer handled the browser doing the wrong thing in all kinds of ways, due to the browser making incorrect decisions when: - On an empty error page - Having an ongoing cross-document navigation which hasn't committed yet Now the browser does the right thing, so the renderer does not need to handle the fallback - except in one case which is a frameset. In that case the browser doesn't know the document is frameset, and the renderer currently enforces a policy that same-document navigations in a frameset document cause it to be reloaded. This is done for both renderer-initiated navigations (by sending the navigation to the browser process instead of performing the navigation immediately) and then by bouncing any same-document requests from the browser back as RestartCrossDocument. R=nasko@chromium.org Bug: 1125106 Change-Id: I74ca38a2213215a107c955127f1f664b96b58aaa Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2558926 Auto-Submit: danakj <danakj@chromium.org> Commit-Queue: Daniel Cheng <dcheng@chromium.org> Reviewed-by:Nasko Oskov <nasko@chromium.org> Reviewed-by:
Daniel Cheng <dcheng@chromium.org> Cr-Commit-Position: refs/heads/master@{#843994}
Showing
Please register or sign in to comment