Elim cr_button from md-settings

chrome/browser/resources/settings/search_page/search_page.css

Index: chrome/browser/resources/settings/search_page/search_page.css
diff --git a/chrome/browser/resources/settings/search_page/search_page.css b/chrome/browser/resources/settings/search_page/search_page.css
index b27aeaa748d314e104fa09381d88374b6133e4d1..95ba730867baa105f4c0ec680c1e51ba61d193ce 100644
--- a/chrome/browser/resources/settings/search_page/search_page.css
+++ b/chrome/browser/resources/settings/search_page/search_page.css
@@ -6,11 +6,11 @@
   -webkit-margin-start: 10px;
 }
 
-cr-button.search-engines-advanced {
+paper-button.search-engines-advanced {
   margin-top: 10px;
 }
 
-cr-button.search-engines {
+paper-button.search-engines {
   align-items: center;
   display: flex;

[michaelpg, 2015/09/22 22:03:46]

these used to apply to a <cr-button> (a container that had a <papre-button>) but
now will apply to the <paper-button> itself, so my guess is this looks weird

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

The button has no content, so this really just applies to the button forcing a
new layout block, i.e. it doesn't mater whether or not there is an extra
wrapper. (The display: flex is the property that matters, without it it looks
weird). I'll leave any re-styling to whomever owns this now.

[michaelpg, 2015/09/23 00:24:40]

I see.... "display: flex" make the paper-button not take up the full width,
which I guess is valid if not ideal.

   margin-top: 20px;