Search found 11 matches
- Tue Sep 02, 2014 3:11 am
- Forum: NoScript Support
- Topic: 2.6.8.39 has stopped allowing top-level sites by default
- Replies: 13
- Views: 3839
Re: 2.6.8.39 has stopped allowing top-level sites by default
ABE is way more complicated than I care to get involved with. When you talk about trusting or not trusting 3rd party scripts, who knows whether you can trust any of them or not anyway? When you look at the list of scripts that are being blocked, you could spend the rest of your life trying to figure...
- Mon Sep 01, 2014 10:55 pm
- Forum: NoScript Support
- Topic: 2.6.8.39 has stopped allowing top-level sites by default
- Replies: 13
- Views: 3839
Re: 2.6.8.39 has stopped allowing top-level sites by default
I was thinking along the lines of an additional option that would allow a person to cascade permanent permissions if they wanted to. If it was enable it would cascade permanent permissions only. It could be enabled or disabled however the user wanted. I've got a few sites permanently whitelisted, an...
- Mon Sep 01, 2014 5:28 pm
- Forum: NoScript Support
- Topic: 2.6.8.39 has stopped allowing top-level sites by default
- Replies: 13
- Views: 3839
Re: 2.6.8.39 has stopped allowing top-level sites by default
Wait, I take it back. It does cascade even the temporarily allowed ones so it's basically like allowing globally. Sorry to waste everyone's time.
A feature so it only cascades the whitelisted ones you enter manually and allow would be a good idea, no?
A feature so it only cascades the whitelisted ones you enter manually and allow would be a good idea, no?

- Mon Sep 01, 2014 4:44 pm
- Forum: NoScript Support
- Topic: 2.6.8.39 has stopped allowing top-level sites by default
- Replies: 13
- Views: 3839
Re: 2.6.8.39 has stopped allowing top-level sites by default
Does it have to be either or? The way it was previously was safe and not like allow globally. With "cascade" enabled it didn't cascade the temporarily allowed ones, just the whitelisted ones. I only have a few whitelisted ones that are allowed globablly while the rest are partially blocked.
- Mon Sep 01, 2014 3:41 am
- Forum: NoScript Support
- Topic: 2.6.8.39 has stopped allowing top-level sites by default
- Replies: 13
- Views: 3839
Re: 2.6.8.39 has stopped allowing top-level sites by default
I found what's causing it. It's "Cascade top document's permissions to 3rd party scripts." If it's checked, the top-level sites aren't temporarily allowed by default. I normally have it enabled and it's never caused a problem before now. If I uncheck it, top-level sites are again allowed. ...
- Mon Sep 01, 2014 12:48 am
- Forum: NoScript Support
- Topic: 2.6.8.39 has stopped allowing top-level sites by default
- Replies: 13
- Views: 3839
Re: 2.6.8.39 has stopped allowing top-level sites by default
Okay, I tried the developmental build on a clean profile and here's what happens. For example, if I open the main forum page, https://forums.informaction.com/viewforum.php?f=3, the first time it loads NoScript doesn't allow it. If I refresh the page, then it does. Once I've refreshed the page, then ...
- Sun Aug 31, 2014 9:04 pm
- Forum: NoScript Support
- Topic: 2.6.8.39 has stopped allowing top-level sites by default
- Replies: 13
- Views: 3839
2.6.8.39 has stopped allowing top-level sites by default
NoScript 2.6.8.39 has stopped allowing top-level sites by default. I was using 2.6.8.36, and when I updated to 2.6.8.39 I noticed the issue. Reverted back to 2.6.8.36 and it was okay again. It does it on XP and Vista with Firefox 31. I tried resetting the Options and configuring again but it didn't ...
- Wed Jan 18, 2012 12:29 am
- Forum: NoScript Support
- Topic: [RESOLVED] Can wildcards be used in about:config .untrusted?
- Replies: 2
- Views: 1135
Re: Can wildcards be used in about:config noscript.untrusted
Excellent, thank you very much.
- Tue Jan 17, 2012 9:05 pm
- Forum: NoScript Support
- Topic: [RESOLVED] Can wildcards be used in about:config .untrusted?
- Replies: 2
- Views: 1135
[RESOLVED] Can wildcards be used in about:config .untrusted?
Hey all. My question is about the noscript.untrusted string in about:config. Is it possible to use wildcards to block anything and everything from certain people. For example, if I wanted to block everything from "Annoyingsite" how would I write it? *annoyingsite*.* Would that work? Thanks...
- Mon Nov 14, 2011 3:57 pm
- Forum: NoScript Support
- Topic: [RESOLVED] New NS object on links from Google search results
- Replies: 3
- Views: 1520
Re: New NS object when opening links from Google search resu
The latest build seems to have resolved this issue. Excellent work Giorgio!
- Tue Nov 08, 2011 9:56 pm
- Forum: NoScript Support
- Topic: [RESOLVED] New NS object on links from Google search results
- Replies: 3
- Views: 1520
[RESOLVED] New NS object on links from Google search results
I recently started seeing something I never saw before when I click links in a Google search results page. I was wondering if anyone else has noticed this. See attachment. The tab outlined in red is the Google results page. The open tab is what I see when I click one of the links. I've got two compu...