InformAction Forums

I want to allow a particular domain to run its site-supporting ads & scripts, but deny scripts from these advertisements globally...disallowing scripts from these sites on other domains.

I know very little about clickjacking/clearclick...I hit the "More Info" button and read through the section it sent me to: http://noscript.net/faq#clearclick but it didn't quite clarify what I'm trying to do, though it did raise some doubts about whether what I'm trying to do is useful or a reasonable idea to support some of the websites I frequent.

Here's an example from the domain in question:


Uploaded with ImageShack.us

And here's the full content of the box, obtained by clicking on the url below the content box:
http://a1.interclick.com/AgControl.AgControl
http://a1.interclick.com/1.0.30226.2
http://a1.interclick.com/2.0.30226.2
http://a1.interclick.com/
http://a1.interclick.com/text/javascript
http://a1.interclick.com/getInPageJSPro ... 3437649756

Looking for help either doing this or some healthy advice about why this is a bad idea.

Thanks in advance!:D

The ClearClick warning you're getting is a side effect of those advertisement frames containing lots of hidden links.
You can probably work around by setting the noscript.jsredirectIgnore about:config preference to true.

Also posted this in another ClearClick thread started January 07 2011, with the same question.

I appreciate the reply, with information about the code setting, but could you please give us the answer in terms of the dialog box choices provided by NoScript/ClearClick?

The original question provided an image of the ClearClick dialog box, with two options. Neither one is clear in terms of what it causes - will ClearClick be globally disabled? What does "locking" or "unlocking" "this element" mean, functionally?

I think ClearClick is neat, and I thank you for it. But, as reflected in clearly-stated and well-documented questions, at least since early December 2010, the user interface in the dialog box should be put into user language, not program-centric jargon. (In this case, that is, "Keep this element locked" and "ClearClick protection on pages untrusted/trusted": what the heck do those mean in terms of the specific detection?). Kind of the ancient issue with software, and it's hard to understand why it exists here. What's the point of a browser-based GUI, when the options are framed in the language of the program functions and the programmer, not the user? You undermine the point of the code, if you don't fix the GUI.

Please, guys, help us with the GUI - it's not helpful to tell us to change code settings when we're all using a browser-based application with user interface.

Long-term fix, please change language in the GUI dialog box, from jargon to user-focused. In the meantime, could you tell us how to use the two options provided in the current ClearClick detection dialog box (an image of which was provided in the original question) so we can Allow that specific detected alteration, while keeping ClearClick Enabled for other detections? This question has persisted for over two months, without an answer. It's a great function, please help us use it.

Thanks in advance for your answers.