Implements frame sniffer to watch iframe loading state.

content/common/view_messages.h

Index: content/common/view_messages.h
diff --git a/content/common/view_messages.h b/content/common/view_messages.h
index 2798a26d32fe6062c3478d42b034ebd0ecb0808b..85af1b828635a088d725776b169387380d14e857 100644
--- a/content/common/view_messages.h
+++ b/content/common/view_messages.h
@@ -2095,3 +2095,11 @@ IPC_MESSAGE_ROUTED0(ViewHostMsg_RequestRemoteAccessClientFirewallTraversal)
 // Notifies the browser of an event occurring in the media pipeline.
 IPC_MESSAGE_CONTROL1(ViewHostMsg_MediaLogEvent,
                      media::MediaLogEvent /* event */)
+
+// This message indicates the error appeared in the frame.
+IPC_MESSAGE_ROUTED1(ViewHostMsg_FrameLoadingError,
+                    int /* error */)
+
+// This message asks frame sniffer start.
+IPC_MESSAGE_ROUTED1(ViewMsg_StartFrameSniffer,

[jam, 2011/08/31 16:36:41]

the messages are separated by ViewMsg first, then ViewHostMsg

[altimofeev, 2011/09/02 15:26:36]

Done.

[jam, 2011/09/02 16:52:59]

sorry maybe I should have been more verbose :) What I mean is you'll notice that
all the ViewMsg messages come first, then all the ViewHostMsg. so if you add two
messages that are different, they won't be beside each other. i.e.
ViewMsg_StartFrameSniffer would go in line 1250.

but, since this is a message that's sent and received in chrome, it doesn't
belong in content. so it should be moved to chrome\common\render_messages.h and
be called ChromeViewHostMsg and ChromeViewMsg like the other messages there
(that's what I meant when I said that content shouldn't be changed at all)

+                    string16 /* frame-name */)