We're calling on all EU-based Mozillians with iOS or iPadOS devices to help us monitor Apple’s new browser choice screens. Join the effort to hold Big Tech to account!

Шукати в статтях підтримки

Остерігайтеся нападів зловмисників. Mozilla ніколи не просить вас зателефонувати, надіслати номер телефону у повідомленні або поділитися з кимось особистими даними. Будь ласка, повідомте про підозрілі дії за допомогою меню “Повідомити про зловживання”

Докладніше

Ця тема перенесена в архів. Якщо вам потрібна допомога, запитайте.

userChrome code for checkmark color in Preferences?

  • 3 відповіді
  • 1 має цю проблему
  • 1 перегляд
  • Остання відповідь від nbi.vegas

more options

Using the Dark Theme in TB 78.12.0 causes the check marks in the Preferences check boxes to be invisible because the check marks are black against a black background. Is there any way to force the check marks to be white via userChrome css?

Using the Dark Theme in TB 78.12.0 causes the check marks in the Preferences check boxes to be invisible because the check marks are black against a black background. Is there any way to force the check marks to be white via userChrome css?

Усі відповіді (3)

more options

I'm using Windows 10 In 'Options' (which is the same as 'Preferences' in a mac) The left pane selection text/icon eg: General - if selected - will use blue colour to indicate what is selected.

All checkmarks in selected checkboxes are also blue.

This is the same regardless of using Light or Dark theme.

Do you see the same problem if you restart Thunderbird in Safe Mode ?

more options

What OS are you using?

more options

Using linux. I found a crude workaround - I temporarily switch foreground and background colors. Obviously this is a PITA and not a long term solution as this will be necessary whenever a preferences change is needed. I spent a lot of time researching how to do this via userChrome, but was unable to find anything. Dark Theme isn't anything unusual or exotic so it should really be a built-in option which is properly supported. TB waving off responsibility by blaming the theme is a bunch of crap. End users shouldn't be forced to spend so much time dicking around with something that should be a fundamental feature that has undergone a basic level of QA. Sorry for venting, but this sort of thing really gets under my skin. I guess it's a case of the old adage "you get what you pay for".