chrome/app/generated_resources.grd

Index: chrome/app/generated_resources.grd
diff --git a/chrome/app/generated_resources.grd b/chrome/app/generated_resources.grd
index 9e036078a6542a4ac992a05e5edae41d3a7bcafd..e6880aa495c2165361286914aeeaad9a92926e43 100644
--- a/chrome/app/generated_resources.grd
+++ b/chrome/app/generated_resources.grd
@@ -6449,6 +6449,21 @@ Keep your key file in a safe place. You will need it to create new versions of y
       <message name="IDS_FLAGS_TAB_CAPTURE_SCALE_QUALITY_BEST" desc="">
         best
       </message>
+      <message name="IDS_FLAGS_TAB_CLOSE_BUTTONS_HIDDEN_WITH_TOUCH_NAME" desc="">

[sky, 2015/02/07 00:09:39]

Do we really need all these permutations? What are you going to use to make a
decision? Could this just be something you build locally and show ux rather than
landing?

[tdanderson, 2015/02/10 18:52:17]

As discussed, there isn't an easy way for me to do this since I'm
in a different office. I checked with the PM and he said the most
convenient way for UX to see it would be for me to land behind
a flag.

+        Hide close buttons of inactive tabs with touch.
+      </message>
+      <message name="IDS_FLAGS_TAB_CLOSE_BUTTONS_HIDDEN_WITH_TOUCH_DESCRIPTION" desc="">
+        Options to hide the close buttons of inactive tabs when touch is used for the tabstrip.
+      </message>
+      <message name="IDS_FLAGS_TAB_CLOSE_BUTTONS_HIDDEN_WITH_TOUCH_ALWAYS" desc="">
+        Always hide
+      </message>
+      <message name="IDS_FLAGS_TAB_CLOSE_BUTTONS_HIDDEN_WITH_TOUCH_NARROW" desc="">
+        Hide when tab is narrower than its standard width
+      </message>
+      <message name="IDS_FLAGS_TAB_CLOSE_BUTTONS_HIDDEN_WITH_TOUCH_STACKED" desc="">
+        Hide when tabs start stacking
+      </message>
       <message name="IDS_FLAGS_DEFAULT_TILE_WIDTH_NAME" desc="Name of about:flags option for default tile width.">
         Default tile width
       </message>