barbaz wrote:If this will be implemented I'd vote for an about:config-only toggle of "disable everything but ABE", with a warning when it's used - then:
- your clients won't do that willy-nilly, but you can recommend them to do it if they are in a hurry and want to troubleshoot more later
- if the user toggles that and it doesn't work, they know to look in the Browser Console (Ctrl-Shift-J) and if they don't know what to do next, they know to ask for ABE help; and OTOH, they still have _some_ protection left
- user can then just un-check NoScript Options > Advanced > ABE > Enable ABE to fully disable everything. The toggle should remind to enable ABE again if ABE is disabled at the time this toggle is used to turn NoScript on.
If this is implemented, I second the above. There needs to be protection against accidentally disabling any part of noscript, especially for anyone that has the "Automatically reload affected pages" option set. If the disable everything is an about:config option (I like this, cuz it would be hard to accidentally do this!), then some indication that it is in effect in the NS icon would probably be enough of a reminder that it was done. If the disable everything option is put in the NS Options GUI, then I think at least a prompt to confirm the disabling of NS should be issued, with the default button set to No or Cancel (don't disable), and an indication in the NS icon that everything is disabled. I also agree that making this a session only option (reset the next time FF starts) makes sense.
Again, I say the above only if this "disable everything" option is implemented. I do not need it and would not ever use it - that is what a separate Clean FF profile is for - but for the OP's case of having less technical users, a separate FF profile would probably not be a good alternative.