#21432: Make a plan on how to deploy e10s in Tor Browser --------------------------------------------+-------------------------- Reporter: gk | Owner: tbb-team Type: task | Status: new Priority: Medium | Milestone: Component: Applications/Tor Browser | Version: Severity: Normal | Resolution: Keywords: ff52-esr, TorBrowserTeam201702 | Actual Points: Parent ID: | Points: Reviewer: | Sponsor: --------------------------------------------+--------------------------
Comment (by mcs): My feeling is that we should keep things as simple as possible: once we make sure that the add-ons we bundle are working correctly with multiple processes, we should enable e10s by default for all Tor Browser users. Most of what Mozilla is doing is to accommodate add-ons that do not support e10s, but since we do not really support third party add-ons it seems reasonable for Tor Browser to use a simpler approach than Firefox. Also, if we believe https://wiki.mozilla.org/Electrolysis#Schedule then e10s mode will be on by default for all Firefox 52 users (I am not sure if something different will be done for the ESR though). If we adopt this approach, it means that someone who wants to use an add- on that is not compatible with e10s will need to turn off e10s mode via about:config. Mozilla has used several different prefs to control e10s (which has led to some confusion), so we will need to ensure that we provide good instructions on how to disable it. There is also a chance that we will discover that e10s mode in ESR52 is too slow or not stable enough to turn on by default. -- Ticket URL: <https://trac.torproject.org/projects/tor/ticket/21432#comment:1> Tor Bug Tracker & Wiki <https://trac.torproject.org/> The Tor Project: anonymity online _______________________________________________ tor-bugs mailing list tor-bugs@lists.torproject.org https://lists.torproject.org/cgi-bin/mailman/listinfo/tor-bugs