New issue
Advanced search Search tips

Issue 618561 link

Starred by 4 users

Issue metadata

Status: Fixed
Owner:
Closed: Jul 2016
Cc:
Components:
EstimatedDays: ----
NextAction: ----
OS: ----
Pri: 1
Type: Bug

Blocking:
issue 614265
issue 614588
issue 614589



Sign in to add a comment

MD Settings: specs for disabled controls

Project Member Reported by michae...@chromium.org, Jun 9 2016

Issue description

I don't see any notes about how to style disabled elements in the specs.

Polymer defaults:

paper-checkbox checkbox: opacity: .5
paper-checkbox label:    opacity: .65

paper-toggle-button button: background-color: #bdbdbd
paper-toggle-button bar:    opacity: .12
paper-toggle-button label:  opacity: 1 (?!)

We also have action buttons, which are --google-blue-500
but then have opacity: .25 applied when disabled,
with a TODO to confirm the style:
https://cs.chromium.org/chromium/src/chrome/browser/resources/settings/settings_shared_css.html?q=settings_shared_css.html&sq=package:chromium&dr&l=130

Should we consistently grey out text for disabled controls, and if so, at what opacity?
 
Labels: Hotlist-MD-Settings-General
Blocking: 614588 614589
Labels: -Pri-2 Pri-1

Comment 4 by dbeam@chromium.org, Jul 18 2016

Blocking: 614265
Cc: bettes@chromium.org
Owner: dbeam@chromium.org
@dbeam -- did we agree on using 60% opacity or something similar?

Comment 6 by dbeam@chromium.org, Jul 23 2016

Status: Fixed (was: Assigned)
basically, but with indicators of /why/ things were disabled at 100% (i.e. power plant icons)

fwiw: there are certain things (like <paper-radio-button>) that already have builtin styles for a disabled look.  they're pretty darn close to 60% opacity in many cases, but with good logic as to why some things are more opaque than others (hard to read, more important, etc.) so I'll probably leave those where they make sense.

Sign in to add a comment