PS - Adjusting webRequest API for use in Public Sessions

chrome/browser/chromeos/extensions/device_local_account_management_policy_provider.cc

Index: chrome/browser/chromeos/extensions/device_local_account_management_policy_provider.cc
diff --git a/chrome/browser/chromeos/extensions/device_local_account_management_policy_provider.cc b/chrome/browser/chromeos/extensions/device_local_account_management_policy_provider.cc
index dc4703efe28334f1e1b1985fc958703629553174..ec4db9cd464dfba754cae40fd8a4cdd8b1906930 100644
--- a/chrome/browser/chromeos/extensions/device_local_account_management_policy_provider.cc
+++ b/chrome/browser/chromeos/extensions/device_local_account_management_policy_provider.cc
@@ -664,12 +664,9 @@ const char* const kSafePermissionStrings[] = {
     // Privacy sensitive URL access.
     // "webNavigation",
 
-    // Provides access to cookies and form upload data. Options: (1) block,
-    // (2) strip all content in events.
-    // "webRequest",
-
-    // Fine once webRequest is adjusted.
-    // "webRequestBlocking",
+    // Sensitive content is stripped away.
+    "webRequest",
+    "webRequestBlocking",
 
     // This allows content scripts and capturing. However, the webview runs
     // within a separate storage partition, i.e. doesn't share cookies and other