Hide "Always-Blocked" Domains in Expandable Menu

[jimw]

Feature Enhancement Request

There are some domains that I never allow. It would be valuable to offer users the ability to hide "always-blocked" domains from the blocked list. These domain get in the way and clutter up the list. These domains could be hidden in an expandable menu below the blocked list. If the user needed to allow all, the collapsed menu would expand before the user was allowed to enable all. The structure could look something like this:



Thanks for your consideration.

[barbaz]

Hmm, that seems overly complicated. How about just providing the option to hide Untrusted entries in such an expandable menu? NoScript Classic does similar by default, and "always-block" is the main point of the Untrusted state anyway.

[jimw]

If I understand your post correctly, hiding untrusted entries would hide everything that was no explicitly trusted. And the list of domain might vary by page visited. By selecting the entries that would never be trusted, the user would be making an active choice to hide them, simplifying the menu and removing noise. Always-block differs from untrusted because the user is saying "Don't show me these anymore".

[barbaz]

If I understand your post correctly, hiding untrusted entries would hide everything that was no explicitly trusted.

No, I mean hiding the entries that are EXPLICITLY set as Untrusted.

[NSisGood]

+1. Hiding the entries that are EXPLICITLY set as Untrusted is exactly what I was to propose. I would also suggest to hide them from the counter on NS icon on FF toolbar.

[Compuitguy]

+1

[barbaz]

How about just providing the option to hide Untrusted entries in such an expandable menu?

Bump.

I would also like to request this feature for NoScript Options > Per-site Permissions. I just now tried NoScript 10 with my daily-use profile, and there are so many Untrusted entries that it's near-impossible for me to use that interface to manage my whitelist. Grouping and collapsing the Untrusted entries would completely fix this significant usability problem.