Only allows extensions to create HTML notifications.

chrome/test/data/extensions/api_test/notifications/has_permission_manifest/background.js

Index: chrome/test/data/extensions/api_test/notifications/has_permission_manifest/background.js
diff --git a/chrome/test/data/extensions/api_test/notifications/has_permission_manifest/background.js b/chrome/test/data/extensions/api_test/notifications/has_permission_manifest/background.js
index 9bc585a6031837da4ea33752774689cbf6f3134a..79fb80a6e6cf1da47f520094ed9c9a4d8601f5b4 100644
--- a/chrome/test/data/extensions/api_test/notifications/has_permission_manifest/background.js
+++ b/chrome/test/data/extensions/api_test/notifications/has_permission_manifest/background.js
@@ -26,11 +26,9 @@ function onNotificationDone() {
     if (changeInfo.status != 'complete')
       return;
     // web_page1 loaded, open extension page to inject script
-    if (tab.url == chromeExtensionsUrl) {

[Mihai Parparita -not on Chrome, 2012/07/26 23:59:05]

Why remove this comparison? Is it just a matter of using
chrome://chrome/extensions/ (the new URL for the settings page)?

[jianli, 2012/07/27 00:34:10]

Yes, it is about the new settings URL. I think we do not care about the current
URL and rather leave it out in case that the settings URL gets changed again and
this test still works.

-      console.log(chromeExtensionsUrl + ' finished loading.');
-      chrome.tabs.onUpdated.removeListener(listener);
-      chrome.test.succeed();
-    }
+    console.log(chromeExtensionsUrl + ' finished loading.');
+    chrome.tabs.onUpdated.removeListener(listener);
+    chrome.test.succeed();
   };
 
   chrome.tabs.onUpdated.addListener(listener);