Weird behaviour in FF 52
Posted: Thu Mar 16, 2017 11:13 am
Ever since updating to Firefox 52 I'm encountering the following:
NoScript configuration:
+ Temporarily allow top-level sites by default
+ Base 2nd level Domains (noscript.net)
Upon opening a new URL in browser (almost any URL I haven't opened in the current Firefox session yet) all the stuff sourced from the primary domain is blocked by NoScript.
If I just reload the website (and don't really do anything else) it starts behaving as it should and continues so (but only for that particular website - I have to do the same thing for all others) until I quit the Firefox process. If I quit and relaunch it, I basically start over with it again.
I tried disabling and re-enabling that mentioned NoScript configuration, but it didn't make any difference.
I use pretty much the same configuration at Windows & macOS (settings synchronized with noscript.sync.enabled being set to true) and it behaves identically at both these operating systems (and both running Firefox 52 there).
Is there anything I can do to diagnose/troubleshoot this issue somehow?
NoScript version 5.0.1
EDIT: I can also confirm that after downgrading to Firefox 51.0.1 the issue is gone.
NoScript configuration:
+ Temporarily allow top-level sites by default
+ Base 2nd level Domains (noscript.net)
Upon opening a new URL in browser (almost any URL I haven't opened in the current Firefox session yet) all the stuff sourced from the primary domain is blocked by NoScript.
If I just reload the website (and don't really do anything else) it starts behaving as it should and continues so (but only for that particular website - I have to do the same thing for all others) until I quit the Firefox process. If I quit and relaunch it, I basically start over with it again.
I tried disabling and re-enabling that mentioned NoScript configuration, but it didn't make any difference.
I use pretty much the same configuration at Windows & macOS (settings synchronized with noscript.sync.enabled being set to true) and it behaves identically at both these operating systems (and both running Firefox 52 there).
Is there anything I can do to diagnose/troubleshoot this issue somehow?
NoScript version 5.0.1
EDIT: I can also confirm that after downgrading to Firefox 51.0.1 the issue is gone.