Thanks! Works for me so far. One thing I found a bit tricky is that if one allows a script from a non-https site but without also allowing non-https from the site by clicking on the padlock, then reloading will show the site as "Default", i.e. most of the time as blocked. So it seems as if the allowing of the site was not remembered by no script. I think it would be better to show the site as allowed as one has chosen before since the padlock will give you the further information that it does only allow non-https.

I have seen lots of people saying that no script does not save allowed sites. So far for me the workaround was always to unlock the padlock as well.

Ottima Estensione fa quello che dice, purchè si capisca come lavora e la si configuri correttamente.

This was a five-star add-on prior! I LOVED it! What happened to the user interface and the options panel with all of its features? This add-on is a mess now.

Bisogna un po' abituarsi alla nuova interfaccia. Come al solito la pazienza degli utenti non e' un gran che "tutto e subito" imparate ad usarlo e controllate se funziona correttamente a me funziona egregiamente e mi sono gia abituato al nuovo look.
A una cosa dato che e' gratuito se non vi comoda cambiate pure componente aggiuntivo credo che Giorgio sopravvivera'.
TNX.

Even as a long time user of NoScript this UI absolutely kills the experience.
I still think there is hope though. Something as little as getting the mouse-over menu activation to work would make it feel not nearly as bad.
The new HTTPS detection is also one of the greatest offenders in breaking website functionality and there isn't even a proper explanation for how or why it works. I had to experiment my way to discovering this.

Why does it suck so hard now? It was a good add-on and one of the reasons I use Firefox. Think i give Opera a chance.
Since 10.1.2 Temporarly button is back; it's getting better again.

Was having a lot of trouble with it at first. The noscript button was working for a bit, then stopped working which may have been due to a FF update as far as I could tell on the noscript site? Restarting the browser fixed that particular issue but other things weren't working.

I removed noscript from the add-ons and then went to https://noscript.net/getit and installed from there and it seems to have fixed a majority of the problems as well as cleaned up the UI a bit. I suggest everyone give that a try as well. Just seems there's still bugs to work out and I'm glad to continue to stick with it.

The extension is still great, but the new UI is absolutely horrible.

Used it for Years.
The new Version doesn't work properly.
UMatrix is an alternative.

Alla fine ho deciso di fare un downgrade alla ultyima versione fi Firefox 56.

Con la v.10 di Noscipt , a parte della complicazione del nuovo menú, molte pagine non caricano correctamente incluso se si permette JavaScript globalmente. Chissa la nuova API non permette il ritorno all'interfaccia calssica?

Spero poter tornare ad usare Nocript prossimamente perche è chiaro che non sarà sicuro continuare con FF 56,02 a lungo.

Grazie comunque per i'ottima estensione che è stata fino a pochi gg fà.

I understood the previous version of NoScript.
I do not understand this version. It is not clear what is going on, or what the icon colours mean. Red versus green seems to be disconnected from permitted and not permitted.
I need documentation. The alternative in the latest version of FireFox is uMatrix, which I have on one machine. It is Very Complicated, but I did find complete documentation for it.
To use NoScript 10.1.1 or later I must have documentation.

3 stars becauze of new Quantum firefox UI, before it it was just perfect, now it is just pure-brainfuck. I will welcome that weed which was smoked while making this nature-fatal-error UI. oh, and TOR still keeps old-fashined perfect UI <3

very unfriendly gui

I am still on FF 56 and generally happy with NoScript. After checking the FF57 status and reading what others wrote I felt compelled to do two things. First, I sent a complaint to Mozilla directly - not just about NoScript, but the whole debacle that the move to webextenions has become. They knew this would happen and let the train wreck continue any way.

Second, I am really disappointed at the vitriol directed at this developer. Most, if not all, of the blame is with Mozilla and that is where you should be directing your anger. Things that could be done pre 57 are no longer either a) allowed or b) possible or c) both.

I don't doubt that he is disappointed and angry too. One of the, if not the, most poplular extensions for years, and now kicked to the curb through little fault of his own. I'm sure he will continue to try to make it better but what is 'better' in 57+ will not ever be the same as the older versions.