Important Notice: We're experiencing email notification issues. If you've posted a question in the community forums recently, please check your profile manually for responses while we're working to fix this.

On Monday the 3rd of March, around 5pm UTC (9am PT) users may experience a brief period of downtime while one of our underlying services is under maintenance.

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

Hierdie gesprek is in die argief. Vra asseblief 'n nuwe vraag as jy hulp nodig het.

About:config accessibility settings not being saved

  • 1 antwoord
  • 1 het hierdie probleem
  • 1 view
  • Laaste antwoord deur Happy112

more options

FF56 in Win 10. I'm trying to enable multiprocess, and after disabling the remaining addon (after doing "Refresh"), about:support multiprocess shows "disabled by accessibility tools". After googling, in about:config I tried setting accessiblity.loadedinlastsession false and accessibility.lastloaddate reset, but those aren't being saved, so about:support still says multiprocess is disabled. Any suggestions on why the settings aren't sticking? Like I said, a Refresh didn't work. TY.

FF56 in Win 10. I'm trying to enable multiprocess, and after disabling the remaining addon (after doing "Refresh"), about:support multiprocess shows "disabled by accessibility tools". After googling, in about:config I tried setting accessiblity.loadedinlastsession false and accessibility.lastloaddate reset, but those aren't being saved, so about:support still says multiprocess is disabled. Any suggestions on why the settings aren't sticking? Like I said, a Refresh didn't work. TY.

All Replies (1)

more options

Hi  !

Could it be that after you toggled those preferences, you didn't close and then restart Firefox  ? That would explain it .....


You say that you're trying to enable Multi-process - did you set the values of these preferences to true:

browser.tabs.remote.autostart

browser.tabs.remote.autostart.2