Rated 3 out of 5 stars
And you go overboard when you say that it was dangerous when you so often temporarily allowed scripts on whole site - well, I still say that mostly even simply keeping scripting on is quite safe - I know NoScript warns that it's dangerous and I can't argue as this is really matter of how we individually define what is danger and levels, etc. of it. What you used anyway was "temporarily allow", this YesScript - a good piece of work most certainly - just turns all on or all off.
So it's either "very dangerous" as you say or no scripts at all - at least with NoScript you can just set the plugin to something you would more likely prefer. NoScript->Options and first leaf, "General" and choose the very first (non-recommended if you are paranoid) option "Temporarily allow top-level sites by default" and of the three options defining what by is the site recognized I chose first: "Full address" - I was just testing, this mode was not for me but this way new sites are by default allowed to run scripts. Naturally if they use, for example, ad-scripts from other server and it has been (with good reason) banned then not all scripts on page naturally work - but you can choose not to ban sites lightly and you can unban them too.
For you NoScript set up like this could be a boosted up YesScript though. Sites allowed by default (but that is not written anywhere: temporarily allowed). Now you can "Revoke temporary permissions" (in noscript menu this is site-specific) and it is like in YesScript turning scripts off. Again select "Temporarily allow all this site" and you have turned scripts on again.
SO HOW IS THIS *BETTER*?
But cross-site scripting is today and there are sites where you might want, you might *need* to block scripts to be able to use the site - yet stopping all scripts altogether will render some of these sites unusable too.
P.S. I am exaggarating but it's not untrue what I have murmured here ;) YesScript is a fine tool but what I wanted was to try prove wrong the bad image your words (I think) were giving to NoScript and point that, used correctly, it can be just as easy as YesScript but with twist for if you suddenly wan't site-specific script-blockings.
I think YesScript *is* great. But if I must compare I would say that YesScript is to NoScript what Lola is to FireBug :o I really think so.
"The worst thing is it would only show part of the web page and sometimes hang on loading others. I only need it to block scripts on a few websites, not the entire Internet. The only thing missing is custom website blacklist, that would make this add-on PERFECT. Thanks."
Or... Was this plugin released under open source license?
YesScript is licensed under GPL3. Patches are welcome.