InformAction Forums

The new Report ID is 1682292.

My noscript.clearclick.subexceptions looks like this:

Status: Default
Type: string
Value: Also the Error Console show this: and
Thanks.

Please check rc7

You have done the job solid this time round. No more warnings. Excellent!

Thank you very much indeed for your effort to keep NoScript THE top add-on for a hassle free browsing experience.

Best wishes!

Markus387

p.s.

Can I buy you are coffee some time?

Hello Giorgio,

unfortunately the Potential Clickjacking / UI Redressing Attempt warning started popping up again using the bit.ly sidebar. For example using the bit.ly sidebar on this forum post I get the Report ID: 1803894.

Thanks for your help.

Dear Giorgio,

sorry I was not using the latest build from here: http://noscript.net/getit#devel now that I updated it works fine again.

Thanks.

Dear Giorgio,

unfortunately the Potential Clickjacking / UI Redressing Attempt warning started popping up again using the bit.ly sidebar. For example using the bit.ly sidebar on this forum post I get the Report ID: 1821331. The strange thing is that for a time it did work just fine, but suddenly it did start showing the Clickjacking / UI Redressing Attempt warning again without me changing anything of the Firefox configuration or system configuration at all. I also made sure to use the latest development build: v 2.1.2.3rc3.

If you can look into this, that would be highly appreciated. Thanks for your help and all the best!

Markus

Not just with bit.ly but I have seen and been experiencing a HUGE increase in false positives on sites that I use daily and just about NEVER had issues before. Unfortunately as sensitivity and logic is adjusted for it, it tends to expand in certain areas and cause those warnings. He can try and fix it for all of eternity but there will always be some form of false positive. If you look at the changelog, he has been tweaking it for quite a while now and although he is great about continuing to fix things, it will come a time where you have to just exempt it if you KNOW its safe or accept that some false positives will happen. The problem is that many of the addons, or tools that either process the content, change it, inject into it, so on and so forth will cause slight interface/layout changes that will cause that to happen which would not if the other interfering factors wasn't there. However, there is no way to account for all of that, there just isn't, hell even using NS to disable JS on a page could cause this to happen because the layout gets all screwy. Not to mention all sites like Facebook and etc, who pop up these shadowed full screen popups that are supposed to improve usability actually cause the warning because part of them will cast over the part you are interacting with and voila, error pops up.

Trivially, they just changed their domain from bit.ly to bitly.com, so the noscript.clearClick.subexceptions about:config preference should be adjusted to (bit\.ly => bitly\.com)

Interesting, the whole point was for them to "shorten" the url, this actually lengthens it. I wonder why they did that? No matter, I never used them anyway but thanks for the update for those who do.