Ko tenda hembiapoite sa’ivéta oñemba’apokuévo hese hembiapo porãve hag̃ua. Peteĩ jehaipyre nomoĩporãiramo ne apañuái ha eporanduséramo, roguerekohína ore nepytyvõ rekoha ikatútava ndeykeko @FirefoxSupport Twitter-pe ha avei /r/firefox Reddit-pe.

Eheka Pytyvõha

Emboyke pytyvõha apovai. Ndorojeruremo’ãi ehenói térã eñe’ẽmondóvo pumbyrýpe ha emoherakuãvo marandu nemba’etéva. Emombe’u tembiapo imarãkuaáva ko “Marandu iñañáva” rupive.

Kuaave

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

  • 1 Mbohovái
  • 1 oguereko ko apañuái
  • 8 Hecha
  • Mbohovái ipaháva 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

Moambuepyre e10s-now rupive

Ñemoĩporã poravopyre

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.

Emoñe’ẽ ko mbohavái ejeregua reheve 👍 0

Opaite Mbohovái (1)

more options

Ñemoĩporã poravopyre

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.