Closed Bug 228508 Opened 21 years ago Closed 15 years ago

Feature Request: Allow all cacheing to be paused

Categories

(SeaMonkey :: General, enhancement)

x86
All
enhancement
Not set
normal

Tracking

(Not tracked)

RESOLVED DUPLICATE of bug 460895

People

(Reporter: Paul.Sorensen, Unassigned)

Details

(Whiteboard: bugday0420)

User-Agent: Mozilla/5.0 (Windows; U; Windows NT 5.0; en-US; rv:1.5) Gecko/20031007 Firebird/0.7 Build Identifier: Mozilla/5.0 (Windows; U; Windows NT 5.0; en-US; rv:1.5) Gecko/20031007 Firebird/0.7 Sorry if I submitted an enhancement incorrectly - I looked around and couldn't find another way. If a user wishes to do some browsing that they do not wish to appear in the caches, they should be able to "pause" the cacheing process. Once they have completed their browsing, they should be able to "unpause" the cacheing process. The benefits to this are that the user doesn't need to clear the caches - and therefore lose all the benefits. Reproducible: Always Steps to Reproduce: 1. 2. 3.
Marking new. Do you want your history be saved as well in this "stealth" mode?
Status: UNCONFIRMED → NEW
Ever confirmed: true
I would think that the "pausing" should include history. Basically the persistent state of the browser (so if you stop it and restart it) should be frozen while the "stealth" mode is active. btw I like the name "stealth" mode :)
oops - pardon the ambiguous language. When in "stealth" mode, history should not be recorded.
Product: Browser → Seamonkey
MASS-CHANGE: This bug report is registered in the SeaMonkey product, but has been without a comment since the inception of the SeaMonkey project. This means that it was logged against the old Mozilla suite and we cannot determine that it's still valid for the current SeaMonkey suite. Because of this, we are setting it to an UNCONFIRMED state. If you can confirm that this report still applies to current SeaMonkey 2.x nightly builds, please set it back to the NEW state along with a comment on how you reproduced it on what Build ID, or if it's an enhancement request, why it's still worth implementing and in what way. If you can confirm that the report doesn't apply to current SeaMonkey 2.x nightly builds, please set it to the appropriate RESOLVED state (WORKSFORME, INVALID, WONTFIX, or similar). If no action happens within the next few months, we move this bug report to an EXPIRED state. Query tag for this change: mass-UNCONFIRM-20090614
Status: NEW → UNCONFIRMED
see also bug 195265 SeaMonkey version of Firefox's "Private Browsing"?
Whiteboard: [bugday0420] [DUPEME]
(In reply to comment #5) > see also bug 195265 > > SeaMonkey version of Firefox's "Private Browsing"? Yep.
Status: UNCONFIRMED → RESOLVED
Closed: 15 years ago
Resolution: --- → DUPLICATE
Whiteboard: [bugday0420] [DUPEME] → bugday0420
You need to log in before you can comment on or make changes to this bug.