100127 - opt in/opt out for javascript would be nice

Status: VERIFIED DUPLICATE of bug 38966

(SeaMonkey :: Preferences, enhancement)

Description

[Matthias Deege]

From Bugzilla Helper:
User-Agent: Mozilla/5.0 (Windows; U; Win98; en-US; rv:0.9.4) Gecko/20010913
BuildID:    2001091303

Mozilla can block cookies and images from special sites in the net, but
javascript can only be deactivated completely (or only for mails). For security
reasons one can deactivate javascript. But on the other side one has to activate
it for some sites that can be trusted or otherwise they won't work.
So I think it would be a nice feature to deactivate the Javascript Engine for
some sites or generally forbid it except of some you allow using Javascript.

Reproducible: Always
Steps to Reproduce:
Edit -> Preferences -> Advanced -> Enable Javascript for Navigator

Actual Results:  Javascript is completely deactivated or not

Expected Results:  Deactivate it except for some sites in a list or allow it
except of some sites in a list.

Comment 1

[gavin long]

Matthias, go and read

http://www.mozilla.org/projects/security/components/configPolicy.html

Unless I'm missing something, what you want is already in place.  (see
"Disabling All Javascript for a Site", about 2/3 down the page.)

There's no UI for it yet (I believe bug 38966 is covering elements of that)

As such, I think is is either a DUPLICATE or INVALID.

-> preferences, but leaving as unconfirmed for now

Comment 2

[Warner Young]

Also see bug 7380, bug 858, and bug 75371 (which isn't quite the same, but it
has some relation to this).

Comment 3

[Samir Gehani]

-> js folks (rogerl?)

Comment 4

[sairuh (rarely reading bugmail)]

this would be a dup of either bug 38966 or bug 75371...

*** This bug has been marked as a duplicate of 38966 ***

Comment 5

[sairuh (rarely reading bugmail)]

mass verification of duplicate bugs: to find all bugspam pertaining to this, set
your search string to "DuplicateBugsBelongInZahadum".

if you think this particular bug is *not* a duplicate, please provide a
compelling reason, as well as check a recent *trunk* build (on the appropriate
platform[s]), before reopening.