OOPIF: Stop using HistoryController and refactor UpdateState.
In OOPIF-enabled builds, we no longer need to track the current
HistoryEntry or use HistoryController. Instead, the current
WebHistoryItem is stored on each RenderFrame.
This also moves UpdateState to RenderFrame{Host}, ensuring that
PageState objects can be stored on each frame's FrameNavigationEntry.
These changes only affect Chrome with --site-per-process or
--isolate-extensions.
BUG=545219, 236848
Review URL: https://codereview.chromium.org/1425303002
Cr-Commit-Position: refs/heads/master@{#357921}
diff --git a/content/browser/web_contents/web_contents_impl.h b/content/browser/web_contents/web_contents_impl.h
index 73a3a2a..779dd38 100644
--- a/content/browser/web_contents/web_contents_impl.h
+++ b/content/browser/web_contents/web_contents_impl.h
@@ -415,6 +415,8 @@
void DidChangeName(RenderFrameHost* render_frame_host,
const std::string& name) override;
void DocumentOnLoadCompleted(RenderFrameHost* render_frame_host) override;
+ void UpdateStateForFrame(RenderFrameHost* render_frame_host,
+ const PageState& page_state) override;
void UpdateTitle(RenderFrameHost* render_frame_host,
int32 page_id,
const base::string16& title,
