Standardize size of WebUI controls for touch and non-touch.

chrome/browser/resources/shared/css/chrome_shared.css

Index: chrome/browser/resources/shared/css/chrome_shared.css
diff --git a/chrome/browser/resources/shared/css/chrome_shared.css b/chrome/browser/resources/shared/css/chrome_shared.css
index d135a31c54b4d37819d865cffd70d75cd57ec03e..d2895f8ad81c6e2ed6c97352150cd28012705c7c 100644
--- a/chrome/browser/resources/shared/css/chrome_shared.css
+++ b/chrome/browser/resources/shared/css/chrome_shared.css
@@ -105,52 +105,7 @@ html[dir='rtl'] .weakrtl input::-webkit-input-placeholder {
   direction: rtl;
 }
 
-/* Rules to make it easier to hit targets when using a coarse pointer like
- * a touch screen.
- */
-@media (pointer:coarse) {
-  list input[type='input'],
-  list input[type='password'],
-  list input[type='search'],
-  list input[type='text'],
-  list input[type='url'] {
-    margin: 0;
-    padding: 3px 3px 2px 3px;
-  }
-
-  /* Margins are not touchable.  Use padding on the inner label instead to
-    increase the size of the touch target. */
-  .checkbox,
-  .radio {
-    margin: 0;
-  }
-
-  .checkbox label,
-  .radio label {
-    padding-bottom: 7px;
-    padding-top: 7px;
-  }
-
-  li > button.link-button {
-    padding-bottom: 8px;
-    padding-top: 8px;
-  }
-
-  :-webkit-any(button,
-               input[type='button'],
-               input[type='submit'],
-               select):not(.custom-appearance):not(.link-button) {
-    margin-bottom: 6px;
-    margin-top: 6px;
-  }
-
-  list :-webkit-any(
-      button,
-      input[type='button'],
-      input[type='submit'],
-      select):not(.custom-appearance):not(.link-button) {
-    margin: 0;
-    padding-bottom: 0;
-    padding-top: 3px;
-  }
+li > button.link-button {

[Evan Stade, 2012/08/10 02:44:16]

where is this pattern found? it seems dangerous to make a rule this generic when
it's quite easy to imagine new or existing code using this hierarchy but not
wanting the padding effects.

[kevers, 2012/08/10 13:56:03]

To the best of my knowledge, this pattern appears in only one place in the UI,
namely, the chromeOS version of the "Add Language" dialog.  Without the padding,
the dialog is unusable with touch.  

This rule has been in effect for some time when the touch enabled flag is on. 
Could move the rule specifically to the language dialog, which would mean that
any new code written using this pattern would likely fail to be touch friendly.

+  padding-bottom: 8px;
+  padding-top: 8px;
 }