Open Bug 468879 Opened 11 years ago Updated 13 days ago

Add a preference to disable plugins inside the private browsing mode

Categories

(Firefox :: Private Browsing, enhancement, P3)

enhancement

Tracking

()

People

(Reporter: ehsan, Unassigned)

References

()

Details

(Whiteboard: [PB-P2])

In the security review for the private browsing mode, I suggested adding a preference to disable plugins altogether inside the private browsing mode.  Such a pref shouldn't probably be set by default, because many users would complain, but privacy-conscious users will probably appreciate such a pref.

Even with bug 468877 fixed, we would need such a pref as well, because bug 468877 enabled plugins opting in to respect the private browsing mode, and that may not be enough for all users.
Mass moving of all Firefox::General private browsing bugs to Firefox::Private Browsing.
Component: General → Private Browsing
QA Contact: general → private.browsing
Assignee: nobody → ehsan.akhgari
Whiteboard: [PB-P1]
Not needed for 3.1.
Priority: -- → P3
Target Milestone: --- → Firefox 3.2a1
Whiteboard: [PB-P1] → [PB-P3]
(In reply to comment #2)
> Not needed for 3.1.

I think we actually would want this for 3.1 (see bug 484792 for an example of why this would be useful), adding the wanted flag for evaluation.
Flags: wanted-firefox3.5?
Whiteboard: [PB-P3] → [PB-P2]
I don't think bug 484792 is asking for those plugins to be _disabled_. I would expect users to very much want their plugins for watching videos while ... uhm .. shopping.
(In reply to comment #4)
> I don't think bug 484792 is asking for those plugins to be _disabled_. I would
> expect users to very much want their plugins for watching videos while ... uhm
> .. shopping.

No, it's not asking for the plugins to be disabled, but it shows one case for this bug: privacy conscious users might want their plugins to be disabled inside the private browsing mode, in order to make sure no external piece of software leaves traces of their activities on the computer.  I think it's safe to assume that any user sophisticated enough to set a pref in about:config is supposed to know the implications (i.e., loss of functionality because of the plugins being disabled).
Flags: blocking-firefox3.6?
Flags: wanted-firefox3.6+
Flags: wanted-firefox3.5?
Flags: blocking-firefox3.6?
Flags: blocking-firefox3.6-
Recently I realized that even "private browsing" does not stop plugins from possibly loggin URIs. So maybe a warning for private browsing could be added whenever a plug-in is called. Maybe for plug-ins something like the popup-blocker is needed (taht is, individually trust your plugins or not).
I agree, while in private browsing mode, the user should have an option to:

1) disable all plugins
2) disable all addons
3) enable "Do Not Track"

Plugins/addons can potentially log info and leaves traces behind so it would be in the user's best interest to allow the option.
Severity: normal → enhancement
Status: NEW → ASSIGNED
Target Milestone: Firefox 3.6a1 → ---
Version: Trunk → unspecified
Assignee: ehsan → nobody
Status: ASSIGNED → NEW
You need to log in before you can comment on or make changes to this bug.