Remove param |context_type| from InitOriginPermissions

chrome/renderer/extensions/chrome_extensions_dispatcher_delegate.cc

Index: chrome/renderer/extensions/chrome_extensions_dispatcher_delegate.cc
diff --git a/chrome/renderer/extensions/chrome_extensions_dispatcher_delegate.cc b/chrome/renderer/extensions/chrome_extensions_dispatcher_delegate.cc
index ef6a60f11f5e8f75e96e9fafaba212fc0c3be5c9..dc7f511748f31d3f01605240695093a2833e145d 100644
--- a/chrome/renderer/extensions/chrome_extensions_dispatcher_delegate.cc
+++ b/chrome/renderer/extensions/chrome_extensions_dispatcher_delegate.cc
@@ -69,13 +69,11 @@ ChromeExtensionsDispatcherDelegate::CreateScriptContext(
 }
 
 void ChromeExtensionsDispatcherDelegate::InitOriginPermissions(
-    const extensions::Extension* extension,
-    extensions::Feature::Context context_type) {
+    const extensions::Extension* extension) {
   // TODO(jstritar): We should try to remove this special case. Also, these
   // whitelist entries need to be updated when the kManagement permission
   // changes.
-  if (context_type == extensions::Feature::BLESSED_EXTENSION_CONTEXT &&
-      extension->HasAPIPermission(extensions::APIPermission::kManagement)) {
+  if (extension->HasAPIPermission(extensions::APIPermission::kManagement)) {

[not at google - send to devlin, 2014/06/06 18:55:19]

I'm not confident that removing the context check here is a no-op.
InitOriginPermissions is called from content scripts too, and we don't want
content scripts getting access to chrome:// URLs just because they have the
management permission (which is a hack in the first place anyway).

a couple of ways to fix this:
- pass the Dispatcher into this method and check
dispatcher->IsExtensionActive(extension->id())
- just pass in a bool whether the extension is active

whichever is easier for you.

     blink::WebSecurityPolicy::addOriginAccessWhitelistEntry(
         extension->url(),
         blink::WebString::fromUTF8(content::kChromeUIScheme),