Re: [tor-bugs] #21432 [Applications/Tor Browser]: Make a plan on how to deploy e10s in Tor Browser

["Tor Bug Tracker & Wiki" <blackhole@xxxxxxxxxxxxxx>]

#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 gk):

 Replying to [comment:1 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.

 I am debating whether we actually should follow Mozilla here because there
 is the inherent risk that users will just complain Tor Browser is not
 working while Firefox is which seems a thing we can actually avoid.
 Additionally, we would be avoiding bugs that Mozilla is not hitting
 because they disabled e10s if known extensions are installed that are
 incompatible with it.

 This entails a lot of complexity. I think we should try to understand how
 complex that system actually is (Are there any updates to the list of
 incompatible extensions shipped? If so, how? What about add-ons where the
 e10s compatibility is not known? etc.) and make then a final decision
 whether it is worth taking the shortcut you propose or not.

--
Ticket URL: <https://trac.torproject.org/projects/tor/ticket/21432#comment:3>
Tor Bug Tracker & Wiki <https://trac.torproject.org/>
The Tor Project: anonymity online
_______________________________________________
tor-bugs mailing list
tor-bugs@xxxxxxxxxxxxxxxxxxxx
https://lists.torproject.org/cgi-bin/mailman/listinfo/tor-bugs