Refactor cc scrollbar layers to separate solid-color vs desktop.

content/child/runtime_features.cc

Index: content/child/runtime_features.cc
diff --git a/content/child/runtime_features.cc b/content/child/runtime_features.cc
index 25804aeee0abc649017dd14d08224ce95536bc63..5575d5177e2b065bf25efd6fe096cd123a093bea 100644
--- a/content/child/runtime_features.cc
+++ b/content/child/runtime_features.cc
@@ -5,6 +5,7 @@
 #include "content/child/runtime_features.h"
 
 #include "base/command_line.h"
+#include "cc/base/switches.h"
 #include "content/public/common/content_switches.h"
 #include "third_party/WebKit/public/web/WebRuntimeFeatures.h"
 
@@ -136,7 +137,7 @@ void SetRuntimeFeaturesDefaultsAndUpdateFromArgs(
   if (command_line.HasSwitch(switches::kEnableHTMLImports))
     WebRuntimeFeatures::enableHTMLImports(true);
 
-  if (command_line.HasSwitch(switches::kEnableOverlayScrollbars))
+  if (command_line.HasSwitch(cc::switches::kEnableOverlayScrollbars))

[jamesr, 2013/08/15 22:34:24]

this is a bad change.  cc::switches should only change cc's behavior, not the
behavior of Blink

[wjmaclean, 2013/08/16 13:34:16]

OK. Is it preferable to add another, CC-specific flag? Or, should I add a static
function in some neutral location (i.e. that WebScrollbarLayerImpl can see
without a layering violation) that can see this flag when it is moved back to
content switches.

*** I will hold off changing this until you let me know your preference.

     WebRuntimeFeatures::enableOverlayScrollbars(true);
 }