Page 1 of 1

some clickable elements breaking w/ FF 16.0.1 + 2.5.8

Posted: Sun Oct 21, 2012 2:15 pm
by moe
Hi, longtime user, thanks for your fine product. This is the first time in 6 years I've encountered an issue which I could not resolve by adjusting settings. This issue is since upgrading to Firefox 16.0.1. Tested with v 2.5.8 and v 2.5.9rc2 with no change.

NoScript is breaking functionality of certain clickable elements on certain pages. I've gone through several troubleshooting steps and am sure it's been isolated to NoScript. When I launch with all extensions disabled, no issue. As soon as I enable NoScript the issue begins with no other extensions enabled. I've tried resetting to stock NoScript setting (wiping my whitelist, reallowing the "bn" domains, any any other settings). This can be duplicated on Barnes and Noble website on any book page, there are marketplace links in the middle which expand content - new, used, all. NoScript is breaking these links. Here's a random page to recreate...

http://www.barnesandnoble.com/w/bring-u ... 1108185320

Thanks for any help you can provide.

Re: some clickable elements breaking w/ FF 16.0.1 + 2.5.8

Posted: Sun Oct 21, 2012 7:12 pm
by Giorgio Maone
For that feature to work you need at least the following script sources to be allowed:

barnesandnoble.com
imagesbn.com
google.com
coremetrics.com
scorecardresearch.com

Re: some clickable elements breaking w/ FF 16.0.1 + 2.5.8

Posted: Sun Oct 21, 2012 9:01 pm
by moe
Thank you for reply, but still no luck. I do have those sites whitelisted. The issue persists when set to Allow Scripts Globally too...

Re: some clickable elements breaking w/ FF 16.0.1 + 2.5.8

Posted: Sun Oct 21, 2012 9:40 pm
by Giorgio Maone
moe wrote:Thank you for reply, but still no luck. I do have those sites whitelisted. The issue persists when set to Allow Scripts Globally too...
Does it happen on a clean profile with a fresh NoScript installation (and the permissions above)?

Re: some clickable elements breaking w/ FF 16.0.1 + 2.5.8

Posted: Mon Oct 22, 2012 12:39 pm
by moe
I have come to the same conclusion, the profile must have some issues. I have this working on another PC/profile with no issues. Thanks for your help!