Mozilla Monitor website will be down for 2 hours starting 5/20/2025 at 6 AM PT. Visit our status site for updates.

Avatar for Username

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

Este fío arquivouse. Faga unha nova pregunta se precisa axuda.

Since the 91 update, check-boxes are not checked after clicking.

  • 2 respostas
  • 1 has this problem
  • 3 views
  • Last reply by jcl23

jcl23
jcl23

Now, when I click on a checkbox it may darken a very little but it is not checked or filled in.I see this was asked a year ago with no apparent answer. Here it is again in version 91.0.

Now, when I click on a checkbox it may darken a very little but it is not checked or filled in.I see this was asked a year ago with no apparent answer. Here it is again in version 91.0.
Capturas de pantalla anexas

Chosen solution

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

In Firefox 91+ you can no longer disable Proton and revert changes that come with this design via "browser.proton.enabled = false" on the about:config page. Best in Firefox 91+ is to set browser.proton.enabled at its default value true as the false setting can cause issues.

In Firefox 91+ you need to use code in userChrome.css to override changes coming with the Proton design.

Ler a resposta no contexto 👍 1

All Replies (2)

cor-el
cor-el
  • Moderator

Chosen Solution

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

In Firefox 91+ you can no longer disable Proton and revert changes that come with this design via "browser.proton.enabled = false" on the about:config page. Best in Firefox 91+ is to set browser.proton.enabled at its default value true as the false setting can cause issues.

In Firefox 91+ you need to use code in userChrome.css to override changes coming with the Proton design.

jcl23
jcl23 Question owner

Ahah, my own damn fault! Exactly right, I forgot to reset the "browser.proton.enabled" setting back to false when I tried the userCrome.css code. Thank you VERY much!

BTW, another vote AGAINST Proton! Wish we could revert back and Mozilla would stop messing around with a previously great interface just for the sake of change.