From bug 411929 comment 19: We need to add a pref which enables the Satchel module to bypass the private browsing mode. This will enable us to provide a UI to allow users to always browse in private mode, but selectively enable recording their form fill history.
I'm not really sure if this makes sense to do. Is the use case this would be enabling (which isn't really clear from 411929) really all that compelling? The downsize here is (1) pref explosion and (2) more confusing UI. Taken to an extreme, what's it mean if I enter private browsing mode but have it save all my private data anyway?
I'll be honest: I don't personally see much sense in this either. This (and a few other similar) bug was filed because of the way Alex has prototyped the privacy UI. I'll leave further comments to him and mconnor.
The mockups referenced in bug 411929 comment 19 (http://people.mozilla.com/~faaborg/files/shiretoko/privacy_i2.png) show a prefpane option that allows the user to set the browser such that private data is never collected ("Firefox should never remember private data"). When the UI is set that way, it makes more sense to me that all the checkboxes about what sort of data Firefox should collect would be disabled, since the user has explicitly stated that Firefox is *not* to collect data. I recommend WONTFIX for this; if the user wants to be selective, there are ways of doing that by saying Firefox can collect data, and then specifying in what ways that data can be collected.
OK, I'm WONTFIXing this bug and the other ones I filed for the same reason, since like Beltzner suggests, there will be other ways to do this.
Status: ASSIGNED → RESOLVED
Last Resolved: 10 years ago
Resolution: --- → WONTFIX
You need to log in before you can comment on or make changes to this bug.