Yeah but what about web extensions ?Virtual_ManPL wrote:BTW Classic Theme Restorer is compatible with e10s.
I always get those two confused. Could you tell me the difference please?
?
Yeah but what about web extensions ?Virtual_ManPL wrote:BTW Classic Theme Restorer is compatible with e10s.
Thanks Aris!Aris wrote:Multi-process mode is also called e10s (electrolysis) and means your browser runs in multiple processes (e.g. task manager > multiple firefox.exe processes).
"Web extensions" is a different kind of add-on environment. They are not based on XUL anymore like legacy add-ons (e.g. CTR).
A little bit. Quite a few add-ons (although not really any big ones) didn't get the necessary code changes. This has kept Mozilla from enabling e10s on the release channel for all users by default. What I don't get, is that they just as well can disable all add-ons that aren't MPC=true (like they did on Nightly recently), and let the good/motivated add-on developers keep on developing their add-ons as they have always done. This might (probably will) cause an outcry because users have their add-ons seemingly randomly disabled, but what they are doing now is *a lot* worse.Aris wrote:The upcoming drop of legacy add-ons has nothing to do with browsers multi-process architecture. While it of course benefits of it, it was not the main reason according to Mozilla.
I expect this will land before. (55-56) I don't plan to update to 57+ for a long while anyway. (Unless some good alternative build retains xul addons)Aris wrote:Maybe, if there will be a way in Fx57+ to apply css style sheets for the browser ui.
Ah, okay. Didn't pay attention to that.Aris wrote:The "demo video" showed Photon ui so I assumed this change is meant for Fx57+ builds. If it will land on Fx 55-56 it sure can be replaced somehow.
What is your plan, stay on Fx 56 or go back to Fx 52 ESR once Fx 57 arrives?
I've been seeing buttons becoming blank then becoming normal again in the past days. (download button, closed tabs button)