News for hackers. Stuff that matters.
Re:What’s up with Firefox? by jsight on Wednesday January 25, 2017 @01:34PM (#13484353)
I assume the problem is just that it seems to be moving towards completion at a snail's pace. It certainly feels like I have been hearing about it for a LONG time without a stable release.
Re:What’s up with Firefox? by KingMob on Wednesday January 25, 2017 @01:41PM (#13484450)
Yeah, but it's a massive reworking of the FF internals, so it took a long time to complete. But I'm using it now, and it works pretty well.

My only hitch was needing to turn off some older add-ons. While Mozilla is still doing a slow roll-out, it disables E10s if it can't ensure your plugins will work. (One of mine was a HN add-on, amusingly.)

Most of the opoular add-ons are ready, though. To check, see: https://www.arewee10syet.com/

Re:What’s up with Firefox? by Aldo_MX on Wednesday January 25, 2017 @03:57PM (#13486007)
I would recommend the following add-on to know which add-ons are incompatible with e10s:

https://addons.mozilla.org/en-US/firefox/addon/add-on-compat...

Re:What’s up with Firefox? by jsight on Wednesday January 25, 2017 @02:07PM (#13484792)
Of course, the reasons for it taking a while to get done are completely reasonable. :)
Re:What’s up with Firefox? by cpeterso on Wednesday January 25, 2017 @04:41PM (#13486473)
The e10s project actually stated back in 2009. The project was put on hold in 2011 because the architectural changes and add-on compatibility breakage was deemed insurmountable. In 2013, the project resumed and has been chugging away since.

You can see 2011-2013 pause in the revision history of Mozilla's Electrolysis wiki page:

https://wiki.mozilla.org/index.php?title=Electrolysis&offset...

I made a burndown chart of the e10s bugs in Bugzilla that shows the development progress. The bug high water mark was in 2016 and today at least 2,495 bugs (specifically tagged as e10s related) have been fixed:

https://people-mozilla.org/~cpeterson/burndown/burndown.html...

Re:What’s up with Firefox? by sp332 on Wednesday January 25, 2017 @02:03PM (#13484743)
But e10s launched in Firefox 48 https://asadotzler.com/2016/06/06/firefox-48-beta-release-an... and hit 35% of all Firefox users by November. https://wiki.mozilla.org/Electrolysis#Schedule
Re:What’s up with Firefox? by oconnore on Wednesday January 25, 2017 @01:43PM (#13484470)
It might be because it's running without you knowing about it? Preferences > Enable multi-process is checked for me.
Re:What’s up with Firefox? by homulilly on Wednesday January 25, 2017 @02:49PM (#13485305)
Still doesn't work in a number of situations like if you have a touch screen.
Re:What’s up with Firefox? by dblohm7 on Wednesday January 25, 2017 @03:46PM (#13485889)
You must be running Windows. I'm the Mozilla developer who is responsible for that. You'll get e10s on touchscreen in version 52.
Re:What’s up with Firefox? by homulilly on Wednesday January 25, 2017 @08:27PM (#13487960)
Yeah that's correct. Awesome!
Re:What’s up with Firefox? by oconnore on Wednesday January 25, 2017 @03:05PM (#13485481)
(I just clicked the reply button to you using my touch screen on e10s. This is Fedora 25, on Wayland -- Firefox is using XWayland.)
Re:What’s up with Firefox? by sp332 on Wednesday January 25, 2017 @04:26PM (#13486311)
I think this is a Win8 problem. https://wiki.mozilla.org/Electrolysis#Schedule
Re:What’s up with Firefox? by jsight on Wednesday January 25, 2017 @02:05PM (#13484770)
I don't believe that I have that option at all here (Firefox 51.0 on Fedora 25).
Re:What’s up with Firefox? by sp332 on Wednesday January 25, 2017 @02:15PM (#13484886)
This is kinda confusing, but that button only exists in Nightly and Developer builds. Here's how to check, enable, and force-enable it for regular builds: https://wiki.mozilla.org/Electrolysis#Testing
Re:What’s up with Firefox? by djsumdog on Wednesday January 25, 2017 @02:50PM (#13485310)
I did have to force enable it as a few plugins didn't official support it yet. So far it's been amazingly stable though and had sped up my browser considerably.