Formalize a RenderFrameHost::AddMessageToConsole() API.

Formalize a RenderFrameHost::AddMessageToConsole() API.

This CL adds a new API to RenderFrameHost allowing consumers to add a
new message to the DevTools console. There's currently one feature doing
this by manually sending an IPC message, but that doesn't scale well,
and I'm in the process of adding a second user.

BUG=

Committed: https://crrev.com/4eb24200b1402c38f37ea02eff707db2710f294d
Cr-Commit-Position: refs/heads/master@{#332374}

[Peter Beverloo, 2015-05-29 13:45:55]

peter@chromium.org changed reviewers:
+ pfeldman@chromium.org

[Peter Beverloo, 2015-05-29 13:45:55]

+pfeldman

[Mike West, 2015-05-29 13:57:43]

mkwst@chromium.org changed reviewers:
+ mkwst@chromium.org

[Mike West, 2015-05-29 13:57:45]

Once pfeldman@ is happy with the implementation, moving the IPC from devtools to
frame LGTM.

[Charlie Reis, 2015-05-29 22:39:50]

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

[Charlie Reis, 2015-05-29 22:39:50]

content/public drive-by: We generally require there to be a caller outside
content/ when adding something to content/public.  Is it possible to include the
caller in this CL?  (Feel free to confirm with jam@.)

[Peter Beverloo, 2015-05-29 22:42:26]

On 2015/05/29 22:39:50, Charlie Reis wrote:
> content/public drive-by: We generally require there to be a caller outside
> content/ when adding something to content/public.  Is it possible to include
the
> caller in this CL?  (Feel free to confirm with jam@.)

The caller is being added in the following, already reviewed CL:
  https://codereview.chromium.org/1158923002/

I added this API in response to a comment there. I'm not opposed to merging the
two, but do feel that it'll add more noise than it's worth.

[Charlie Reis, 2015-05-29 22:46:06]

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

[Charlie Reis, 2015-05-29 22:46:06]

On 2015/05/29 22:42:26, Peter Beverloo wrote:
> On 2015/05/29 22:39:50, Charlie Reis wrote:
> > content/public drive-by: We generally require there to be a caller outside
> > content/ when adding something to content/public.  Is it possible to include
> the
> > caller in this CL?  (Feel free to confirm with jam@.)
> 
> The caller is being added in the following, already reviewed CL:
>   https://codereview.chromium.org/1158923002/
> 
> I added this API in response to a comment there. I'm not opposed to merging
the
> two, but do feel that it'll add more noise than it's worth.

Ah, nice.  If that one's ready to land apart from this, I'm ok with landing them
back-to-back.  @jam, do you agree?

[pfeldman, 2015-05-30 19:19:27]

lgtm

[jam, 2015-06-01 21:34:09]

lgtm

[Peter Beverloo, 2015-06-02 11:34:26]

The CQ bit was checked by peter@chromium.org

[Peter Beverloo, 2015-06-02 11:34:27]

The patchset sent to the CQ was uploaded after l-g-t-m from mkwst@chromium.org
Link to the patchset: https://codereview.chromium.org/1154673005/#ps20001
(title: "Android fix")

[commit-bot: I haz the power, 2015-06-02 11:34:48]

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

[commit-bot: I haz the power, 2015-06-02 12:45:26]

Committed patchset #2 (id:20001)

[commit-bot: I haz the power, 2015-06-02 12:46:30]

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