Przeszukaj pomoc

Unikaj oszustw związanych z pomocą.Nigdy nie będziemy prosić Cię o dzwonienie na numer telefonu, wysyłanie SMS-ów ani o udostępnianie danych osobowych. Zgłoś podejrzaną aktywność, korzystając z opcji „Zgłoś nadużycie”.

Więcej informacji

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

  • 1 odpowiedź
  • 1 osoba ma ten problem
  • 2 wyświetlenia
  • Ostatnia odpowiedź od cor-el

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

Zmodyfikowany przez e10s-now w dniu

Wybrane rozwiązanie

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.

Przeczytaj tę odpowiedź w całym kontekście 👍 0

Wszystkie odpowiedzi (1)

more options

Wybrane rozwiązanie

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.