[Fixed] All permissions suddenly CUSTOM

[barbaz]

Like the title says. Firefox 79 Dev Edition, NoScript 11.0.34rc1 here.

This happened to me when I was manually setting domains to TRUSTED in NoScript Options > Per-site Permissions trying to get a website to work. The actual permissions seemed preserved, just that the presets are suddenly not used?

I run the browser in a sandbox, so ended up just quitting and dumping the change. I wasn't able to reproduce it again so far. I might try again later.

Anyone else seeing anything like this?

[barbaz]

I saw this again.

Possible STR:

1) NoScript Options > Per-site Permissions, add blindspot.fandom.com to TRUSTED and click the green lock to make this entry HTTPS only.

2) Leaving NoScript Options open, visit https://blindspot.fandom.com/ in another tab. (Let it redirect to the main page.)

3) Open the NoScript popup, look at the sites listed, then close the NoScript popup without doing anything with it.

4) Leaving both tabs open, go back to NoScript Options and manually add wikia.nocookie.net

[therube]

Confirmed.

I see a lot of Custom .
No idea what a "default" listing should look like?
I'll take it that if a site is Allowed, all the checkboxes are enabled? Well, at least that what it looks like, now.
And on sites where you may have actually Customized Allows (checkboxes), that they were left in their existing state. Actually all I can say on a "truly" Custom site is that not all the checkboxes are allowed.


Looks to be an aberration, with things righted after a restart.

[skriptimaahinen]

Can confirm the steps do cause both blindspot.fandom.com and wikia.nocookie.net to appear as CUSTOM. But like therube noted, they only appear so. If the options page is refreshed, both are back to TRUSTED.

Additional things:

Right after the permissions change to CUSTOM:

1. If the wikia.nocookie.net is set to DEFAULT and the page is refreshed, it will revert to TRUSTED.

2. If the wikia.nocookie.net is first set to e.g. UNTRUSTED (no refresh) and then to DEFAULT and the page is refreshed, it will be DEFAULT (vanish).

Looks like the problem lies with ui.js:799 getPresetName that fails to correctly compare preset and perms objects, probably due to the opening of the popup which causes the UI.policy to be set again and thus making the perms and preset not to be of same instance. JSON.stringify?

[Giorgio Maone]

Please check latest dev build:
v 11.0.35rc2
============================================================
x Updated TLDs
x Fixed buggy policy references in the Options dialog
x More accurate NOSCRIPT element emulation
x Anticipate onScriptDisabled surrogates to first script-src
'none' CSP violation
x isTrusted checks for all the content events
x Improved look in mobile portrait mode

[barbaz]

That fixed it. Thanks Giorgio & skriptimaahinen!