diff options
| author | ananta@chromium.org <ananta@chromium.org@0039d316-1c4b-4281-b951-d872f2087c98> | 2011-09-23 00:11:00 +0000 |
|---|---|---|
| committer | ananta@chromium.org <ananta@chromium.org@0039d316-1c4b-4281-b951-d872f2087c98> | 2011-09-23 00:11:00 +0000 |
| commit | 4e6239c7292df55796511a57407a542741077daf (patch) | |
| tree | af4eb38e36e66ca2ed47961bcf18a22f9cb3c404 /content/browser/tab_contents | |
| parent | 02065c61d8f4b019bc0addb5b53db8426e0e5ce5 (diff) | |
| download | chromium_src-4e6239c7292df55796511a57407a542741077daf.zip chromium_src-4e6239c7292df55796511a57407a542741077daf.tar.gz chromium_src-4e6239c7292df55796511a57407a542741077daf.tar.bz2 | |
Removed sending of the following IPC messages from chrome and added API's on the RenderViewHost
object to facilitate this.
1. ViewMsg_CustomContextMenuAction
2. ViewMsg_ContextMenuClosed
3. ViewMsg_CopyImageAt
4. ViewMsg_MediaPlayerActionAt
5. ViewMsg_DisassociateFromPopupCount
6. ViewMsg_MoveOrResizeStarted
7. ViewMsg_StopFinding
The ViewMsg_FindReplyACK message is now sent by the TabContents::OnFindReply handler.
Continuing changes to get rid of the pattern of IPC messages being sent and processed across content
and chrome.
BUG=87335.
TEST=no change in functionality.
Review URL: http://codereview.chromium.org/8002005
git-svn-id: svn://svn.chromium.org/chrome/trunk/src@102404 0039d316-1c4b-4281-b951-d872f2087c98
Diffstat (limited to 'content/browser/tab_contents')
| -rw-r--r-- | content/browser/tab_contents/tab_contents.cc | 8 |
1 files changed, 8 insertions, 0 deletions
diff --git a/content/browser/tab_contents/tab_contents.cc b/content/browser/tab_contents/tab_contents.cc index 287e661..73bbe5b 100644 --- a/content/browser/tab_contents/tab_contents.cc +++ b/content/browser/tab_contents/tab_contents.cc @@ -1150,6 +1150,14 @@ void TabContents::OnFindReply(int request_id, bool final_update) { delegate()->FindReply(this, request_id, number_of_matches, selection_rect, active_match_ordinal, final_update); + // Send a notification to the renderer that we are ready to receive more + // results from the scoping effort of the Find operation. The FindInPage + // scoping is asynchronous and periodically sends results back up to the + // browser using IPC. In an effort to not spam the browser we have the + // browser send an ACK for each FindReply message and have the renderer + // queue up the latest status message while waiting for this ACK. + render_view_host()->Send( + new ViewMsg_FindReplyACK(render_view_host()->routing_id())); } void TabContents::OnCrashedPlugin(const FilePath& plugin_path) { |