OOPIF: Allow navigations on a RFH without a site to stay in same process

OOPIF: Allow navigations on a RFH without a site to stay in same process.

This was causing failures in NavigateToURL for a few content_browsertests when running under --site-per-process.

BUG=417518
Committed: https://crrev.com/d74555751144d391e0e2d05483760cb2836d8560
Cr-Commit-Position: refs/heads/master@{#297863}

[alexmos, 2014-10-02 16:50:11]

alexmos@chromium.org changed reviewers:
+ creis@chromium.org

[alexmos, 2014-10-02 16:55:55]

Hi Charlie, can you please take a look at this fix?

[Charlie Reis, 2014-10-02 17:19:31]

LGTM.  (This is in keeping with Nasko's TODO to make it behave more like
UpdateStateForNavigate, and it only affects --site-per-process.)

Can you update the CL description to show this is specific to
--site-per-process?  Maybe just prefix it with "OOPIF: "?

[alexmos, 2014-10-02 17:27:05]

On 2014/10/02 17:19:31, Charlie Reis wrote:
> LGTM.  (This is in keeping with Nasko's TODO to make it behave more like
> UpdateStateForNavigate, and it only affects --site-per-process.)
> 
> Can you update the CL description to show this is specific to
> --site-per-process?  Maybe just prefix it with "OOPIF: "?

Done.

[alexmos, 2014-10-02 17:27:13]

The CQ bit was checked by alexmos@chromium.org

[commit-bot: I haz the power, 2014-10-02 17:27:42]

CQ is trying da patch. Follow status at
 https://chromium-cq-status.appspot.com/patch-status/625483002/20001

[commit-bot: I haz the power, 2014-10-02 18:06:10]

Committed patchset #2 (id:20001) as 8fd66cc29205164a508703b52f99f2dfc92e8f80

[commit-bot: I haz the power, 2014-10-02 18:07:11]

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