View blocked Scripts?

[efkah]

Hello to all of you.

Just started to use Noscript (on FF) and i have 2 Questions:

a.) Is it possible to view the blocked scripts directly in Noscript or do i have to use Firebug?
b.) Is it possible to selectivly enable/disable Scripts (if there are multiple script tags, i inspect that only one is evil and still want to surf the NOT barrier-free version of the site?) or do i have to greasemonkey something for that?

Thanks in Advance,
efkah

PS: We use "Barrier-free websites" in germany for websites that are able to work without js etc. and older browsers.

[Thrawn]

a.) Is it possible to view the blocked scripts directly in Noscript or do i have to use Firebug?

Firebug, or JSView, or you can view Page Source and trace it from there...no, NoScript doesn't do this. But there are plenty of other tools that work very well.

b.) Is it possible to selectivly enable/disable Scripts (if there are multiple script tags, i inspect that only one is evil and still want to surf the NOT barrier-free version of the site?) or do i have to greasemonkey something for that?

When you say "evil", do you mean evil as in tracking/advertisements, or do you mean evil as in "going to exploit a buffer overflow and take over my machine"?

If you're talking about a tracker or advertiser, then you might be able to use NoScript's surrogate script feature for this, if you know JavaScript (which I presume you do, since you suggested Greasemonkey). You use it by leaving the site blocked, but providing a surrogate that will simulate the usual script behavior just enough to get the page working. You can search for 'surrogate' in about:config to see examples.
If you're talking about a site trying to attack you, then I suggest you don't try to use it, just turn tail and run.

[efkah]

well, i wished for something like ABPs "show blocked elements -> deactivate feature", but what you got seems pretty awesome, too.

So i was taking a look at how you deactivate the tracking on the google-hits.
the glinks.sources is a regex to filter the urls where to activate the script, the glinks.replacement is the script which will be run?

seems fine, but what about this whitelist and block thingy?
you said that i can leave the site blocked. The script seems to run on google.com but not on google.de!
If i allow scripts on google.de it runs there, too.

Also i kinda get the idea that it does exactly the same as greasemonkey;-)

Kind Regards,
efkah

[efkah]

edit: compare
https://www.google.de/search?hl=de&q=asdf
https://www.google.com/search?hl=de&q=asdf

[Thrawn]

Surrogate scripts are similar to Greasemonkey, yes. They're meant to be used when you want to block a site, like Google Analytics, but poorly-designed websites break without it, so you write something to fix the break.

However, if you want to block Google link tracking, you could just block google.com?

[efkah]

The example should just state that it doesnt seem to work as intended, you can't use scripts on blocked sites.
either that or (which seems more probable thinking about it) i am using it wrong;-)

[Thrawn]

You may wish to read the Script Surrogate Quick Reference.

[efkah]

probably i should;-)
thanks for you help, much appriciated.

[Itadakimasu]

well, i wished for something like ABPs "show blocked elements -> deactivate feature"

I love ABP's interface for this. The deactivate feature is neat, but the show blocked elements itself is something I've hoped to see in NoScript for a long time.

It would be pretty cool to have a ABP like panel open up at the bottom of the page, and under main categories which would be domains, there would be all the elements that NoScript cares about listed per sub-domain and type. (JS, Fonts, plugin applets, even stuff such as IFrames maybe) (JS inlined in the main page could be listed as "Inlined" or not at all)

Being able to temporarily allow one specific element would then naturally follow, although it probably implies adding a whole subsystem to NoScript because NS doesn't work like that. Still, just having elements listed individually in a nice UI would be interesting. It would give a better overall picture of the website so we can decide what to domains and subdomains to whitelist with better insight.


Has such a feature a chance to be implemented in the future ?

[Thrawn]

Has such a feature a chance to be implemented in the future ?

Probably not. Why not just use ABP?

[Itadakimasu]

It doesn't help in figuring out the minimum I should allow to get certain features to work on a site, such as comments, some video or whatever. It's kind of a guess work and can be tedious. Improving that area through a visual representation would make NoScript more user friendly without compromising security.

ABP-like panel is just an example, I'm sure there are cooler representations, like (for web dev) how Firefox's Inspector [CTRL+SHIFT+I] allows to modify page layout very easily by showing exactly what needs to be changed. You visually click on an element and you've code both appropriate HTML and CSS under the eyes for you to tweak in seconds. No need to dig in source code, find the correct CSS external, etc.

If NoScript had *something* to smoothen the guessing process, it would both reduce tediousness and look powerful, which is good for product image.

But it's a whole lot of work, so I guess won't happen.

[Itadakimasu]

Whoops, I used the wrong word in second paragraph. Fixing it up

You visually click on an element and you GET both appropriate HTML and CSS under the eyes for you to tweak in seconds.