Closed
Bug 463132
Opened 16 years ago
Closed 16 years ago
failing to leave private browsing mode can lead to session loss
Categories
(Firefox :: Private Browsing, defect)
Firefox
Private Browsing
Tracking
()
VERIFIED
FIXED
Firefox 3.1b2
People
(Reporter: zeniko, Unassigned)
References
Details
(Keywords: dataloss, verified1.9.1, Whiteboard: [fixed by bug 463188])
Steps to Reproduce: 1. Open a few tabs 2. Enter private browsing 3. Do your privacy sensitive thing (a few minutes should do) 4. Once you're done, close the window Expected result: Get either a warning that the tabs from step 1 will be lost, be asked to save those tabs before quitting or just get those tabs back. Actual result: The tabs are gone (unless Session Restore was enabled).
Comment 1•16 years ago
|
||
I think this issue is quite different to that of bug 463188. Bug 463188 is about the fact that after step 4 in comment 0, if you open Firefox in a profile with default settings, an empty session is restored. I see that this might prevent some confusions. Maybe we should detect in WindowIsClosing if we're the last browser window and we're in private browsing mode, and if so, show a warning (which should override the gBrowser.warnAboutClosingTabs warning)? CCing Alex because we're past string freeze, and I'm not sure what we want to do here. (Wishing that private browsing mode could have landed a few days before the string freeze...)
Comment 2•16 years ago
|
||
(In reply to comment #0) > Actual result: > The tabs are gone (unless Session Restore was enabled). Just to clarify, the tabs are *gone*, and session restore won't help here because it won't remember anything from your private session.
Reporter | ||
Comment 3•16 years ago
|
||
(In reply to comment #2) > Just to clarify, the tabs are *gone*, and session restore won't help here > because it won't remember anything from your private session. I was talking about the tabs from step 1 which are indeed remembered inside nsSessionStore and written to disk when quitting - if Session Restore is enabled.
Comment 4•16 years ago
|
||
(In reply to comment #3) > I was talking about the tabs from step 1 which are indeed remembered inside > nsSessionStore and written to disk when quitting - if Session Restore is > enabled. Oh, right...
Comment 5•16 years ago
|
||
>The tabs are gone (unless Session Restore was enabled).
I'm confused on how session restore got disabled, and if the user actively disabled it, why they would expect their tabs to be restored.
Comment 6•16 years ago
|
||
I suppose the answer to the second part would be because we are saying in the dialog that we are going to restore them, even though we are not.
Reporter | ||
Comment 7•16 years ago
|
||
(In reply to comment #5) > I'm confused on how session restore got disabled I meant that the startup option wasn't set to "Show my windows and tabs from last time". Session Restore can't be further disabled than that.
Comment 8•16 years ago
|
||
(In reply to comment #1) > I think this issue is quite different to that of bug 463188. Bug 463188 is > about the fact that after step 4 in comment 0, if you open Firefox in a profile > with default settings, an empty session is restored. > > I see that this might prevent some confusions. Maybe we should detect in > WindowIsClosing if we're the last browser window and we're in private browsing > mode, and if so, show a warning (which should override the > gBrowser.warnAboutClosingTabs warning)? CCing Alex because we're past string > freeze, and I'm not sure what we want to do here. (Wishing that private > browsing mode could have landed a few days before the string freeze...) So, Alex do you have any decision about the above quote yet?
Comment 9•16 years ago
|
||
Alex: ping?
Comment 10•16 years ago
|
||
I think we should save the session regardless of the startup option, since the user might want to momentarily go into private browsing mode.
Comment 11•16 years ago
|
||
Hmmm, Simon, reading comment 3, I think what you're really observing might have been solved by bug 463188. Can you please test this with the latest nightly and confirm it?
Reporter | ||
Comment 12•16 years ago
|
||
This bug used to depend on bug 463188 for a reason... ;-)
Status: NEW → RESOLVED
Closed: 16 years ago
Resolution: --- → FIXED
Comment 13•16 years ago
|
||
Sorry, the confusion was all mine. :-)
Depends on: 463188
Whiteboard: fixed by bug 463188
Comment 14•16 years ago
|
||
Mass moving of all Firefox::General private browsing bugs to Firefox::Private Browsing.
Component: General → Private Browsing
Updated•16 years ago
|
QA Contact: general → private.browsing
Updated•16 years ago
|
Whiteboard: fixed by bug 463188 → [fixed by bug 463188]
Target Milestone: --- → Firefox 3.1b2
Comment 15•16 years ago
|
||
Verified with multiple windows, tabs, and "Show my home page" set with: Mozilla/5.0 (Windows; U; Windows NT 5.1; en-US; rv:1.9.1b3pre) Gecko/20081228 Shiretoko/3.1b3pre ID:20081228032813 Mozilla/5.0 (Macintosh; U; Intel Mac OS X 10.5; en-US; rv:1.9.1b3pre) Gecko/20081228 Shiretoko/3.1b3pre ID:20081228020322
Status: RESOLVED → VERIFIED
Keywords: verified1.9.1
You need to log in
before you can comment on or make changes to this bug.
Description
•