Implement better communication between NoScript and Tor Browser

While preparing the Tor Browser 8 release we ran into a number of issues with communicating with NoScript and getting the Security Slider to work (legacy/trac#26520 (moved), legacy/trac#27401 (moved), legacy/trac#27411 (moved)). We should implement a better approach for communictaion. The currently best plan is outlined in comment:33:ticket:26520:

If we wanted to be absolutely sure, NoScript could be patched to listen for a "ping" and reply with a "pong". And then torbutton could repeatedly send "ping" (say, once a second) until it receives a "pong", and then proceed by sending the first updateSettings message.

added TorBrowserTeam201809 in Legacy / Trac component::applications/tor browser in Legacy / Trac gitlab-tb-torbutton in Legacy / Trac noscript in Legacy / Trac owner::tbb-team in Legacy / Trac priority::very high in Legacy / Trac severity::normal in Legacy / Trac status::new in Legacy / Trac tbb-security-slider in Legacy / Trac tbb-torbutton in Legacy / Trac type::enhancement in Legacy / Trac labels

One thing to note: While testing the workaround for legacy/trac#27411 (moved) I saw that applying the safer and safest settings seem to block startup significantly. That's again only on Windows and the symptom is a Tor Launcher dialog showing the "Connected" state but only going away after up to some seconds.

I won't file a separate bug for this assuming our fix for this bug will solve this issue as well.

Trac:
Keywords: N/A deleted, noscript added

Trac:
Cc: arthuredelstein, ma1 to arthuredelstein, ma1, intrigeri

Add magic gitlab keyword.

Trac:
Keywords: N/A deleted, gitlab-tb-torbutton added

mentioned in issue legacy/trac#31572 (moved)

moved from legacy/trac#27413 (moved)

added Feature label and removed 1 deleted label

added NoScript Security Settings labels and removed 1 deleted label

I think this does not apply anymore.

closed