css hack n' slash, continued: New styles for buttons and selects.

chrome/browser/resources/chromeos/login/login.html

Index: chrome/browser/resources/chromeos/login/login.html
diff --git a/chrome/browser/resources/chromeos/login/login.html b/chrome/browser/resources/chromeos/login/login.html
index 7ca89a896d70ed35bd09addee91162017f00a563..a228f0c8e6f2ab89ceca58f8e2a865559ab5cead 100644
--- a/chrome/browser/resources/chromeos/login/login.html
+++ b/chrome/browser/resources/chromeos/login/login.html
@@ -5,7 +5,6 @@
 <link rel="stylesheet" href="chrome://resources/css/button.css">
 <link rel="stylesheet" href="chrome://resources/css/dialogs.css"></link>
 <link rel="stylesheet" href="chrome://resources/css/list.css">
-<link rel="stylesheet" href="chrome://resources/css/select.css">

[Dan Beam, 2012/03/02 17:58:43]

I'd move button.css to the old position of select.css here and throughout, IMO,
as otherwise you might have cascade issues.

[Evan Stade, 2012/03/02 19:46:20]

depending on order is inherently a bug imo (except maybe if it's two rules in
the same file --- even that is iffy though). I'd rather keep them alphabetical,
and if this uncovers a dormant ordering bug, we'll find it and squash it (also,
while it exists, it's not likely to be very high impact).

 <link rel="stylesheet" href="chrome://resources/css/spinner.css">
 <link rel="stylesheet" href="bubble.css">
 <link rel="stylesheet" href="header_bar.css">