Add a section for the fullscreen JS API in the content settings page.

chrome/browser/content_settings/host_content_settings_map.cc

Index: chrome/browser/content_settings/host_content_settings_map.cc
diff --git a/chrome/browser/content_settings/host_content_settings_map.cc b/chrome/browser/content_settings/host_content_settings_map.cc
index b0baa0425bf6024d7d1ca7959f192a8d9a8dfac3..5f63ee94f699e695eec52cd88c58fc5998f84412 100644
--- a/chrome/browser/content_settings/host_content_settings_map.cc
+++ b/chrome/browser/content_settings/host_content_settings_map.cc
@@ -310,6 +310,12 @@ bool HostContentSettingsMap::IsSettingAllowedForType(
           switches::kEnableWebIntents))
     return false;
 
+  // BLOCK semantics are not implemented for fullscreen.

[jochen (gone - plz use gerrit), 2011/11/18 00:14:28]

can you file a bug and add a TODO entry with a reference to that bug here?

[koz (OOO until 15th September), 2011/11/18 00:24:50]

Done.

+  if (content_type == CONTENT_SETTINGS_TYPE_FULLSCREEN &&
+      setting == CONTENT_SETTING_BLOCK) {
+    return false;
+  }
+
   // DEFAULT, ALLOW and BLOCK are always allowed.
   if (setting == CONTENT_SETTING_DEFAULT ||
       setting == CONTENT_SETTING_ALLOW ||
@@ -318,15 +324,15 @@ bool HostContentSettingsMap::IsSettingAllowedForType(
   }
   switch (content_type) {
     case CONTENT_SETTINGS_TYPE_COOKIES:
-      return (setting == CONTENT_SETTING_SESSION_ONLY);
+      return setting == CONTENT_SETTING_SESSION_ONLY;
     case CONTENT_SETTINGS_TYPE_PLUGINS:
-      return (setting == CONTENT_SETTING_ASK &&
-              CommandLine::ForCurrentProcess()->HasSwitch(
-                  switches::kEnableClickToPlay));
+      return setting == CONTENT_SETTING_ASK &&
+             CommandLine::ForCurrentProcess()->HasSwitch(
+                 switches::kEnableClickToPlay);
     case CONTENT_SETTINGS_TYPE_GEOLOCATION:
     case CONTENT_SETTINGS_TYPE_NOTIFICATIONS:
     case CONTENT_SETTINGS_TYPE_INTENTS:
-      return (setting == CONTENT_SETTING_ASK);
+      return setting == CONTENT_SETTING_ASK;
     default:
       return false;
   }