Make WordPress Core

Opened 8 years ago

Closed 8 years ago

Last modified 8 years ago

#22871 closed enhancement (wontfix)

WP 3.5 Tinymce Button Opacity

Reported by: josh401 Owned by:
Milestone: Priority: normal
Severity: normal Version: 3.5
Component: TinyMCE Keywords:
Focuses: Cc:


Hello everyone,

I have a small request. The button opacity set for buttons which are inactive in the tinymce editor is really low, in my humble opinion.

Here is the current css being used:

.wp_themeSkin .mceButtonDisabled .mceIcon {
    opacity: 0.2;

For many custom buttons... this makes it almost "greyed out" when viewing the inactive button in the editor.

I know it's a very subjective.. but I think an opacity of 0.5 is much better.

You can see in the screenshot... the fourth button over from the left on the bottom row... is almost "invisible" in it's inactive state.

Thank you for your consideration.

Attachments (1)

trac-button-opacity.png (20.6 KB) - added by josh401 8 years ago.

Download all attachments as: .zip

Change History (4)

#1 @helenyhou
8 years ago

  • Milestone Awaiting Review deleted
  • Resolution set to wontfix
  • Status changed from new to closed

A higher opacity makes it nearly impossible to tell what is disabled and what is not among the default buttons, which is what influenced the value chosen for core. If a particular custom icon has a problem, then perhaps the icon should be changed or it should be accounted for individually. I'm not sure that a disabled button really needs to be clearer, though I do see one that essentially disappears, likely because it was too light to begin with.

#2 @markoheijnen
8 years ago

I do think from an accessibility perspective the opacity can be to low and we can make it 0.3. It still has the felling the buttons are disabled.

#3 @josh401
8 years ago

I'm not sure why it affects custom buttons this way. I've tried a different image.. with the same results. I will keep experimenting. Perhaps it has something to do with using a sprite image?

Thanks for the consideration!

Note: See TracTickets for help on using tickets.