Adapt Tor Launcher to TBB/FF52ESR

Tor Launcher probably needs some tweaks for ESR52, especially with e10s enabled.

added TorBrowserTeam201703R component::applications/tor browser ff52-esr owner::tbb-team parent::20680 priority::medium resolution::fixed severity::normal status::closed tbb-7.0-must tbb-7.0-must-nightly type::defect labels

If you know of specific things that need to be fixed in Tor Launcher, please let Kathy and I know. Since Tor Launcher does not interact with browser content, it may not need any changes for e10s. In any case, Kathy and I have not found anything so far that needs to be fixed for ESR52 or e10s beyond adding <em:multiprocessCompatible>true</em:multiprocessCompatible> to install.rdf. But we have not done a lot of testing yet either.

Trac:
Cc: N/A to brade, mcs

Trac:
Keywords: N/A deleted, tbb-7.0-must added

Getting those tickets on our March radar as well.

Trac:
Keywords: N/A deleted, TorBrowserTeam201703 added

Replying to mcs:

If you know of specific things that need to be fixed in Tor Launcher, please let Kathy and I know. Since Tor Launcher does not interact with browser content, it may not need any changes for e10s. In any case, Kathy and I have not found anything so far that needs to be fixed for ESR52 or e10s beyond adding <em:multiprocessCompatible>true</em:multiprocessCompatible> to install.rdf. But we have not done a lot of testing yet either.

I did some testing and it all seems to be working. I'll close this ticket for now and we can open individual tickets if specific ESR52 or e10s issues pop up. Sorry for the false alarm! :)

Trac:
Status: new to closed
Resolution: N/A to worksforme

Replying to arthuredelstein:

Replying to mcs:

If you know of specific things that need to be fixed in Tor Launcher, please let Kathy and I know. Since Tor Launcher does not interact with browser content, it may not need any changes for e10s. In any case, Kathy and I have not found anything so far that needs to be fixed for ESR52 or e10s beyond adding <em:multiprocessCompatible>true</em:multiprocessCompatible> to install.rdf. But we have not done a lot of testing yet either.

I did some testing and it all seems to be working. I'll close this ticket for now and we can open individual tickets if specific ESR52 or e10s issues pop up. Sorry for the false alarm! :)

But we should patch the install.rdf and add the e10s compat item. Seems fine to me doing that in this ticket pointing to a patch.

Trac:
Status: closed to reopened
Resolution: worksforme to N/A

bug_21546 (https://gitweb.torproject.org/user/gk/tor-launcher.git/commit/?h=bug_21546&id=336e7c8731296866dd67a090c010e41fcc26ef69) in my public tor-launcher repo has the proposed amendment.

Trac:
Status: reopened to needs_review
Keywords: TorBrowserTeam201703 deleted, TorBrowserTeam201703R added

r=brade, r=mcs

We want those tickets for our first ESR52 nightlies.

Trac:
Keywords: N/A deleted, tbb-7.0-must-nightly added

That's commit 336e7c8731296866dd67a090c010e41fcc26ef69 on master now.

Trac:
Resolution: N/A to fixed
Status: needs_review to closed

closed

moved to tpo/applications/tor-browser#21546 (closed)