Switch BackgroundContents to use TabContents instead of RenderViewHost.

content/browser/intents/intent_injector.cc

 // Copyright (c) 2011 The Chromium Authors. All rights reserved.
 // Use of this source code is governed by a BSD-style license that can be
 // found in the LICENSE file.
 
 #include "content/browser/intents/intent_injector.h"
 
 #include "base/command_line.h"
 #include "base/logging.h"
 #include "base/string16.h"
 #include "content/browser/renderer_host/render_view_host.h"
@@ skipping 33 matching lines @@
   source_intent_.reset(new webkit_glue::WebIntentData(intent));
   intent_id_ = intent_id;
 
   SendIntent();
 }
 
 void IntentInjector::RenderViewCreated(RenderViewHost* host) {
   SendIntent();
 }
 
-void IntentInjector::DidNavigateMainFramePostCommit(
+void IntentInjector::DidNavigateMainFrame(
     const content::LoadCommittedDetails& details,
     const ViewHostMsg_FrameNavigate_Params& params) {
   SendIntent();
 }
 
 // TODO(gbillock): The "correct" thing here is for this to be a
 // RenderViewHostObserver, and do this on RenderViewHostInitialized. There's no
 // good hooks for attaching the intent to such an object, though. All RVHOs get
 // made deep inside tab contents initialization. Idea: propagate out
 // RenderViewHostInitialized to a TabContentsObserver latch? That still looks
@@ skipping 29 matching lines @@
                              int intent_id) {
   if (!CommandLine::ForCurrentProcess()->HasSwitch(switches::kEnableWebIntents))
     NOTREACHED();
 
   if (source_tab_.get() != NULL) {
     source_tab_->Send(new IntentsMsg_WebIntentReply(
         0, reply_type, data, intent_id));
     source_tab_.reset(NULL);
   }
 }