InformAction Forums

Reported here: https://bugzilla.mozilla.org/show_bug.c ... 246349#c29
STR:
Nightly 2016-11-12, NS 2.9.5rc21. Create new profile, install 2.9.5rc21 from AMO
Go to about:config, find capability.policy.maonoscript.sites and replace its value with the string from this pastebin: http://pastebin.com/B1zMDHv7
Go to https://www.instagram.com/advokatzhorin/
Hover the mouse over NoScript icon: it says "Forbid Instagram", "Forbid akamaihd.net", that means instagram and akamaihd are whitelisted. However, scripts from both instagram and akamaihd are actually blocked by NoScript.

I'll try to optimize STR in the future.

Thank you for your report.
Editing that preference directly has never been really supported (it even used to be hidden from about:config, when CAPS still existed), even though it worked as a (quite unstable) hack.
The issue at hand is due to a lack of synchronization between the configuration in the parent process (where the UI is and the preference change is observed) and the content process( where the permissions are actually enforced), which instead is triggered whenever permissions are changed through the proper interfaces.
So, I'll probably "fix" it but, since is an undocumented and unsupported feature, low priority.

I initially came across this bug after upgrading from NoScript 2.9.0.14 to NoScript 2.9.5rc21 in my regular Nightly profile. Basically, that's what I did:
Add multiple pages to white list using NoScript 2.9.x dropdown menu on the navigation bar
Remove NoScript 2.9.0.14, install NoScript 2.9.5rc21
Bug is reproduced

I never edited about:config directly in this case. I'll try to work out new STR without editing about:config entry.