On menu edit pages in Garland (such as /admin/build/menu-customize/navigation) disabled menu items receive a 0.5 opacity via a style rule applied to tr.menu-disabled. This creates the effect of the menu item being "grayed out" and that is bad for usability. Graying out a control is a nearly universal sign of that control being inactive - ie. unable to be acted upon. That, however, is not the case here, and sends the wrong message since one must click on a grayed out "edit" link or grayed out "enabled" checkbox to enable that menu item.

I've attached a patch that removes the 0.5 opacity rule from Garland, as that rule simply compromises usability.

I checked the other core themes and none of them engage in the use of opacity in this way.

CommentFileSizeAuthor
no_disabled_opacity.patch500 bytesmlsamuelson
Support from Acquia helps fund testing for Drupal Acquia logo

Comments

Stefan Nagtegaal’s picture

Stefan Nagtegaal CreditAttribution: Stefan Nagtegaal commented
Title: Usability - disabled menu items should not be opaque in Garland theme » Garland usability: Disabled menu items should not be opaque
Status: Needs review » Reviewed & tested by the community

I agree with you..
This is RTBC

Dries’s picture

Dries CreditAttribution: Dries commented
Status: Reviewed & tested by the community » Fixed

Committed to CVS HEAD. Thanks.

Anonymous’s picture

Anonymous (not verified) CreditAttribution: Anonymous commented
Status: Fixed » Closed (fixed)

Automatically closed -- issue fixed for two weeks with no activity.