InformAction Forums

The filtration against canned pork meat (can't use real words for fear of setting it off) is blocking all attempts to post on your forums. I can't tell why. I need to report problems with the new version of noscript and can't even use this site from FF with the new noscript in it.

The filtration in question is against Superunwelcome Painful Annoying Matter, if the verbal description didn't say it well enough.

Now to try to find another way to say the things I really need to post here:

Moderators, if you can get to this without tripping the filtration please put it into the new interface thread.

The main tools of noscript are all gone in version 10.

I cannot find "temporarily allow" for any domains.

"revoke temporary permissions" is missing.

"tempoarily allow all this page"?

Application Boundary Enforcement, where are the options?

cross site scripting prevention, where are the choices?

NoScript 5 had atleast 5 menus worth of tickable options, 10 has only a single webpage of which sites to permanently allow or block.

furthermore:

I can't allow specific objects, so am being forced to type this from a program which rhymes with dome, the new noscript won't let me allow the computer automated alan turing test object, I can't see anywhere to click to let it run.

I don't want to have to tinker around with many settings for every website and domain about whether it may run script, object, media... I just want to be able to disable and enable scripts and objects per page I visit by clicking on the objects or going to scripts in the bottom bar menu (also gone). And how do I get back that warning sound that goes off when scripts are getting blocked, others may hate it and leave it off but I found it a helpful reminder that noscript was working.

I apologise for breaking over many posts like this but the thing to stop meat that comes in cans from being deposited all over this forum didn't like my full post at once, perhaps an admin of this site may know how to clean up my post into one thing which won't break.

I continue:

I understand NoScript 10 is still a work in progress, will we be getting back the dozens of options and tick boxes we are used to? I feel that a product so great as NoScript should work on it's strengths as it is and not try to change itself for a new audience, but to stick with the way of operating that it has taught us up to now. Please dob't let this be a case of choosing appearance over functionality, i can see that version 10 looks elegant but I can't find how to work it, frankly all the options (cog??) are too small (bad for poorly sighted or small screens) and it seems designed to work in terms of what to allow from which domains in an almost global sense, rather than the old way of letting you pick things centred around what page you were on right now.

And I know on noscript 5 you could choose to hide or show the locations of blocked i-frames and plugin boxes, but on noscript 10 I don't know how to show them when they need enabling.

In the final part of my post string, sorry, problems with the preventer of canned meat I say also:

Yet despite losing most of the options I knew and loved I find that "allow scripts globally" still remains, I can see why some people may want it but surely something so dangerous should be the last priority of tools to translate over to the new web extensions API. What has happened to the tools I really need, the ones I've grown so used to, or am I too dumb to find them in the new interface?

Giorgio, I really appreciate the work you've done with NoScript, I recommend it to everyone I know and swear by it absolutely. But this new interface is really confusing, and I think lots of the important things are hidden in tiny buttons and under buttons with graphical labels but no text explanation. Could the old interface be recreated, it seemed perfect to me? Are tutorials for the new one available, it's a lot to learn, though I worry the new interface won't match the granularity and control the old one gave.

It's such a shame that the company which rhymes with the title character in what was originally a japanese monster movie, for all I know company names may set off the canned meat stopper, had to force out the new standard for firefox extensions and do so without a good long period of a decided standard for the new API and without realising how many FF users choose FF solely for NoScript.

- The old GUI is unfortunately just not possible, therefore Giorgio is starting from scratch.

- Several important functions (eg ABE) are just not done yet, and will likely take precedence over most GUI aspects.

OK, thanks for those clarifications. I know the old method of GUI, the pop up sub window stuff isn't do-able in quantum but is the whole principle of having all those options now gone too? I just thought it would be possible to redo them all but on that tab webpage style control interface for quantum options as opposed to the old sub window pop up interface.

Is clicking on blocked objects no longer possible, the way that NoScript 5 can block videos but you click the NoScript icon which is plastered over them, click ok on the dialog and then proceed? Even if the dialog box bit is no longer possible in FF57.

And can the new quantum engine not handle text labelled buttons, like the way NoScript used to have buttons on all it's labels "Options" "about noscript 5.1.7..." "temporarily allow example.com" "forbid examples.com"... The new icons only method seems really confusing to me, and the clock and cog are far too hard to distinguish.

I really appreciate Giorgio's work, I don't feel safe browsing without it, but I wish the interface could stick with what we all recognise, I guess that might have been more possible if mozzila had finalised it's quantum engine API earlier before 57's release so that Giorgio would have had more time to start converting noscript before the converted version needed releasing.