Thanks for reporting back.
Trahanas wrote:Close the topic if you want, my bad!
I think not. If this UI design choice is left as-is, I'm sure you won't be the only user to make a thread like this. It just looks broken.
Conditionally greying out options is fine when user won't care about setting the greyed out option, and when setting it would be useless anyway. For example, if a program has a "Check for updates" checkbox, it would make sense to grey out a setting for frequency of update checks.
But a "check for updates" setting is something users typically want to set once and leave that way. In the case of NoScript, "Disable restrictions globally" is not like that.
The way that setting works in NoScript 10, enabling it permanently would pretty much defeat the purpose of using NoScript. A user might want to set it
temporarily, to quickly get some sites working and see what all they load, perhaps as part of troubleshooting. If user wants to edit their whitelist, or the permission presets...they can't, because these settings are greyed out. Worse yet, as pointed out in the OP, you can't even VIEW these settings, making troubleshooting a lot harder.
NoScript Classic didn't do this, and neither should NoScript 10.
It would be better to allow access to the Per-site permissions tab, but put a prominent warning banner or something, that says "Restrictions are disabled globally. These permissions will have no effect." Same for the individual presets configuration in the General tab. This would be much more understandable and transparent.
Thanks for reporting back.
[quote="Trahanas"]Close the topic if you want, my bad![/quote]
I think not. If this UI design choice is left as-is, I'm sure you won't be the only user to make a thread like this. It just looks broken.
Conditionally greying out options is fine when user won't care about setting the greyed out option, and when setting it would be useless anyway. For example, if a program has a "Check for updates" checkbox, it would make sense to grey out a setting for frequency of update checks.
But a "check for updates" setting is something users typically want to set once and leave that way. In the case of NoScript, "Disable restrictions globally" is not like that.
The way that setting works in NoScript 10, enabling it permanently would pretty much defeat the purpose of using NoScript. A user might want to set it [i]temporarily[/i], to quickly get some sites working and see what all they load, perhaps as part of troubleshooting. If user wants to edit their whitelist, or the permission presets...they can't, because these settings are greyed out. Worse yet, as pointed out in the OP, you can't even VIEW these settings, making troubleshooting a lot harder.
NoScript Classic didn't do this, and neither should NoScript 10.
It would be better to allow access to the Per-site permissions tab, but put a prominent warning banner or something, that says "Restrictions are disabled globally. These permissions will have no effect." Same for the individual presets configuration in the General tab. This would be much more understandable and transparent.