Revert of Enable subframe FrameNavigationEntries by default.

Revert of Enable subframe FrameNavigationEntries by default. (patchset #4 id:60001 of https://codereview.chromium.org/1952533003/ )

Reason for revert:
Caused several layout tests to fail:
https://build.chromium.org/p/chromium.webkit/buildstatus?builder=WebKit%20Mac10.11&number=6083

  fast/history/same-document-iframes-changing-fragment.html [ Failure ]
  fast/history/same-document-iframes-changing-pushstate.html [ Failure ]
  fast/loader/form-state-restore-with-frames.html [ Failure ]
  http/tests/misc/resource-timing-iframe-restored-from-history.html [ Failure ]
  http/tests/navigation/back-to-dynamic-iframe.html [ Failure ]
  http/tests/navigation/back-to-redirect-with-frame.php [ Failure ]
  http/tests/security/mixedContent/insecure-iframe-in-main-frame.html [ Failure ]

Original issue's description:
> Enable subframe FrameNavigationEntries by default.
>
> This is a major change to the navigation logic in Chrome, making
> the browser process responsible for selecting subframes to
> navigate.  Each NavigationEntry now has a tree of
> FrameNavigationEntries representing each frame in the page, and
> these frame entries track per-frame PageState.
>
> HistoryController in content/renderer is no longer used, since
> equivalent code in NavigationController in content/browser now
> determines which frames to navigate.
>
> This CL is designed to be easy to revert if regressions are
> found, though the new path has been in use on 50% of Canary and
> Dev channels for a while.
>
> BUG=236848
> TEST=Existing tests pass.
>
> Committed: https://crrev.com/810a396cc50315037a51e55342da6c04d1c9b260
> Cr-Commit-Position: refs/heads/master@{#401969}

TBR=boliu@chromium.org,nick@chromium.org
# Skipping CQ checks because original CL landed less than 1 days ago.
NOPRESUBMIT=true
NOTREECHECKS=true
NOTRY=true
BUG=236848
Committed: https://crrev.com/5e66abf8057e5e904c9539ee8aa2fe92161d208f
Cr-Commit-Position: refs/heads/master@{#401985}

[Charlie Reis, 2016-06-24 21:49:56]

The CQ bit was checked by creis@chromium.org

[Charlie Reis, 2016-06-24 21:49:56]

Created Revert of Enable subframe FrameNavigationEntries by default.

[commit-bot: I haz the power, 2016-06-24 21:50:18]

CQ is trying da patch. Follow status at
 
https://chromium-cq-status.appspot.com/v2/patch-status/codereview.chromium.or...

[commit-bot: I haz the power, 2016-06-24 21:51:26]

Description was changed from

==========
Revert of Enable subframe FrameNavigationEntries by default. (patchset #4
id:60001 of https://codereview.chromium.org/1952533003/ )

Reason for revert:
Caused several layout tests to fail:
https://build.chromium.org/p/chromium.webkit/buildstatus?builder=WebKit%20Mac...

  fast/history/same-document-iframes-changing-fragment.html [ Failure ]
  fast/history/same-document-iframes-changing-pushstate.html [ Failure ]
  fast/loader/form-state-restore-with-frames.html [ Failure ]
  http/tests/misc/resource-timing-iframe-restored-from-history.html [ Failure ]
  http/tests/navigation/back-to-dynamic-iframe.html [ Failure ]
  http/tests/navigation/back-to-redirect-with-frame.php [ Failure ]
  http/tests/security/mixedContent/insecure-iframe-in-main-frame.html [ Failure
]

Original issue's description:
> Enable subframe FrameNavigationEntries by default.
> 
> This is a major change to the navigation logic in Chrome, making
> the browser process responsible for selecting subframes to
> navigate.  Each NavigationEntry now has a tree of
> FrameNavigationEntries representing each frame in the page, and
> these frame entries track per-frame PageState.
> 
> HistoryController in content/renderer is no longer used, since
> equivalent code in NavigationController in content/browser now
> determines which frames to navigate.
> 
> This CL is designed to be easy to revert if regressions are
> found, though the new path has been in use on 50% of Canary and
> Dev channels for a while.
> 
> BUG=236848
> TEST=Existing tests pass.
> 
> Committed: https://crrev.com/810a396cc50315037a51e55342da6c04d1c9b260
> Cr-Commit-Position: refs/heads/master@{#401969}

TBR=boliu@chromium.org,nick@chromium.org
# Skipping CQ checks because original CL landed less than 1 days ago.
NOPRESUBMIT=true
NOTREECHECKS=true
NOTRY=true
BUG=236848
==========

to

==========
Revert of Enable subframe FrameNavigationEntries by default. (patchset #4
id:60001 of https://codereview.chromium.org/1952533003/ )

Reason for revert:
Caused several layout tests to fail:
https://build.chromium.org/p/chromium.webkit/buildstatus?builder=WebKit%20Mac...

  fast/history/same-document-iframes-changing-fragment.html [ Failure ]
  fast/history/same-document-iframes-changing-pushstate.html [ Failure ]
  fast/loader/form-state-restore-with-frames.html [ Failure ]
  http/tests/misc/resource-timing-iframe-restored-from-history.html [ Failure ]
  http/tests/navigation/back-to-dynamic-iframe.html [ Failure ]
  http/tests/navigation/back-to-redirect-with-frame.php [ Failure ]
  http/tests/security/mixedContent/insecure-iframe-in-main-frame.html [ Failure
]

Original issue's description:
> Enable subframe FrameNavigationEntries by default.
> 
> This is a major change to the navigation logic in Chrome, making
> the browser process responsible for selecting subframes to
> navigate.  Each NavigationEntry now has a tree of
> FrameNavigationEntries representing each frame in the page, and
> these frame entries track per-frame PageState.
> 
> HistoryController in content/renderer is no longer used, since
> equivalent code in NavigationController in content/browser now
> determines which frames to navigate.
> 
> This CL is designed to be easy to revert if regressions are
> found, though the new path has been in use on 50% of Canary and
> Dev channels for a while.
> 
> BUG=236848
> TEST=Existing tests pass.
> 
> Committed: https://crrev.com/810a396cc50315037a51e55342da6c04d1c9b260
> Cr-Commit-Position: refs/heads/master@{#401969}

TBR=boliu@chromium.org,nick@chromium.org
# Skipping CQ checks because original CL landed less than 1 days ago.
NOPRESUBMIT=true
NOTREECHECKS=true
NOTRY=true
BUG=236848
==========

[commit-bot: I haz the power, 2016-06-24 21:51:27]

Committed patchset #1 (id:1)

[commit-bot: I haz the power, 2016-06-24 21:54:39]

Description was changed from

==========
Revert of Enable subframe FrameNavigationEntries by default. (patchset #4
id:60001 of https://codereview.chromium.org/1952533003/ )

Reason for revert:
Caused several layout tests to fail:
https://build.chromium.org/p/chromium.webkit/buildstatus?builder=WebKit%20Mac...

  fast/history/same-document-iframes-changing-fragment.html [ Failure ]
  fast/history/same-document-iframes-changing-pushstate.html [ Failure ]
  fast/loader/form-state-restore-with-frames.html [ Failure ]
  http/tests/misc/resource-timing-iframe-restored-from-history.html [ Failure ]
  http/tests/navigation/back-to-dynamic-iframe.html [ Failure ]
  http/tests/navigation/back-to-redirect-with-frame.php [ Failure ]
  http/tests/security/mixedContent/insecure-iframe-in-main-frame.html [ Failure
]

Original issue's description:
> Enable subframe FrameNavigationEntries by default.
> 
> This is a major change to the navigation logic in Chrome, making
> the browser process responsible for selecting subframes to
> navigate.  Each NavigationEntry now has a tree of
> FrameNavigationEntries representing each frame in the page, and
> these frame entries track per-frame PageState.
> 
> HistoryController in content/renderer is no longer used, since
> equivalent code in NavigationController in content/browser now
> determines which frames to navigate.
> 
> This CL is designed to be easy to revert if regressions are
> found, though the new path has been in use on 50% of Canary and
> Dev channels for a while.
> 
> BUG=236848
> TEST=Existing tests pass.
> 
> Committed: https://crrev.com/810a396cc50315037a51e55342da6c04d1c9b260
> Cr-Commit-Position: refs/heads/master@{#401969}

TBR=boliu@chromium.org,nick@chromium.org
# Skipping CQ checks because original CL landed less than 1 days ago.
NOPRESUBMIT=true
NOTREECHECKS=true
NOTRY=true
BUG=236848
==========

to

==========
Revert of Enable subframe FrameNavigationEntries by default. (patchset #4
id:60001 of https://codereview.chromium.org/1952533003/ )

Reason for revert:
Caused several layout tests to fail:
https://build.chromium.org/p/chromium.webkit/buildstatus?builder=WebKit%20Mac...

  fast/history/same-document-iframes-changing-fragment.html [ Failure ]
  fast/history/same-document-iframes-changing-pushstate.html [ Failure ]
  fast/loader/form-state-restore-with-frames.html [ Failure ]
  http/tests/misc/resource-timing-iframe-restored-from-history.html [ Failure ]
  http/tests/navigation/back-to-dynamic-iframe.html [ Failure ]
  http/tests/navigation/back-to-redirect-with-frame.php [ Failure ]
  http/tests/security/mixedContent/insecure-iframe-in-main-frame.html [ Failure
]

Original issue's description:
> Enable subframe FrameNavigationEntries by default.
>
> This is a major change to the navigation logic in Chrome, making
> the browser process responsible for selecting subframes to
> navigate.  Each NavigationEntry now has a tree of
> FrameNavigationEntries representing each frame in the page, and
> these frame entries track per-frame PageState.
>
> HistoryController in content/renderer is no longer used, since
> equivalent code in NavigationController in content/browser now
> determines which frames to navigate.
>
> This CL is designed to be easy to revert if regressions are
> found, though the new path has been in use on 50% of Canary and
> Dev channels for a while.
>
> BUG=236848
> TEST=Existing tests pass.
>
> Committed: https://crrev.com/810a396cc50315037a51e55342da6c04d1c9b260
> Cr-Commit-Position: refs/heads/master@{#401969}

TBR=boliu@chromium.org,nick@chromium.org
# Skipping CQ checks because original CL landed less than 1 days ago.
NOPRESUBMIT=true
NOTREECHECKS=true
NOTRY=true
BUG=236848

Committed: https://crrev.com/5e66abf8057e5e904c9539ee8aa2fe92161d208f
Cr-Commit-Position: refs/heads/master@{#401985}
==========

[commit-bot: I haz the power, 2016-06-24 21:54:40]

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