NoScript gets disabled after a while

It was discovered that the Tor Browser fix for #16694 (closed) (armagadd-on-2.0) isn’t complete. All is fine the first run, but if you restart Tor Browser it will eventually recheck NoScript’s validity and fail. There will be a Tor Browser 8.0.9-build2 because of this. The situation is better for Tails thanks to our amnesic filesystem: each time you boot Tails you get a “first” start, unlike outside of Tails. So we can keep -build1 in Tails 3.13.2 and instruct users to not restart Tor Browser (restart Tails instead).

This should be fixed once we import Tor Browser in the next release.

• Tor Browser bug: https://trac.torproject.org/projects/tor/ticket/30388
• Mozilla bug: https://bugzilla.mozilla.org/show_bug.cgi?id=1549344

Related issues

• Related to #16694 (closed)
• Related to #16690 (closed)
• Related to #16337 (closed)
• Blocks #16209

Original created by @anonym on 16706 (Redmine)