Revert of OOPIF: Fix subframe back/forward after recreating FTNs.

Revert of OOPIF: Fix subframe back/forward after recreating FTNs. (patchset #6 id:100001 of https://codereview.chromium.org/1816763002/ )

Reason for revert:
This appears to have caused browser crashes in https://crbug.com/603245.

Original issue's description:
> OOPIF: Fix subframe back/forward after recreating FTNs.
>
> In some cases, we would navigate the main frame when going back/forward
> in a subframe.  This was because the FTN ID had changed from what was
> stored in the FrameNavigationEntry.  We can now use the frame's unique
> name to find the FrameNavigationEntry as well.
>
> Also relaxes the restriction that a FrameNavigationEntry's item and
> document sequence numbers don't change, at least until
> https://crbug.com/596707 is fixed.
>
> BUG=586324, 568768
> TEST=See bug for repro steps.
> CQ_INCLUDE_TRYBOTS=tryserver.chromium.linux:linux_site_isolation
>
> Committed: https://crrev.com/273cbf61991e5339108de04c8a51fdb00a0916d5
> Cr-Commit-Position: refs/heads/master@{#386756}

TBR=alexmos@chromium.org
# Not skipping CQ checks because original CL landed more than 1 days ago.
BUG=586324, 568768
Committed: https://crrev.com/e7b0a15f687a1a5efe0d6c2c8fc68b4d0b472bcb
Cr-Commit-Position: refs/heads/master@{#387126}

[Charlie Reis, 2016-04-13 21:20:35]

Created Revert of OOPIF: Fix subframe back/forward after recreating FTNs.

[commit-bot: I haz the power, 2016-04-13 21:20:59]

CQ is trying da patch. Follow status at
 https://chromium-cq-status.appspot.com/patch-status/1889583003/1
View timeline at
 https://chromium-cq-status.appspot.com/patch-timeline/1889583003/1

[commit-bot: I haz the power, 2016-04-13 21:31:49]

CQ is trying da patch. Follow status at
 https://chromium-cq-status.appspot.com/patch-status/1889583003/1
View timeline at
 https://chromium-cq-status.appspot.com/patch-timeline/1889583003/1

[commit-bot: I haz the power, 2016-04-13 22:01:44]

CQ is trying da patch. Follow status at
 https://chromium-cq-status.appspot.com/patch-status/1889583003/1
View timeline at
 https://chromium-cq-status.appspot.com/patch-timeline/1889583003/1

[commit-bot: I haz the power, 2016-04-13 22:30:11]

Committed patchset #1 (id:1)

[commit-bot: I haz the power, 2016-04-13 22:31:28]

Description was changed from

==========
Revert of OOPIF: Fix subframe back/forward after recreating FTNs. (patchset #6
id:100001 of https://codereview.chromium.org/1816763002/ )

Reason for revert:
This appears to have caused browser crashes in https://crbug.com/603245.

Original issue's description:
> OOPIF: Fix subframe back/forward after recreating FTNs.
> 
> In some cases, we would navigate the main frame when going back/forward
> in a subframe.  This was because the FTN ID had changed from what was
> stored in the FrameNavigationEntry.  We can now use the frame's unique
> name to find the FrameNavigationEntry as well.
> 
> Also relaxes the restriction that a FrameNavigationEntry's item and
> document sequence numbers don't change, at least until
> https://crbug.com/596707 is fixed.
> 
> BUG=586324, 568768
> TEST=See bug for repro steps.
> CQ_INCLUDE_TRYBOTS=tryserver.chromium.linux:linux_site_isolation
> 
> Committed: https://crrev.com/273cbf61991e5339108de04c8a51fdb00a0916d5
> Cr-Commit-Position: refs/heads/master@{#386756}

TBR=alexmos@chromium.org
# Not skipping CQ checks because original CL landed more than 1 days ago.
BUG=586324, 568768
==========

to

==========
Revert of OOPIF: Fix subframe back/forward after recreating FTNs. (patchset #6
id:100001 of https://codereview.chromium.org/1816763002/ )

Reason for revert:
This appears to have caused browser crashes in https://crbug.com/603245.

Original issue's description:
> OOPIF: Fix subframe back/forward after recreating FTNs.
>
> In some cases, we would navigate the main frame when going back/forward
> in a subframe.  This was because the FTN ID had changed from what was
> stored in the FrameNavigationEntry.  We can now use the frame's unique
> name to find the FrameNavigationEntry as well.
>
> Also relaxes the restriction that a FrameNavigationEntry's item and
> document sequence numbers don't change, at least until
> https://crbug.com/596707 is fixed.
>
> BUG=586324, 568768
> TEST=See bug for repro steps.
> CQ_INCLUDE_TRYBOTS=tryserver.chromium.linux:linux_site_isolation
>
> Committed: https://crrev.com/273cbf61991e5339108de04c8a51fdb00a0916d5
> Cr-Commit-Position: refs/heads/master@{#386756}

TBR=alexmos@chromium.org
# Not skipping CQ checks because original CL landed more than 1 days ago.
BUG=586324, 568768

Committed: https://crrev.com/e7b0a15f687a1a5efe0d6c2c8fc68b4d0b472bcb
Cr-Commit-Position: refs/heads/master@{#387126}
==========

[commit-bot: I haz the power, 2016-04-13 22:31:30]

Patchset 1 (id:??) landed as
https://crrev.com/e7b0a15f687a1a5efe0d6c2c8fc68b4d0b472bcb
Cr-Commit-Position: refs/heads/master@{#387126}