Whilst running Firefox in a terminal I've spotted this strange message:
console.log: NoScript could not disable scripts for system global [System Principal]
I think it was one of those news websites containing loads of those cross-site requests calling each other, I was trying to watch a video that could clearly not be loaded without probably allowing everything so I just gave up.
But then I spotted that message and decided to ask, just in case it was something interesting.
Chrome 45.0 (Windows 10 - 64 bit) / Mozilla/5.0 (Windows NT 10.0; WOW64) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/45.0.2454.93 Safari/537.36
Probably not interesting. Giorgio would know more about where the message comes from. Actually, it sounds like you have a higher-than-default level of logging enabled.
======
Thrawn
------------
Religion is not the opium of the masses. Daily life is the opium of the masses.
True religion, which dares to acknowledge death and challenge the way we live, is an attempt to wake up.
Mozilla/5.0 (X11; Ubuntu; Linux x86_64; rv:42.0) Gecko/20100101 Firefox/42.0
Thanks for your reply, I haven't explicitly enabled an higher verbosity level (as far as I know...), I just run Firefox from a terminal sometimes and - aside of this NoScript message - there is quite a lot of output indeed.
Mozilla/5.0 (X11; Linux x86_64; rv:41.0) Gecko/20100101 Firefox/41.0
How come you're running Firefox 41.x instead of the latest release (Firefox 42.0)?
What NoScript version are you running?
I will take a look into this but right now I'm thinking it's likely related to another extension. (I don't see it in my Terminal running SeaMonkey FWIW.)
EDIT
Well that was a lot quicker than I thought it'd be. So it looks like this message is coming from chrome://noscript/content/WinScript.js and happens when NoScript tries to block scripts on a "system global". I'm not sure what a "global" is nor what the message actually means though.
*Always* check the changelogs BEFORE updating that important software!
I should also add that when I saw this message I was experimenting with the Policeman addon, maybe having both enabled isn't a good idea as they could conflict?
It could be some interaction between the two addons but I don't think something this minor counts as a "conflict". As a test disable Policeman and see if it persists?
Also what's the deal with that weird UA string you have there?
*Always* check the changelogs BEFORE updating that important software!
It just means some page, either from the browser internals or another add-ons, is shown in a content viewer but has browser privileges and therefore cannot be blocked.
