Take 2 at implementing activeTab.

chrome/renderer/extensions/user_script_scheduler.cc

Index: chrome/renderer/extensions/user_script_scheduler.cc
diff --git a/chrome/renderer/extensions/user_script_scheduler.cc b/chrome/renderer/extensions/user_script_scheduler.cc
index dad8cb9936dc191a96a27937b161f8143609d0fb..dc4ebee15bf2b939a9892debcf591338745c86f6 100644
--- a/chrome/renderer/extensions/user_script_scheduler.cc
+++ b/chrome/renderer/extensions/user_script_scheduler.cc
@@ -133,6 +133,7 @@ void UserScriptScheduler::ExecuteCodeImpl(
       params.extension_id);
   content::RenderView* render_view =
       content::RenderView::FromWebView(frame_->view());
+  ExtensionHelper* extension_helper = ExtensionHelper::Get(render_view);
 
   // Since extension info is sent separately from user script info, they can
   // be out of sync. We just ignore this situation.
@@ -162,7 +163,9 @@ void UserScriptScheduler::ExecuteCodeImpl(
       // For child frames, we just skip ones the extension doesn't have access
       // to and carry on.
       if (!extension->CanExecuteScriptOnPage(frame->document().url(),
-                                             NULL, NULL)) {
+                                             extension_helper->tab_id(),
+                                             NULL,
+                                             NULL)) {
         if (frame->parent()) {
           continue;
         } else {