3 ms·

I switched to Firefox for a week and wanted to kill myself. Basically, extensions still aren't forced to behave. As soon as you install a non-e10s extension, it

I switched to Firefox for a week and wanted to kill myself. Basically, extensions still aren't forced to behave. As soon as you install a non-e10s extension, it disables e10s entirely, and then you're in the bad old days of single-process train wreck. LastPass specifically seems like it has a bug where it locks the UI (beachball) while it populates login fields, and if you've got a lot of passwords (which we do), it'll take several seconds to unlock. Basically unusable. I know these sound like LastPass problems, but the browser needs to sandbox these sketchy things better. I believe that getting from here to there is a really tough ecosystem problem, and while I appreciate Mozilla's philosophy on the open web, Chrome is simply better.

aswan 10y ago
There is a lot of work underway in this area. The Webextensions project is the big long-term effort. But regarding e10s, it is true that e10s is an all-or-nothing proposition. However, as of Firefox 51, extensions do not disable e10s unless they are explicitly marked as incompatible with e10s. The rollout was deliberately done slowly in this area to favor stability over getting e10s enabled quickly, I think that was pretty clearly the right decision.
untangle 10y ago
I had reversion episodes too – until I followed the protocol described by AdamKalisz on Superuser [1]. The "extra" steps made a big difference. [1] https://superuser.com/questions/1029400/how-to-enable-electrolysis-e10s-on-mozilla-firefox-beta https://superuser.com/questions/1029400/how-to-enable-electr...