Plugins page in BWSI session has unnecessary and misleading UI components

chrome/browser/resources/shared/css/widgets.css

Index: chrome/browser/resources/shared/css/widgets.css
diff --git a/chrome/browser/resources/shared/css/widgets.css b/chrome/browser/resources/shared/css/widgets.css
index 755d539d62f1f82022e839a341e94b251bb42c2b..1ebf2cdcbc584a6eacd3ce3e1aa07e0a8758ffe9 100644
--- a/chrome/browser/resources/shared/css/widgets.css
+++ b/chrome/browser/resources/shared/css/widgets.css
@@ -217,6 +217,15 @@ input:not([type]):disabled {
   color: #999;
 }
 
+<if expr="pp_ifdef('chromeos')">

[Nikita (slow), 2012/04/06 12:36:09]

chrome_shared2.css seems to be a better place for these rules.

As this file: "This file defines styles for form controls."
chrome_shared2.css: "This file holds CSS that should be shared, in theory, by
all user-visible chrome:// pages. This contrasts chrome_shared.css, which it is
meant to replace, but has CSS specific to options and options-like pages."

[Denis Kuznetsov (DE-MUC), 2012/04/09 11:21:30]

On the other hand, widgets.css is the common part included by both
chrome_shared.css and chrome_shared2.css

[Nikita (slow), 2012/04/09 12:18:49]

Good point. So it's either code duplication (placing it in chrome_shared.css and
chrome_shared2.css) or placing it in widgets.css.

Placing in widgets.css is fine for me but please add comment  on what these 2
styles are about.

[Denis Kuznetsov (DE-MUC), 2012/04/09 13:17:03]

Done.

+.guest-disabled {
+  color: #999;
+}
+
+a.guest-disabled {
+  opacity: 0.75;
+}
+</if>
 /* Focus **********************************************************************/
 
 button:not(.custom-appearance):not(.link-button):enabled:focus,