by barbaz » Thu Sep 11, 2014 6:10 am
Thrawn wrote:That's there because in many cases, you don't actually need to disable NoScript to make everything 'just work' - and if you don't need to disable it, then you're better off keeping some protection.
Yes, but that sort of warning is suitable only for "normal" / "non-techie" users. Power users (presumably, because a normal user has no valid use case for disabling that dialog) like agaxwmtp and myself, who know enough to go into about:config without needing to worry much about the warning, already know the risks of disabling NS, and are likely disabling it only for testing anyway. The dialog is actually a minor annoyance when I'm disabling and re-enabling all my extensions, which is now happening basically every time I use a current SeaMonkey nightly.
Actually, the first time I saw that dialog, I already knew that I would be turning off a huge chunk of my browser security (for testing only), and all the dialog did was force me to make an extra click and, since I wasn't expecting it, kinda scare me (but in a good way, because it's good to know that addons can prevent themselves from being disabled/removed
).
For me, now, the only purpose that dialog would have is to alert me if NoScript is being disabled, so even if I didn't disable NS myself I would still be able to cancel that from happening. But nothing other than me has tried to disable NS in my browser yet, so for all I know that use case is moot.
[quote="Thrawn"]That's there because in many cases, you don't actually need to disable NoScript to make everything 'just work' - and if you don't need to disable it, then you're better off keeping [i]some[/i] protection.[/quote]
Yes, but that sort of warning is suitable only for "normal" / "non-techie" users. Power users (presumably, because a normal user has no valid use case for disabling that dialog) like agaxwmtp and myself, who know enough to go into about:config without needing to worry much about the warning, already know the risks of disabling NS, and are likely disabling it only for testing anyway. The dialog is actually a minor annoyance when I'm disabling and re-enabling all my extensions, which is now happening basically every time I use a current SeaMonkey nightly.
Actually, the first time I saw that dialog, I already knew that I would be turning off a huge chunk of my browser security (for testing only), and all the dialog did was force me to make an extra click and, since I wasn't expecting it, kinda scare me (but in a good way, because it's good to know that addons can prevent themselves from being disabled/removed :shock: ).
For me, now, the only purpose that dialog would have is to alert me if NoScript is being disabled, so even if I didn't disable NS myself I would still be able to cancel that from happening. But nothing other than me has tried to disable NS in my browser yet, so for all I know that use case is moot.