Make WordPress Core

Opened 6 years ago

Closed 4 years ago

#11645 closed defect (bug) (duplicate)

Admin style, input fields and dark OS themes

Reported by: tonyf12 Owned by:
Milestone: Priority: normal
Severity: normal Version: 3.0.1
Component: Accessibility Keywords: has-patch close
Focuses: Cc:


On the ACP, if you are using a dark OS theme (for example the HumanLogin theme included in Ubuntu), many of the form fields have an explicit background-color:#FFFFFF set. On most dark themes, the default font color is also white, so this causes the form fields to be displayed as white text on white background.

Possible fixes:
Remove the explicit background-color declaraton.
Add an explicit color:black declaration

Attachments (2)

11645.diff (1.6 KB) - added by andrewryno 5 years ago.
11645.2.diff (653 bytes) - added by andrewryno 5 years ago.

Download all attachments as: .zip

Change History (21)

#1 @tonyf12
6 years ago

Trac stripped out some newlines I didn't expect. I hope it's still readable.

#2 @hakre
6 years ago

  • Component changed from General to Accessibility

Then we need to reset the foreground colors as well.

Related: #10881

#3 @hakre
6 years ago

  • Keywords needs-patch reporter-feedback added
  • Milestone changed from Unassigned to 3.0

Can you please make a screenshot and upload it?

#4 @hakre
6 years ago

Realted: #10985

#5 @rfair404
6 years ago

I tried to duplicate this issue on several OS's and browsers and all I found was that on certain high contrast settings this issue exists.


Ubuntu 9.10 64 bit high contrast, only firefox is effected, tested fine on ie and ff on windows 7


#6 @nacin
6 years ago

  • Type changed from enhancement to defect (bug)

#7 @nacin
6 years ago

  • Milestone changed from 3.0 to Future Release

Future pending patch.

#8 @tonyf12
5 years ago

  • Keywords reporter-feedback removed
  • Version changed from 2.9 to 3.0.1

A bit of further feedback:

Chrome is unaffected, as are most of the windows browsers. Firefox on Linux uses the OS controls however, so is affected. Also still exists as of 3.0.1



#9 follow-up: @tonyf12
5 years ago

  • Version changed from 3.0.1 to 2.9

Actually, just totally ignore that, I misread the issue I reported myself. Sorry, how do I delete comments?

#10 in reply to: ↑ 9 @tonyf12
5 years ago

  • Version changed from 2.9 to 3.0.1

Replying to tonyf12:

Actually, just totally ignore that, I misread the issue I reported myself. Sorry, how do I delete comments?

*sigh* Ok, I'm really sorry, but turns out I was right with the files the first time.

#11 @hakre
5 years ago

  • Keywords dev-feedback added

Maybe something for UI?

#12 @ocean90
5 years ago

  • Keywords ui-feedback added; dev-feedback removed

If UI, then use ui-feedback.

5 years ago

#13 @andrewryno
5 years ago

Attached possible fix. I don't have Linux to test it with, so someone else may have to do that.

5 years ago

#14 @andrewryno
5 years ago

Ignore the first one. Had some left over changes from another fix.

#15 @hakre
5 years ago

Thanks for looking into this and providing a patch. Patch looks good in my eyes.

#16 @SergeyBiryukov
4 years ago

  • Keywords has-patch added; needs-patch removed

#17 @seolife
4 years ago


Last edited 4 years ago by ocean90 (previous) (diff)

#18 @helenyhou
4 years ago

  • Keywords close added; ui-feedback removed

Duplicate: #19923, marked as commit for 3.4. Might want to close this one in favor of, but will let somebody else decide which is best.

#19 @SergeyBiryukov
4 years ago

  • Milestone Future Release deleted
  • Resolution set to duplicate
  • Status changed from new to closed
Note: See TracTickets for help on using tickets.