Open
Bug 460895
Opened 16 years ago
Updated 10 years ago
Private browsing mode feature
Categories
(SeaMonkey :: General, enhancement)
SeaMonkey
General
Tracking
(seamonkey2.1 wontfix)
NEW
Tracking | Status | |
---|---|---|
seamonkey2.1 | --- | wontfix |
People
(Reporter: vu1611, Unassigned)
References
(Depends on 2 open bugs)
Details
(Keywords: meta)
User-Agent: Mozilla/5.0 (Windows; U; Windows NT 6.0; en-US) AppleWebKit/525.13 (KHTML, like Gecko) Chrome/0.2.149.29 Safari/525.13
Build Identifier:
Web browser should allow for user to enter a 'private' mode where data
is not stored on the local pc, data may include web history, cookies etc.
Reproducible: Always
Steps to Reproduce:
1.
2.
3.
Comment 1•16 years ago
|
||
The core feature is going to land soon, so it will also take a simple UI-only patch in order for SeaMonkey to support this.
Depends on: PrivateBrowsing, mozpb
Comment 2•16 years ago
|
||
Confirming as I'd at least like to see it; it is a matter of "how to expose the UI" and we probably need at _least_ Session Store support first.
Status: UNCONFIRMED → NEW
Ever confirmed: true
Comment 3•15 years ago
|
||
The core bug seems to have lost steam as of March 2009, so I've posted a comment to see if anyone's still working on it. The Firefox implementation seems to work well enough. I find myself using Safari over SeaMonkey for most of my browsing because I want history entries and cookies suppressed for casual browsing, reserving it for work-related sites for which history and cookies are actually useful. Also, I'd prefer to prevent the browser from maintaining any information about sensitive logins (banks, credit cards, insurance, etc.) beyond not remembering the usernames and passwords.
Updated•15 years ago
|
Flags: wanted-seamonkey2.1?
Comment 4•15 years ago
|
||
So, the patch I've posted in bug 462832 is bitrotted right now. I need help from someone who's willing to put some efforts into making this patch apply cleanly on trunk and possibly handle a few cases which might have changed in the private browsing code after the time I wrote that patch (which shouldn't be that many.)
I'll be able to help any volunteer to work their way through the process, and I can provide them with a clear view of how they should drive the patch, and I can also promise timely reviews! :-)
Is there anyone up for this task?
Updated•15 years ago
|
Updated•14 years ago
|
Comment 8•12 years ago
|
||
The per-window private browsing back end is now fully enabled on trunk. We just need to create UI and port all of the supporting front end changes.
Keywords: helpwanted → meta
Comment 9•12 years ago
|
||
See Firefox Bug 832290 - Proper styling for full-screen private windows on Mac
Comment 10•12 years ago
|
||
Related bugs filed for Firefox which may need to be ported unless they get in effect implicitly for SeaMonkey by fixes in the Private Browsing backend code:
Bug 826865 - Do not store offline cache data in private mode
Bug 873024 - Changes in site-specific zoom leaks from private into regular
browser windows showing the same site
You need to log in
before you can comment on or make changes to this bug.
Description
•