ancestry.com, jquery.com, need to uninstall noscript
Posted: Wed Oct 08, 2014 10:24 am
Hello
I have to uninstall noscript to view image content of the ancestry.com.au website.
No problems previously, I just restarted computer after many months with no restart, and firefox updated & presumably noscript also. So I have no idea what my old version of firefox or noscript was! Current version of firefox 32.03, version of noscript 2.6.9.
Have been using noscript with the ancestry site for a number of years with no problems. To view graphic (images) content normally have to enable jquery.com when first visit the graphic page (enable many other ancestry.com sites before reaching the graphic content) .
Have tried enabling whole page, does not work, enable global, does not work, disable noscript, does not work, restart with noscript disabled, does not work, uninstall noscript, works, reinstall noscript, still does not work.
Suggest this is worrisome as disabling does not fix it. Any ideas on a workaround before a fix?
After writing above re-searched board for jquery.com & saw reports of a driveby problem on the jquery site. Is this related perchance?
Thanks for your time
Glenn
I have to uninstall noscript to view image content of the ancestry.com.au website.
No problems previously, I just restarted computer after many months with no restart, and firefox updated & presumably noscript also. So I have no idea what my old version of firefox or noscript was! Current version of firefox 32.03, version of noscript 2.6.9.
Have been using noscript with the ancestry site for a number of years with no problems. To view graphic (images) content normally have to enable jquery.com when first visit the graphic page (enable many other ancestry.com sites before reaching the graphic content) .
Have tried enabling whole page, does not work, enable global, does not work, disable noscript, does not work, restart with noscript disabled, does not work, uninstall noscript, works, reinstall noscript, still does not work.
Suggest this is worrisome as disabling does not fix it. Any ideas on a workaround before a fix?
After writing above re-searched board for jquery.com & saw reports of a driveby problem on the jquery site. Is this related perchance?
Thanks for your time
Glenn