Added group policy for disabling all client-side 3D APIs in Chromium...

chrome/browser/policy/managed_prefs_banner_base.cc

Index: chrome/browser/policy/managed_prefs_banner_base.cc
===================================================================
--- chrome/browser/policy/managed_prefs_banner_base.cc	(revision 69586)
+++ chrome/browser/policy/managed_prefs_banner_base.cc	(working copy)
@@ -71,6 +71,7 @@
       AddUserPref(prefs::kSyncManaged);
       AddUserPref(prefs::kAutoFillEnabled);
       AddUserPref(prefs::kPasswordManagerEnabled);
+      AddUserPref(prefs::kDisable3DAPIs);

[Mattias Nissler (ping if slow), 2010/12/20 12:25:36]

Why would we need this? Our policy is to only show the banner if something on
the particular page is inaccessible due to policy being in effect. We don't have
a knob for 3D on the content page AFAICS though.

[Ken Russell (switch to Gerrit), 2010/12/20 20:34:33]

No good reason. I copied it from the example code review at
http://www.chromium.org/developers/how-tos/adding-new-policies but you're right,
there is currently no content setting for 3D content. I've removed this change.

 #if defined(OS_CHROMEOS)
       AddUserPref(prefs::kEnableScreenLock);
 #endif