Add about:flags entry to disable WebGL.

chrome/browser/about_flags.cc

Index: chrome/browser/about_flags.cc
diff --git a/chrome/browser/about_flags.cc b/chrome/browser/about_flags.cc
index 4df2c0661edcb7bce7227b30fa6d90042a5cc8ff..37c4b260988feb1b2f36b23902506d7fb331bec0 100644
--- a/chrome/browser/about_flags.cc
+++ b/chrome/browser/about_flags.cc
@@ -20,6 +20,7 @@
 #include "chrome/common/chrome_switches.h"
 #include "chrome/common/pref_names.h"
 #include "content/browser/user_metrics.h"
+#include "content/common/content_switches.h"
 #include "grit/generated_resources.h"
 #include "ui/base/l10n/l10n_util.h"
 #include "ui/gfx/gl/gl_switches.h"
@@ -413,6 +414,13 @@ const Experiment kExperiments[] = {
     kOsMac | kOsWin | kOsLinux,
     SINGLE_VALUE_TYPE(switches::kEnableAutologin)
   },
+  {
+    "in-process-webgl",
+    IDS_FLAGS_ENABLE_WEBGL_NAME,
+    IDS_FLAGS_ENABLE_WEBGL_DESCRIPTION,
+    kOsAll,
+    SINGLE_VALUE_TYPE(switches::kInProcessWebGL)

[vangelis, 2011/09/21 21:35:27]

This is the wrong flag.  The one we need in order to disable WebGL is
kDisableExperimentalWebGL.  

What will be a bit confusing with the about:flags UI for this is that the flag
is a disable flag but you'll still need to click on the "Enable" button to
disable WebGL.  But that's the unfortunate side-effect of using about:flags for
such settings...

[tfarina, 2011/09/21 21:42:39]

Done.

+  },
 };
 
 const Experiment* experiments = kExperiments;