I really liked this extension but the latest update has ruined it. The new UI is very unintuitive and difficult to use. I struggled to get permissions to apply on a website; it kept resetting every time I closed the NoScript settings. Also, I was in those settings because NoScript now has broken most of my RSS feeds on Firefox. I do not know why or how but the only way I seem to get all my RSS feeds working is by disabling NoScript.

The update contains the features missing from the initial release. I'm also starting to get used to the new interface. Thanks for this awesome add-on!

I understand it can be difficult to migrate to a new framework, which is why I am slightly sympathetic. However, the people have spoken. The new UI is garbage, and much of the functionality has been altered in a negative way since the Web Extensions framework updates. I'll go back to 5 stars pending UI and usage fixes! In spite of all this, thank you for the work you've done on the extension.

I like new interface and access to custom permission for current website with just few clicks.

I put 4 stars to encourage the developer, but I don't understand how it works. I can't find the options with the whitelist, the embeddings and the appearance. I don't even understand how to temporary allow some scripts in one click like before. I downgrade in Firefox 56 and I'll wait for a better version.

It's not as good as the original YET, but at least he put something out there so we're not browsing totally naked.
Interface not as friendly, block scripts well, but hard to fine tune like before.
A good start.

So thanks Giorgio and please keep working on that better version we all really want. Don't make us wait too long.

Why did you change a simple UI to this "new" style. You already had the issue with late support for the new firefox, and then you came across with this ugly and popups spamming addon ? Umatrix welcome

Das ist die Beste!!!

There is a bug related to XSS blocking in recent updates:
Opening new tabs from Firfox's blank page is extremely slow and showing a dialog "XSS attack from [...] to ".

Please fix.

Works ok, new UI not as good.

Nice new interface but very confusing. You gonna get a lot of complains about it.

Thanks for bringing the temporary allow all & revoke options. Please continue going and make the WE version as good and power as the normal version.
One question - Clicking the default option show that scripts are marked for sites to load, only objects are unmarked. Is this an UI error?

a must have extension if you care about privacy and security.
Requires some familiarity with the concept of javascript

Updating my review, now it's works under private tab. UI still needs some work but now it is more clear.

Old NoScript come back! :-(

Firstly let me say that I am a long time user of NoScript and I have sent monetary contributions to the developer at least once, possibly more often. It is a *free* addon that obviously takes many hours of work to maintain. The developer should be given thanks and respect for doing that voluntarily. No self-respecting developer sets out to make mistakes or produce something that users don't want.

So something has gone badly wrong with this release. There are two aspects to it that I can see: the script blocking operation, and the UI. Some sites that I visited no longer work with NoScript enabled, even if you allow everything. Amazon music (play sample) didn't work for me, just one example. So that needs sorting out.

As for the UI, I initially found it complicated and confusing but I am getting used to it now. What happened to the middle-click functionality?

But until the developer has managed to fix the functionality, I have to disable it. I may just end up using the Brave browser until it is fixed.

Oh, and I would like a way to save my Whitelist so that I don't lose it if I uninstall and reinstall.

Wow, what went wrong? Mozilla is fucking with everything!!!

Most of what is happening now you should blame on Mozilla, though I have to admit there are several things I don't get with NS' new interface.

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.