cc: Implement overdraw feedback debugging feature.

cc/base/switches.cc

Index: cc/base/switches.cc
diff --git a/cc/base/switches.cc b/cc/base/switches.cc
index b7de4724ccefc1a8be3b44965956528779bfcd78..6f32215c629a8bb1b62ce0697cf9abd380591b38 100644
--- a/cc/base/switches.cc
+++ b/cc/base/switches.cc
@@ -98,6 +98,18 @@ const char kUIShowScreenSpaceRects[] = "ui-show-screenspace-rects";
 const char kEnableLayerLists[] = "enable-layer-lists";
 const char kUIEnableLayerLists[] = "ui-enable-layer-lists";
 
+// Visualize overdraw by color-coding elements based on if they have other
+// elements drawn underneath. This is good for showing where the UI might be
+// doing more rendering work than necessary. The colors are hinting at the
+// amount of overdraw on your screen for each pixel, as follows:
+//
+// True color: No overdraw.
+// Blue: Overdrawn once.
+// Green: Overdrawn twice.
+// Pink: Overdrawn three times.
+// Red: Overdrawn four or more times.
+const char kOverdrawFeedback[] = "overdraw-feedback";

[Daniele Castagna, 2017/01/09 18:53:06]

Shouldn't flag names be imperative? (i.e: show-overdraw-feedback.)

[reveman, 2017/01/10 23:52:00]

Done.

+
 // Prevents the layer tree unit tests from timing out.
 const char kCCLayerTreeTestNoTimeout[] = "cc-layer-tree-test-no-timeout";