Introduce RenderFrameObserver.

Introduce RenderFrameObserver.

Right now this is empty other than IPC related methods. We can start using this to replace RenderViewObservers. Eventually we will remove RenderViewObserver.

BUG=245126
R=nasko@chromium.org

Committed: https://src.chromium.org/viewvc/chrome?view=rev&revision=238258

[nasko, 2013-12-03 00:07:33]

LGTM with a nit.

https://codereview.chromium.org/100363002/diff/1/content/renderer/render_fram...
File content/renderer/render_frame_impl.h (right):

https://codereview.chromium.org/100363002/diff/1/content/renderer/render_fram...
content/renderer/render_frame_impl.h:62: int routing_id() const { return
routing_id_; }
nit: Why not keep the GetRoutingID() naming, which is present in RenderView? I
expect this will have to be in the public RenderFrame interface at some point.

[jam, 2013-12-03 00:14:31]

https://codereview.chromium.org/100363002/diff/1/content/renderer/render_fram...
File content/renderer/render_frame_impl.h (right):

https://codereview.chromium.org/100363002/diff/1/content/renderer/render_fram...
content/renderer/render_frame_impl.h:62: int routing_id() const { return
routing_id_; }
On 2013/12/03 00:07:33, nasko wrote:
> nit: Why not keep the GetRoutingID() naming, which is present in RenderView?

just because in general we have unix_hacker accessors for simple getters

> I expect this will have to be in the public RenderFrame interface at some
point.

sure, in that point we can then move it? I tend to prefer to not adding methods
until we know they're needed. Who knows, maybe this won't be needed on RF and in
which case the unix_hacker getter is enough.