Search found 16 matches
- Fri Sep 01, 2017 8:43 am
- Forum: NoScript Support
- Topic: "Temporarily allow", then revoke - and then site still works
- Replies: 4
- Views: 2076
Re: "Temporarily allow", then revoke - and then site still w
salon.com is in my whitelist. I did assume they were confusing noscript with an ad blocker. The behavior I'm seeing is definitely weird. Some kind of timing glitch. I left my browser running, left the computer for a couple of hours, came back and salon.com again won't load. Temporarily allowed all; ...
- Fri Sep 01, 2017 3:08 am
- Forum: NoScript Support
- Topic: "Temporarily allow", then revoke - and then site still works
- Replies: 4
- Views: 2076
Re: "Temporarily allow", then revoke - and then site still w
Ooops! I must have deleted a line, as I thought I had included a URL. Sorry! One site is http://www.salon.com I was away for most of the day and just found it reverted back to blocked condition... So I once again allowed all temporarily; the page refreshed and all was fine. Then I revoked temporary ...
- Thu Aug 31, 2017 12:17 pm
- Forum: NoScript Support
- Topic: "Temporarily allow", then revoke - and then site still works
- Replies: 4
- Views: 2076
"Temporarily allow", then revoke - and then site still works
Similar things have happened at a few sites, with slightly different symptoms. They may warn they detect an ad blocker, but allow me to dismiss the warning and continue. Or the site may put up a page that says something, probably an ad blocker, is preventing the site from operating. I disable Add Bl...
- Fri Nov 25, 2016 7:21 am
- Forum: NoScript Support
- Topic: Noscript blocking Dashlane extension Firefox 50
- Replies: 33
- Views: 18588
Re: Noscript blocking Dashlane extension Firefox 50
I don't think all that testing is necessary based on the timeline I posted previously, but I did it anyway. I just downgraded NoScript to 2.9.0.14 on FF 50 for Windows, and removed the new ABE rule. Dashlane works perfectly. The only ABE notice in the console is [ABE WAN] Detected WAN IP <my public ...
- Thu Nov 24, 2016 8:23 pm
- Forum: NoScript Support
- Topic: Noscript blocking Dashlane extension Firefox 50
- Replies: 33
- Views: 18588
Re: Noscript blocking Dashlane extension Firefox 50
Pardon my intrusion - turns out I'm registered here. Posting this so I'll get notified when thread is updated. Thanks.
- Thu Nov 24, 2016 8:13 pm
- Forum: NoScript Support
- Topic: Noscript blocking Dashlane extension Firefox 50
- Replies: 33
- Views: 18588
Re: Noscript blocking Dashlane extension Firefox 50
Oops, my bad. This should work better - Site 127.0.0.1 localhost Accept GET from about:blank 127.0.0.1 localhost Yes! Errors gone, and extension initializes quickly. Will there be a fix to NoScript making this change unnecessary? I'm guessing it would be a fix to how the default system LOCAL rule i...
- Thu Nov 24, 2016 6:03 pm
- Forum: NoScript Support
- Topic: Noscript blocking Dashlane extension Firefox 50
- Replies: 33
- Views: 18588
Re: Noscript blocking Dashlane extension Firefox 50
Your suggestion Site 127.0.0.1 localhost Accept GET from about:blank Does work, but there is a 10-15 second pause before Dashlane starts working. (It is gray till ready; then it turns green.) The console shows this: Could not read chrome manifest 'file:///C:/Program%20Files/Mozilla%20Firefox/chrome....
- Thu Nov 24, 2016 12:26 pm
- Forum: NoScript Support
- Topic: Noscript blocking Dashlane extension Firefox 50
- Replies: 33
- Views: 18588
Re: Noscript blocking Dashlane extension Firefox 50
Putting this into ABE options, as suggested, solves it for me too: Site 127.0.0.1 Accept GET The existing rule allows any behavior from local, and denies everything else. This rule apparently allows any GET operation from anywhere to succeed, regardless of source - which seems like it might break a ...
- Thu Nov 24, 2016 6:03 am
- Forum: NoScript Support
- Topic: Noscript blocking Dashlane extension Firefox 50
- Replies: 33
- Views: 18588
Re: Noscript blocking Dashlane extension Firefox 50
Sorry for the typo. Where I wrote:
I meant FF 50.I've been ignoring the FF notifications to update to FF 40 the last couple of days.
- Thu Nov 24, 2016 5:50 am
- Forum: NoScript Support
- Topic: Noscript blocking Dashlane extension Firefox 50
- Replies: 33
- Views: 18588
Re: Noscript blocking Dashlane extension Firefox 50
This was happening before FF 50 for Windows. The problem started, actually - this morning, when I was still on prior version of FF. I've been ignoring the FF notifications to update to FF 40 the last couple of days. So Dashlane stopped working - and, actually, to try to FIX this, I updated to FF 50,...
- Wed Aug 12, 2015 3:36 pm
- Forum: NoScript Support
- Topic: [FIXED] Firefox/POCKET problem
- Replies: 10
- Views: 7040
Fixed Re: Firefox/POCKET problem
Fixed in V. 2.6.9.35. Thank you.
- Sun Aug 09, 2015 10:20 pm
- Forum: NoScript Support
- Topic: [FIXED] Firefox/POCKET problem
- Replies: 10
- Views: 7040
Re: Firefox/POCKET problem
Every bit helps. Thanks!
- Sun Aug 09, 2015 7:34 pm
- Forum: NoScript Support
- Topic: [FIXED] Firefox/POCKET problem
- Replies: 10
- Views: 7040
Re: Firefox/POCKET problem
Meant to login to this thread. This reply posted by logged in user.
- Sun Aug 09, 2015 7:29 pm
- Forum: NoScript Support
- Topic: [FIXED] Firefox/POCKET problem
- Replies: 10
- Views: 7040
[FIXED] Firefox/POCKET problem
Running NoScript 2.6.9.34. Firefox 39.0.3 I think I've read the other threads on Pocket problems. about:pocket-signup and about:pocket-saved were in about:config / noscript-default about:pocket-signup was in the NoScript Options whitelist I added about:pocket-saved manually to the whitelist The Pock...
- Thu Feb 07, 2013 10:16 pm
- Forum: NoScript Support
- Topic: XSS error with some links in nytimes.com newsletters
- Replies: 2
- Views: 1585
Re: XSS error with some links in nytimes.com newsletters
That worked. I had tried something like that, but apparently I got the regexp wrong .
Thanks for your quick help!
Thanks for your quick help!