FF57 is a big challenge. Don't be disappointed. Being a father 24/7 is more important.

Last update has broken NoScript. Completely trusted sites still have blocked items which disable the visited sites.

Review for noscript 10.1.3c1
After fiddling with noscript for a while, I see that noscipt is working for me , and I am beginning to like the new UI, but there are some issues with unexpected behavior.

For instance, if I create a rule to allow an insecure connection to wired.com, and then reload the page, my selection will seem to disappear (or revert), but in reality my selection is not shown because there is no insecure connection to wired.com so the site remains blocked. It is unexpected to see the rule disappear and block the page and might cause people to think it doesn't work. I also assumed that my insecure rule would automatically allow a secure connection. EDIT: This problem has been fixed with a recent update. Thanks

Also a smaller issue is globally allowing scripts only shows top level domain allowed, instead of showing all allowed domains, similar to how "temporary allow all this page" shows all domains.

Overall I think Giorgio has done good work so far at rewriting noscript, but I think it needs a little more polishing.

Big thanks to the developer for the hard work on this excellent add-on, the new UI is definitely getting there. Keep up the good work, ignore the naysayers - some people need to remember that change is the only constant.

Well, obviously the security aspect of the new version is good, but I gotta say that it seems hard (and uncertain) on how to do a TEMPORARILY ALLOW DOMAIN in the new version. The TEMPORARILY ALLOW is what I use almost exclusively (when needed) to deal with things I don't want to grant permanent permission to. (Yes, I know you know this).

I just find it too hard to get to it. It took me a while to realize the teeny-tiny watch-face symbol was used for that, but even more unclear was that I actually had to click on the clock itself. Can you make the TEMPORARY feature easier to recognize and access?

Frank

For now, down to 4 stars, instead of the usual 5

Good add-on, a must have.
One star missing cause of the new context menu UI, the previous one was better.
I like this new settings depth.

Thank you for all the work you put into your excellent add on.

Thank you for your continued development efforts. I hope you can return NoScript to it's former glory, despite the massive changes forced upon us all by Mozilla. I do miss the old interface, especially the simple "Temporarily Allow All Scripts" button.

Appreciate the work to update this for Quantum. Working well most of the time but seems to have issues with piecemeal enabled scripts for a site with inter-dependencies. ESPN is good example.

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.

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?

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

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.

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.

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.

the android version don't block anything on FF57 and the UI on the desktop has ugly scrollbars here

The old version was amazing, truly a power user's addon. The new version... well I understand that you had to rush a complete redesign and rewrite... but it's too bad that it lost a lot of functionality. On the up-side, I do like the new interface.

In particular I'd like to point out that the addon does not work in Private Browsing mode. Would it be possible to add back the Temporary Permissions feature and allow people to "Temporarily Allow" URL's for the duration of Private Browsing sessions?

Actually a 5*, it might be language related but in germany the translations are way to long for the new interface (Words don't fit in the reserved space).
Sadly it looks really bad.
For the other stuff I like the uMatrix like way to control what gets loaded.
Also, even thought I need to look how it works somewhere, that we got some https contol looks promising.