Chromium Code Reviews
chromiumcodereview-hr@appspot.gserviceaccount.com (chromiumcodereview-hr) | Please choose your nickname with Settings | Help | Chromium Project | Gerrit Changes | Sign out
(62)

Issue 2239413002: Don't mark a history navigation as in page in a new renderer process. (Closed)

Created:
4 years, 4 months ago by Charlie Reis
Modified:
4 years, 4 months ago
Reviewers:
nasko
CC:
chromium-reviews, jam, nasko+codewatch_chromium.org, darin-cc_chromium.org, creis+watch_chromium.org, mlamouri+watch-content_chromium.org, site-isolation-reviews_chromium.org
Base URL:
https://chromium.googlesource.com/chromium/src.git@master
Target Ref:
refs/pending/heads/master
Project:
chromium
Visibility:
Public.

Description

Don't mark a history navigation as in page in a new renderer process. Blink won't realize that the page needs to be loaded from scratch and will stay in-page on the initial blank page. This became a problem when moving the in-page determination to the browser process, where we need to check whether the renderer process has a committed page or not. BUG=635403 TEST=Ctrl+back in page (see bug comment 4 for repro steps) CQ_INCLUDE_TRYBOTS=master.tryserver.chromium.linux:linux_site_isolation Committed: https://crrev.com/5413169e62dc4c20d31e1afaea680f943bbe085c Cr-Commit-Position: refs/heads/master@{#411712}

Patch Set 1 #

Unified diffs Side-by-side diffs Delta from patch set Stats (+69 lines, -1 line) Patch
M content/browser/frame_host/navigation_controller_impl.cc View 1 chunk +8 lines, -1 line 0 comments Download
M content/browser/frame_host/navigation_controller_impl_browsertest.cc View 1 chunk +51 lines, -0 lines 0 comments Download
M content/renderer/render_frame_impl.cc View 1 chunk +10 lines, -0 lines 0 comments Download

Messages

Total messages: 12 (7 generated)
Charlie Reis
Nasko, can you take a look? The renderer-side check is just to be safe against ...
4 years, 4 months ago (2016-08-12 16:59:32 UTC) #5
nasko
LGTM
4 years, 4 months ago (2016-08-12 17:15:43 UTC) #6
commit-bot: I haz the power
CQ is trying da patch. Follow status at https://chromium-cq-status.appspot.com/v2/patch-status/codereview.chromium.org/2239413002/1
4 years, 4 months ago (2016-08-12 17:33:50 UTC) #9
commit-bot: I haz the power
Committed patchset #1 (id:1)
4 years, 4 months ago (2016-08-12 18:32:41 UTC) #10
commit-bot: I haz the power
4 years, 4 months ago (2016-08-12 18:35:35 UTC) #12
Message was sent while issue was closed.
Patchset 1 (id:??) landed as
https://crrev.com/5413169e62dc4c20d31e1afaea680f943bbe085c
Cr-Commit-Position: refs/heads/master@{#411712}

Powered by Google App Engine
This is Rietveld 408576698