Don't send NewFrameProxy for top-level remote frames

Don't send NewFrameProxy for top-level remote frames.

If site A embeds a frame for site B, the process for B needs to create a remote frame to represent the top-level frame A.  Currently, this is done when RenderFrameHostManager::CreateRenderFrame sends a ViewMsg_New to process B to create a swapped-out RenderView.  However, after initializing the new view, CreateRenderFrame also sends a NewFrameProxy message, which isn't necessary because the remote frame has already been created.  Note that nothing actually happens on the renderer side due to another bug with sending NewFrameProxy (crbug.com/423538).

This CL removes the call to InitRenderFrameProxy which sends the extra NewFrameProxy.  We only need to send NewFrameProxy messages for subframes, and we should never hit this path for subframes with swapped_out being true (there's a CHECK on top of RFHM::CreateRenderFrame that ensures this).

BUG=423567
Committed: https://crrev.com/28d4362169d043400a389e70b4744b7e74b4559c
Cr-Commit-Position: refs/heads/master@{#299970}

[lutei777, 2014-10-15 23:29:10]

lutei777@gmail.com changed reviewers:
+ lutei777@gmail.com

[alexmos, 2014-10-15 23:41:28]

alexmos@chromium.org changed reviewers:
- lutei777@gmail.com

[alexmos, 2014-10-16 04:20:36]

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

[alexmos, 2014-10-16 16:48:20]

Nasko, could you please review this CL?

[nasko, 2014-10-16 18:53:01]

LGTM

[alexmos, 2014-10-16 20:20:08]

The CQ bit was checked by alexmos@chromium.org

[commit-bot: I haz the power, 2014-10-16 20:21:01]

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

[commit-bot: I haz the power, 2014-10-16 20:35:42]

Committed patchset #1 (id:1)

[commit-bot: I haz the power, 2014-10-16 20:36:54]

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