location.replace() breaks same-document back/forward navigations.

location.replace() breaks same-document back/forward navigations.

For navigations that don't create a new entry in the back/forward list (like
location.replace), we don't create a new HistoryItem, we just update the
existing one. If the url changes, we currently update some id numbers as well:
the item sequence number (which uniquely identifies the item), and the
document sequence number (which is common among history items that can be
navigated between without creating a new document). For a location.replace()
within the same document, we still need to change the item sequence number
(so that a back navigation is guaranteed to do something), but the document
sequence number should *not* update, so that a same-document navigation is
still possible.

BUG=363724
TEST=fast/loader/back-after-same-document-location-replace.html

Committed: https://src.chromium.org/viewvc/blink?view=rev&revision=173045

[abarth-chromium, 2014-04-30 22:41:52]

lgtm

[Nate Chapin, 2014-04-30 22:44:19]

The CQ bit was checked by japhet@chromium.org

[commit-bot: I haz the power, 2014-04-30 22:44:47]

CQ is trying da patch. Follow status at
https://chromium-status.appspot.com/cq/japhet@chromium.org/267613003/1

[commit-bot: I haz the power, 2014-05-01 00:42:51]

Change committed as 173045