This site will have limited functionality while we undergo maintenance to improve your experience. If an article doesn't solve your issue and you want to ask a question, we have our support community waiting to help you at @FirefoxSupport on Twitter and/r/firefox on Reddit.

Search Support

Avoid support scams. We will never ask you to call or text a phone number or share personal information. Please report suspicious activity using the “Report Abuse” option.

Learn More

FF on Mac OS is now white and can't see boxes or when marking check boxes

  • 2 respostas
  • 1 has this problem
  • 3 views
  • Last reply by cor-el

more options

When browsing sites the browser seems to be white on white. It happened after an auto update. I can't see some boxes or when I check some boxes. Any help would be great.

When browsing sites the browser seems to be white on white. It happened after an auto update. I can't see some boxes or when I check some boxes. Any help would be great.

Chosen solution

cor-el said

This could be a problem with High Contrast Mode on Mac. See "New" in the release notes. Firefox now automatically enables High Contrast Mode when "Increase Contrast" is checked on MacOS in the Accessibility settings.

Make sure you allow pages to choose their own colors.

  • Settings -> General: Fonts & Colors -> Colors: "Override the colors specified by the page with my selections above"

Try "Never" if the default "Only with High Contrast themes" isn't working.

Ler a resposta no contexto 👍 1

All Replies (2)

more options

Chosen Solution

cor-el said

This could be a problem with High Contrast Mode on Mac. See "New" in the release notes. Firefox now automatically enables High Contrast Mode when "Increase Contrast" is checked on MacOS in the Accessibility settings.

Make sure you allow pages to choose their own colors.

  • Settings -> General: Fonts & Colors -> Colors: "Override the colors specified by the page with my selections above"

Try "Never" if the default "Only with High Contrast themes" isn't working.

more options

This can happen if you have set "browser.proton.enabled = false" on the about:config page to disable Proton.