Avatar for Username

Pretraži podršku

Izbjegni prevare podrške. Nikad te nećemo tražiti da nas nazoveš, da nam pošalješ telefonski broj ili da podijeliš osobne podatke. Prijavi sumnjive radnje pomoću opcije „Prijavi zlouporabu”.

Saznaj više

Ova tema je arhivirana. Postavi novo pitanje ako trebaš pomoć.

extensions.e10sBlockedByAddons keeps resetting to 'true' - why ?

  • 1 odgovor
  • 1 ima ovaj problem
  • 2 prikaza
  • Posljednji odgovor od cor-el

e10s-now
e10s-now
more options

i have only chosen addons that, according to mozilla's 'addon compatibility reporter' are all compatible with multiprocess. and i don't even have any non-compatible addons installed. i can confirm that e10s is definitely enabled when checking about:support. however, any time i click enable/disable on an addon, the about:config option extensions.e10sBlockedByAddons will reset to 'true' the next time firefox is started !! why ??? sometimes this seems to reset subtley in the background, and i don't notice straight away. and even when i do notice i have to restart the whole browser >.< what a pain

i have only chosen addons that, according to mozilla's 'addon compatibility reporter' are all compatible with multiprocess. and i don't even have any non-compatible addons installed. i can confirm that e10s is definitely enabled when checking about:support. however, any time i click enable/disable on an addon, the about:config option extensions.e10sBlockedByAddons will reset to 'true' the next time firefox is started !! why ??? sometimes this seems to reset subtley in the background, and i don't notice straight away. and even when i do notice i have to restart the whole browser >.< what a pain

Izmjenjeno od e10s-now

Izabrano rješenje

See also:

You can consider to set the pref to false via the user.js file in the profile folder. That way it is at least disabled on a Firefox start.

Pročitaj ovaj odgovor u kontekstu 👍 0

Svi odgovori (1)

cor-el
cor-el
  • Moderator
  • Top 10 Contributor
more options

Odabrano rješenje

See also:

You can consider to set the pref to false via the user.js file in the profile folder. That way it is at least disabled on a Firefox start.