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 113758: Remove the HistoryState property of WebRequest.... (Closed)

Created:
11 years, 7 months ago by darin (slow to review)
Modified:
9 years, 7 months ago
Reviewers:
brettw
CC:
chromium-reviews_googlegroups.com
Visibility:
Public.

Description

Remove the HistoryState property of WebRequest. In the new WebKit API, it seems best if WebRequest is just a wrapper for WebCore::ResourceRequest since in most contexts that's what we need it to be. The solution here is to introduce a LoadHistoryState method on WebFrame that can be used to navigate to a session history item. BUG=10038 TEST=covered by existing back/forward navigation tests. R=brettw Committed: http://src.chromium.org/viewvc/chrome?view=rev&revision=16747

Patch Set 1 #

Total comments: 1

Patch Set 2 : '' #

Patch Set 3 : '' #

Unified diffs Side-by-side diffs Delta from patch set Stats (+84 lines, -78 lines) Patch
M chrome/renderer/render_view.cc View 1 2 chunks +31 lines, -21 lines 0 comments Download
M webkit/glue/webframe.h View 1 1 chunk +4 lines, -0 lines 0 comments Download
M webkit/glue/webframe_impl.h View 1 2 chunks +2 lines, -0 lines 0 comments Download
M webkit/glue/webframe_impl.cc View 1 4 chunks +14 lines, -5 lines 0 comments Download
M webkit/glue/weburlrequest.h View 1 1 chunk +0 lines, -4 lines 0 comments Download
M webkit/glue/weburlrequest_impl.h View 1 2 chunks +0 lines, -7 lines 0 comments Download
M webkit/glue/weburlrequest_impl.cc View 1 1 chunk +0 lines, -10 lines 0 comments Download
M webkit/tools/test_shell/test_shell.cc View 1 1 chunk +33 lines, -31 lines 0 comments Download

Messages

Total messages: 2 (0 generated)
darin (slow to review)
11 years, 7 months ago (2009-05-22 06:26:33 UTC) #1
brettw
11 years, 7 months ago (2009-05-22 15:50:49 UTC) #2
LGTM

http://codereview.chromium.org/113758/diff/1/9
File chrome/renderer/render_view.cc (right):

http://codereview.chromium.org/113758/diff/1/9#newcode807
Line 807: if (!is_reload && !params.state.empty()) {
Can you add a comment to each arm of this if statement exaplining what that
state represents? Also, it wasn't immediately clear why state.empty mattered
here, can you mention that in the comment about this?

Powered by Google App Engine
This is Rietveld 408576698