Elim cr_button from md-settings

ui/webui/resources/cr_elements/v1_0/cr_button/cr_button.css

-/* Copyright 2015 The Chromium Authors. All rights reserved.
- * Use of this source code is governed by a BSD-style license that can be
- * found in the LICENSE file. */
-
-:host {
-  display: inline-block;
-  vertical-align: middle;
-}
-
-:host([disabled]) {
-  pointer-events: none;
-}
-
-paper-button[toggles][active] {
-  background-color: lightgrey;
-}
-
-paper-button {
-  margin: 0;
-  --paper-button: {
-    min-width: auto;

[Dan Beam, 2015/09/22 17:22:47]

where are we doing this?

[stevenjb, 2015/09/22 17:36:29]

I thought you added this for md-downloads then didn't use it? I haven't seen any
places where this is important for settings yet, I'd prefer to add it
if/when/where we need it.

[Dan Beam, 2015/09/22 22:22:23]

downloads still does this, but so should settings, IMO:
https://code.google.com/p/chromium/codesearch#chromium/src/chrome/browser/res...

[stevenjb, 2015/09/22 23:00:18]

I was reluctant to propagate --paper-button, but copying the styling from
Downloads to settings_page.css seems fine; done.

[Dan Beam, 2015/09/22 23:09:55]

this is fine for now, I suppose, but we should start a polymer_shared.css or
polymer_wigets.css that handles stuff like this for all pages

[stevenjb, 2015/09/23 17:22:48]

I agree that would be better, but it would also mean adding an additional .css
include to every settings page. Probably worth discussing, documenting, and
implementing before we start on too many additional WebUI pages. (Either at a
standup, or next week's meeting seems fine).

-  };
-}
-
-:host([lowercase]) paper-button {
-  --paper-button: {
-    min-width: auto;  /* HACK(dbeam): mixins can't be redefined. */
-    text-transform: none;
-  };
-}