Enable subframe FrameNavigationEntries by default.

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/111baab648276f64b58d7af5b3f47fd3823dc42e
Cr-Commit-Position: refs/heads/master@{#410150}

[Charlie Reis, 2016-08-02 19:51:15]

The CQ bit was checked by creis@chromium.org to run a CQ dry run

[commit-bot: I haz the power, 2016-08-02 19:52:21]

Dry run: 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-08-02 21:07:35]

The CQ bit was unchecked by commit-bot@chromium.org

[commit-bot: I haz the power, 2016-08-02 21:07:36]

Dry run: This issue passed the CQ dry run.

[Charlie Reis, 2016-08-02 22:27:20]

creis@chromium.org changed reviewers:
+ boliu@chromium.org, nasko@chromium.org

[Charlie Reis, 2016-08-02 22:27:21]

We're getting ready to attempt this again, once the last
back-to-dynamic-iframe.html layout test is fixed.

nasko@ and boliu@, can you rubber stamp?  (Same as the last time:
https://codereview.chromium.org/1952533003.)  CC'ing japhet@ as FYI.

[boliu, 2016-08-02 22:30:52]

lgtm

[nasko, 2016-08-02 22:54:45]

Super exciting! LGTM

[Charlie Reis, 2016-08-05 17:18:36]

Patchset #2 (id:20001) has been deleted

[nasko, 2016-08-05 18:08:45]

The CQ bit was checked by nasko@chromium.org to run a CQ dry run

[commit-bot: I haz the power, 2016-08-05 18:09:23]

Dry run: 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-08-05 18:15:54]

The CQ bit was unchecked by commit-bot@chromium.org

[commit-bot: I haz the power, 2016-08-05 18:15:55]

Dry run: Try jobs failed on following builders:
  linux_chromium_asan_rel_ng on master.tryserver.chromium.linux (JOB_FAILED,
http://build.chromium.org/p/tryserver.chromium.linux/builders/linux_chromium_...)
  linux_chromium_rel_ng on master.tryserver.chromium.linux (JOB_FAILED,
http://build.chromium.org/p/tryserver.chromium.linux/builders/linux_chromium_...)

[nasko, 2016-08-05 18:44:32]

The CQ bit was checked by nasko@chromium.org to run a CQ dry run

[commit-bot: I haz the power, 2016-08-05 18:44:54]

Dry run: 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-08-05 19:43:10]

The CQ bit was unchecked by commit-bot@chromium.org

[commit-bot: I haz the power, 2016-08-05 19:43:10]

Dry run: This issue passed the CQ dry run.

[nasko, 2016-08-05 19:52:39]

The CQ bit was checked by nasko@chromium.org

[commit-bot: I haz the power, 2016-08-05 19:52:56]

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-08-05 19:56:43]

Committed patchset #1 (id:1)

[commit-bot: I haz the power, 2016-08-05 19:58:42]

Description was changed from

==========
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.
==========

to

==========
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/111baab648276f64b58d7af5b3f47fd3823dc42e
Cr-Commit-Position: refs/heads/master@{#410150}
==========

[commit-bot: I haz the power, 2016-08-05 19:58:43]

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