InformAction Forums

reporting bug:
doesn't reload page after changing a few permissions (not the whole page).
can't revoke when on a blank page.
revoking permission reload the page i'm on even if it's not affected by the permissions made on another tab.

Ralph wrote:After setting them to trusted, you should switch the green Lock-icon to the red state...

That would be a nice idea, if there even was a lock icon! There isn't!

Worse, sites I have had set to Trusted for ages have suddenly switched to Default.

This version is a disaster.

Ralph wrote:After setting them to trusted, you should switch the green Lock-icon to the red state, because otherwise the trusted is only matched for the https: address, and when the site doesn't have https: in its address, the site will NOT be considered as trusted, and so it switches to Default state. I mentioned this effect also in an other thread ( https://forums.informaction.com/viewtop ... 998#p91998 ), so i hope it will be considered in the next update.

That worked. Thanks

I thought the lock was to tell if the site was safe or not. Or it was set up to mark scripts as unsafe so other people would know.

joe786 wrote:It seems like the red/green lock is just more trouble than it's worth. If you trust a site, you trust a site. Why would https and non-https make a difference?

Because one sends data encrypted, and the other not.
It's basically a method to not accidentally send unencrypted data, when you thought you where on a secure site.

It's less about whether you trust the recipient/sender, but everything between you and them.

No-Script is making my FF unstable after opening just a couple of tabs. For example, having 2 twitch streams open (one in pause), switching between the two makes FF to hang for 10-20 seconds. It does not like multitasking.

I would like to say just by doing clicking on the lock or unlock, respectively makes NoScript "forget" whether it is trusted.

For example, when I navigated to "http://nashvillepublicradio.org", I clicked the trusted for nashvillepublicradio.org, and the unlock button. NoScript remembers the "trusted" site when I reload the page.

However, as soon as I click the lock to "Math HTTPS content only", NoScript immediately doesn't remember that nashvillepublicradio.org is a trusted side.

I, and many others believe that this is a SEVERE breaking change due to the fact that a user has to remember to purposely click on the unlock button for NoScript to remember that XYZ is a trusted site.

Please fix this...

If you are curious, this applies to any new site.

So for the nashvillepublicradio.org example, it looks like the following

https://ibb.co/ej0NiR

dcwan wrote:I would like to say just by doing clicking on the lock or unlock, respectively makes NoScript "forget" whether it is trusted.

For example, when I navigated to "http://nashvillepublicradio.org", I clicked the trusted for nashvillepublicradio.org, and the unlock button. NoScript remembers the "trusted" site when I reload the page.

However, as soon as I click the lock to "Math HTTPS content only", NoScript immediately doesn't remember that nashvillepublicradio.org is a trusted side.

I, and many others believe that this is a SEVERE breaking change due to the fact that a user has to remember to purposely click on the unlock button for NoScript to remember that XYZ is a trusted site.

Please fix this...

That's because if you use the green lock (which doesn't mean lock or unlock, but "https only" and "https and http both" (as their hoverover says))
you allow HTTPS:-//nashville.... which doesn't exist.
Thus when you go to http:-//nashville, NS finds no rule, and applies the default.
The rule for HTTPS:-//nashville does exist, and should they ever upgrade, it would work fine.

Take heed though, do to a bug the same applies for "untrusted" even though it doesn't show the locks, the same logic applies, which means if you want to block the http part you have to set it to trusted, set the red lock, then untrusted and go from there.

Is this auto-reload feature gone for good?

Hey, i get constant pop-ups out of nowhere about cross-something, repeatedly, about some random website. What's the deal with that? happens on two separate computers, Ubuntu and Windows 10, both Firefox 57

clarification - constant pop-ups about "cross-site suspicious requests". it's always from "[] to some website"

zettos wrote:clarification - constant pop-ups about "cross-site suspicious requests". it's always from "[] to some website"

That's the firefox hub page calling your previously visited pages.

The page that opens in a new tab.

My Noscript is too eager: it seems to block every script what ever I do except when I allow them in Default mode. (Or Globally, or turning Noscrip off) Allowing everything temporary does do nothing (when scripts are not Default-allowed). Red http-unlock does not help either.
And this happens on every site. (Or better does not happen: when I click a link (which works NoScript turned off) on any site, nothing happens.)

Pansa wrote:
Take heed though, do to a bug the same applies for "untrusted" even though it doesn't show the locks, the same logic applies, which means if you want to block the http part you have to set it to trusted, set the red lock, then untrusted and go from there.

pansa; thank you for this clarification, because this was my problem - my untrusted settings would not 'stick'. for example, on espn; i would untrust optimizely.com, and then when i would reload i would have two entries for optimizely - one with default and one with the untrusted settings - but neither had a red/green indicator. i didnt know what was going on until i read your quote above. one clarification though, you dont need to set it to trusted, you can simply set to custom, and then the lock option appears in the master list.

i dont care for this new default behavior of allowing scripts by default, so i did as someone said above and changed the default default behavior to allow nothing from a domain and i will add as i please. i do love noscript overall, but the new ui is taking me quite a bit of getting used to and figuring how to do some of the old stuff a new way. keep up the good work.
thanks;

Hello, I'm having a rather bizarre issue I've been unsuccessfully trying to look up for the last hour.

NS simply doesn't work for me. It shows up in Extensions (the only one, I haven't installed others yet) but doesn't have any icons, by default or in Customize. It doesn't seem to do anything either. There are no options relating to it anywhere.
I have no idea what to do, I tried launching FF in safemode, in the vain hope it might fix anything, but it hasn't.

Halp.