Remove document sequence number update from HistoryEntry.
This code appears unnecessary and dates back to early changes in
WebKit when it might have been needed. We don't have an equivalent
in the new FrameNavigationEntry-based path, so this CL shows that
it should be safe to remove.
This is also a speculative attempt to find cases where the two
navigation paths differ in a way that could cause a NC_AUTO_SUBFRAME
renderer kill, since this code can affect whether a navigation is
considered in-page.
BUG=613732
TEST=No behavior change
Review-Url: https://codereview.chromium.org/2085163002
Cr-Commit-Position: refs/heads/master@{#401634}
2 files changed
