JavaScript-only whitelist?

Bug reports and enhancement requests
Post Reply
User avatar
Thrawn
Senior Member
Posts: 3106
Joined: Mon Jan 16, 2012 3:46 am
Location: Australia
Contact:

JavaScript-only whitelist?

Post by Thrawn » Sat Aug 25, 2012 12:22 am

This one's mostly for Giorgio, but I'm posting it here so that others can discuss its pros & cons.

NS3 will give comprehensive coverage of site-specific permissions. However, in the meantime, how practical or difficult would it be to add a second, intermediate whitelist, where JavaScript would be allowed, but not any other active content? So, on the menu, you could 'Allow example.com' or 'Script-allow example.com' (or something similar).

Advantages that I can see:
- Covers the majority of requests for site-specific plugin whitelisting.
- Makes plugin-blocking on trusted sites easier to use, since it's still possible to completely whitelist sites.
- Could be added to NS2 with (presumably) much less time & effort than the full NS3 engine.

Disadvantages:
- Redundant once NS3 is complete. If the effort is quite small, this might not matter, but if significant, it wouldn't be worth delaying NS3 to do it.
- Extra menu clutter. Probably the menu options for the intermediate whitelist should be hidden by default.
- Possibly confusing interaction with 'Apply these restrictions to whitelisted sites too'. Enabling that checkbox would mean that the regular whitelist and the intermediate would be the same.
======
Thrawn
------------
Religion is not the opium of the masses. Daily life is the opium of the masses.

True religion, which dares to acknowledge death and challenge the way we live, is an attempt to wake up.
Mozilla/5.0 (X11; Ubuntu; Linux i686; rv:14.0) Gecko/20100101 Firefox/14.0.1

tlu
Senior Member
Posts: 129
Joined: Fri Jun 05, 2009 8:01 pm

Re: JavaScript-only whitelist?

Post by tlu » Sat Aug 25, 2012 10:02 am

Thrawn,

I'm obviously not Giorgio :lol: and can't tell how difficult it would be to implement this feature. But considering that FF now offers click-to-play for plugins (which works very well with Noscript), I don't think that such an enhancement is worth the effort if we assume that NS 3 is (hopefully) not far away ;)
Mozilla/5.0 (X11; Ubuntu; Linux x86_64; rv:16.0) Gecko/20120819 Firefox/16.0

Post Reply