Convert SearchTabHelper to use the new navigation callbacks.

chrome/test/data/extensions/api_test/tabs/on_updated/test.js

Index: chrome/test/data/extensions/api_test/tabs/on_updated/test.js
diff --git a/chrome/test/data/extensions/api_test/tabs/on_updated/test.js b/chrome/test/data/extensions/api_test/tabs/on_updated/test.js
index 41f2aa28c3100bc72ae1a4e0129b84a4b06431a7..16688a2f88835b6535412e4b9fa3f6bbaddcc6ce 100644
--- a/chrome/test/data/extensions/api_test/tabs/on_updated/test.js
+++ b/chrome/test/data/extensions/api_test/tabs/on_updated/test.js
@@ -50,9 +50,18 @@ chrome.test.runTests([
   function newTab() {
     // Test for crbug.com/27208.
     expect([
+      { title : "New Tab" },
       { status: 'loading', url: 'chrome://newtab/' },
       { status: 'complete' }
-    ]);
+    ], function(info) {
+      // TODO(jam): remove this logic and the title line above when PlzNavigate
+      // is turned on by default. Right now the test has to handle both cases
+      // which have different timing. http://crbug.com/368813
+      if (info.status === 'loading' && capturedEventData.length == 0) {
+        expectedEventData.shift();
+      }
+      return false;
+    });
 
     chrome.tabs.create({ url: 'chrome://newtab/' });
   },