Problem: TOR v8.0.3 erases NoScript Per-Site Permissions when closed & requires re-import
The latest TOR v8.0.3 Win32 Browser update 60.3.0esr release with a NoScript update as of 10/18/18 still does not fix TOR Devs breaking NoScript...
The problem that I have experienced for the past several months with Win10 v1803/v1809 is NoScript Per-Site Permissions auto-erased when TOR Browser closes and requires the manual re-import or rebuild of NoScript Per-Site Permissions.
If NoScript Per-Site Permissions are removed while running NoScript with TOR, most Internet websites access that use Javascript, Cookies, etc. are blocked until either the website is manually re-inserted into the NoScript Per-Site Permissions list or else NoScript is disabled as an add-on App.
Other TOR users have complained about recent TOR mods from TOR Devs that also broke NoScript. TOR Staff apparently closed these complaints as SOLVED without acknowledgement of the problem and no ETA for a fix...
Enclosed are TOR Troubleshooting text that describe the software environment on my Laptop.
Why did TOR break the use of NoScript Per-Site Permissions with TOR Win32 Browser that worked OK up to several months ago and is a fix currently scheduled for release?
Trac:
Username: Questor