Difference in master list and icon list [bug?]

[8-bit]

Quick update (10.1.2) - thanks. Seems to be working pretty smoothly...

Wait....just found another bug when attempting to post this. I marked informaction as trusted, but when I clicked away from the icon menu, it did not reload the page. I had to do a manual refresh (or go back to the icon and click on the green refresh icon.) [bug?]

I go to a site and click on the NS icon to check scripts/block/etc...
Note: both google.com and googlesyndication.com are showing as default:



I have already marked both of these as UNTRUSTED and they are showing as such properly in my **master list**, also there is now a huge space between the site name and the default, trusted, untrusted, & custom options (not a big deal) :



BUGS? - is anyone seeing this? ....Repro? It makes me unsure which one is correct, I would assume the master list is correct, but can't be sure because of conflicting states.

Thanks!
8-bit

[8-bit]

bump...

[barbaz]

I marked informaction as trusted, but when I clicked away from the icon menu, it did not reload the page. I had to do a manual refresh (or go back to the icon and click on the green refresh icon.) [bug?]

Same behavior here FWIW.

I go to a site and click on the NS icon to check scripts/block/etc...
Note: both google.com and googlesyndication.com are showing as default:



I have already marked both of these as UNTRUSTED and they are showing as such properly in my **master list**, also there is now a huge space between the site name and the default, trusted, untrusted, & custom options (not a big deal) :



BUGS? - is anyone seeing this? ....Repro? It makes me unsure which one is correct, I would assume the master list is correct, but can't be sure because of conflicting states.

Quick look didn't show that behavior here. Can you please give more detailed steps to reproduce this?

[8-bit]

Quick look didn't show that behavior here. Can you please give more detailed steps to reproduce this?

STR:
[1] Go to the mater list/preferences page of NS
[2] Set google.com and googlesyndication.com as UNTRUSTED (if you do not have googlesyndication.com already in your prefs/master list, you can add it and mark it as untrusted)
[3] Head over to http://forums.mozillazine.org/viewforum.php?f=38 (Mozillazine Firefox Support Forums) and click on the NS icon in the toolbar - you should see the discrepancy in the set states of the two domains - Masterlist: Untrusted. Clicking on icon: Default.

Can you repro this? Thanks! - try that first.

There is one thing I remember from using the legacy NS - On the Mozillazine site, both google.com and googlesyndication.com are NOT secure connections, whereas when I first set them to Untrusted they were coming from secure connections. I don't think MozZine usses any secure connections for anything on that forum. This may be what is "confusing" NoScript.

[Pansa]

Can confirm.

My suspicion is that this also overlaps with the "https/http" issue of saving changes.
When I tried adding the syndication from default to untrusted, it wouldn't save the change, unless I set it to trusted first and removed the green lock.
Now it's in the ui as well as in the options.

it's also now blocked without the ... in front of it (which is another thing I haven't understood what that means exactly, I assume that the ... means "just the root" and without them "including all subdomains"?

[bo elam]

When I tried adding the syndication from default to untrusted, it wouldn't save the change, unless I set it to trusted first and removed the green lock.
Now it's in the ui as well as in the options.

I can also confirm this behavior. I seen it in a few sites, not many. I am doing same workaround as Pansa.

Bo

[8-bit]

Can confirm.

My suspicion is that this also overlaps with the "https/http" issue of saving changes.
When I tried adding the syndication from default to untrusted, it wouldn't save the change, unless I set it to trusted first and removed the green lock.
Now it's in the ui as well as in the options.

it's also now blocked without the ... in front of it (which is another thing I haven't understood what that means exactly, I assume that the ... means "just the root" and without them "including all subdomains"?

Ah, Thanks! Nice to get a repro to confirm my suspicions.

Yeah, the ... in front of domains I've always understood as just the root, because I have others on my list that have more than one subdomain which do not include the ... in front of them. I think we are right about that.

Thanks for the help. It's nice to know I'm not "seeing things"

[8-bit]

I can also confirm this behavior. I seen it in a few sites, not many. I am doing same workaround as Pansa.Bo

Ok, Thanks for reporting......it helps A LOT

[Some Person]

Can confirm similar behavior. It seems like the problem is that when you set what to allow/trust/untrust through the icon list, it will create an entry for the domain and automatically(?) set it to match https or secured content within NoScript's Options. However, since not every website/webpage uses https or secured content, http or unsecured content will not load. I've tried this with site like ESPN and Mozillazine that do not use https and got the same result.

[barbaz]

STR:
[1] Go to the mater list/preferences page of NS
[2] Set google.com and googlesyndication.com as UNTRUSTED (if you do not have googlesyndication.com already in your prefs/master list, you can add it and mark it as untrusted)
[3] Head over to http://forums.mozillazine.org/viewforum.php?f=38

Ah, that would explain it. I can reproduce it with those steps.

Pansa is right. What you are Marking as Untrusted is "https://[...]google.com" and "https://[...]googlesyndication.com". That doesn't include the plain HTTP versions of those sites.

You would need to click the green lock to turn it into a red unlock, so that you mark the plain HTTP versions of those sites Untrusted.

Not sure if this is a bug. Certainly extremely confusing behavior IMO.

Related: the green lock don't show up when something is Untrusted. You first need to mark it Trusted or Custom, then toggle the lock, then put it back to Untrusted. Blargh.

[8-bit]

Ah, that would explain it. I can reproduce it with those steps.

You would need to click the green lock to turn it into a red unlock, so that you mark the plain HTTP versions of those sites Untrusted.

Not sure if this is a bug. Certainly extremely confusing behavior IMO.

Related: the green lock don't show up when something is Untrusted. You first need to mark it Trusted or Custom, then toggle the lock, then put it back to Untrusted. Blargh.

Ok, once again, thanks - I'll give that a whirl - yes a bit confusing behaviour indeed.

Thanks all!

[8-bit]

You would need to click the green lock to turn it into a red unlock, so that you mark the plain HTTP versions of those sites Untrusted.

Understood, BUT, then the green HTTPS versions of the sites are not on my "master list". In other words, I can't block BOTH the secure AND unsecured connections. Only one or the other show up on the main prefs master list...

[Pansa]

You would need to click the green lock to turn it into a red unlock, so that you mark the plain HTTP versions of those sites Untrusted.

Understood, BUT, then the green HTTPS versions of the sites are not on my "master list". In other words, I can't block BOTH the secure AND unsecured connections. Only one or the other show up on the main prefs master list...

Green : https only
Red: https AND http.

Technically it should never "greenlock-distrust" because that is not a wanted behaviour, ever. That's why the interface doesn't show a lock on distrusted to begin with. Why would you want to block https but not http?
But that's what it currently does basically.

[8-bit]

Green : https only
Red: https AND http.

Technically it should never "greenlock-distrust" because that is not a wanted behaviour, ever. That's why the interface doesn't show a lock on distrusted to begin with. Why would you want to block https but not http?
But that's what it currently does basically.

Ah, totally understood. All clear now. Thanks for taking your time to help me out. MUCH appreciated.

I am still very concerned that the page is not automatically refreshing after changing prefs from the icon menu - which is a regression, but you have cleared this issue up for me very clearly (and so have the others).

Thanks all!
8-bit

[Thanks]

This solution (hopefully it'll be worked-out more elegantly at somepoint; BUT I do so appreciate the NS10 WE FFF57 FFS!)...

This solution -- the unlocking the https/http restriction -- should be pinned to the top of the forums and motded to the home page and announced to the heavens.