-
Notifications
You must be signed in to change notification settings - Fork 3
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Breakage with Tor Browser (observed from 1.0.8.6 to 1.0.10.2+) #14
Comments
Confirmed with Ff 57.03 x64 on Win 10 x64 b16299, except for the browser freeze when opening console.
Clicking |
Yes indeed https://addons.mozilla.org/en-GB/firefox/addon/policy-control/ If active the console is showing With said extension there is no option to unblock Which one to unblock? Now having Policy Control disabled the bug is still present. The console output reading |
Meantime upgraded 1.0.9.1 Clicking
|
|
I tested with stock Tor Browser (in an ephemeral setup). Almost all Tor Browser settings were default; the exceptions are such matters as raising the Security Slider (actually, I preset a This is the Linux distribution of Tor Browser. |
perfect, works like a charm. Though not part of this bug I was wondering whether with the subdomains it might confuse new users of this extension having to click several times (n = number of subdomains) until the site is finally loading. Might be worth considering to highlight/bold on the blocking site. That is just a thought since during first exposure I kept on wondering why the block page kept on reappearing. |
This has been reported by others, as of 1.0.10.2 with Tor Browser:
Good question, that last. I think no, but I’m not sure. I am also still experiencing this problem (although not the freeze/CPU-spin I did in 1.0.8.6). |
Earlier, I installed 1.0.8.6 on Tor Browser “7.0.11 (based on Mozilla Firefox 52.5.2) (64-bit)”. The whitelisting and options UI did not work.
I tried to open the Browser Console to figure out what was happening; but the whole browser froze, spinning my CPU, and I had to kill it. Thus, I could not get any useful debug information; and I have not had time to investigate further. Also I’ve not had time to test adequately against older versions, to see if it be a regression. Apologies for the substance-starved bug report.
@whatsusername, I know that Tor Browser dislikes localstorage in its default configuration. Could that be the cause? I know that sites aren’t allowed localstorage; but I have no idea if/how that impacts add-ons.
The text was updated successfully, but these errors were encountered: