[Extensions] Adjust script injection reporting to the browser side

chrome/browser/extensions/extension_util.h

Index: chrome/browser/extensions/extension_util.h
diff --git a/chrome/browser/extensions/extension_util.h b/chrome/browser/extensions/extension_util.h
index 3ac12e5837e2dc9c6c0bfc995d14541b05b8c1f8..49fa599c9055935b265579e883c055b0d637d423 100644
--- a/chrome/browser/extensions/extension_util.h
+++ b/chrome/browser/extensions/extension_util.h
@@ -86,14 +86,6 @@ void SetAllowedScriptingOnAllUrls(const std::string& extension_id,
 bool HasSetAllowedScriptingOnAllUrls(const std::string& extension_id,
                                      content::BrowserContext* context);
 
-// Returns true if the --scripts-require-action flag would possibly affect
-// the given |extension| and |permissions|. We pass in the |permissions|
-// explicitly, as we may need to check with permissions other than the ones
-// that are currently on the extension's PermissionsData.
-bool ScriptsMayRequireActionForExtension(
-    const Extension* extension,
-    const PermissionSet* permissions);
-
 // Returns true if |extension_id| can be launched (possibly only after being
 // enabled).
 bool IsAppLaunchable(const std::string& extension_id,