Enable GPU rasterization by default on Android

content/browser/gpu/compositor_util.cc

Index: content/browser/gpu/compositor_util.cc
diff --git a/content/browser/gpu/compositor_util.cc b/content/browser/gpu/compositor_util.cc
index 96cee0a12a2fa87d632fb63ccbe0f33003e73619..171ef768420a38c9ea653343553df8cd875ddf2a 100644
--- a/content/browser/gpu/compositor_util.cc
+++ b/content/browser/gpu/compositor_util.cc
@@ -272,18 +272,12 @@ bool IsGpuRasterizationEnabled() {
   else if (command_line.HasSwitch(switches::kEnableGpuRasterization))
     return true;
 
-  if (command_line.HasSwitch(
-          switches::kEnableBleedingEdgeRenderingFastPaths)) {
-    return true;
-  }

[Zhenyao Mo, 2014/04/17 22:54:53]

I see this is removed instead of moving after blacklist.


Is this what you want?

[ajuma, 2014/04/17 22:57:17]

Since we're already returning true after the blacklist check, checking this
condition after the blacklist check doesn't change the return value (we return
true either way).

[Zhenyao Mo, 2014/04/17 23:04:19]

The only difference is for a system that's blacklisted, you can use
--enable-bleeding-edge-rendering-fast-paths to turn the feature one.  Now you
can't.  But it's your call, as you can still turn it one with
--enable-gpu-rasterization.

-
   if (GpuDataManagerImpl::GetInstance()->IsFeatureBlacklisted(
           gpu::GPU_FEATURE_TYPE_GPU_RASTERIZATION)) {
     return false;
   }
 
-  // Change this to true to turn on the feature by default.
-  return false;
+  return true;
 }
 
 bool IsForceGpuRasterizationEnabled() {