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

[Tor Bug Tracker & Wiki]

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

 Replying to [ticket:21432 gk]:
 > Our current goal is to make Tor Browser based on ESR 52 ready for
 content sandboxing (e10s).
 Content Sandboxing is another task:
 https://wiki.mozilla.org/Firefox/AddOns/Status/current#Sandboxing
 To make Tor Browser based on ESR 52 ready for content sandboxing, ESR 52
 should be ready for e10s.
 > While the work is done in different bugs we need to create a plan on how
 we want to deploy it. For that we need to investigate first how Mozilla is
 shipping it in Firefox 52 ESR.
 e10s qualification criteria for ESR52:
 https://bugzilla.mozilla.org/show_bug.cgi?id=1329752
 > The goal in 53 is to allow e10s to expand to all users, unless they have
 add-ons marked specifically MPC=False (not multiprocess compatible)
 So, it's a nice thing to investigate on alphas, but not for the stable.

 Also, in order to stop spending time on Mozilla's experiments your effort
 should be targeted to conversion to WebExtensions compatible with e10s-
 multi.

--
Ticket URL: <https://trac.torproject.org/projects/tor/ticket/21432#comment:4>
Tor Bug Tracker & Wiki <https://trac.torproject.org/>
The Tor Project: anonymity online