Closed
Bug 1211348
Opened 9 years ago
Closed 7 years ago
Don't restore private tabs after killing the app if "Close Private tabs when leaving private browsing" is enabled
Categories
(Firefox for iOS :: General, defect, P1)
Tracking
()
VERIFIED
FIXED
People
(Reporter: csuciu, Assigned: justindarc)
References
(Blocks 1 open bug)
Details
(Keywords: privacy, Whiteboard: [PrivateBrowsing])
Attachments
(1 file)
1. Go to Firefox settings and enable "Close Private tabs when leaving private browsing".
2. Open a few private tabs
2. Kill Firefox from the app switcher
3. Open Firefox
Expected: The private tabs should not be restored because the user is leaving private browsing when Firefox is closed
Actual: The private tabs are restored
Updated•9 years ago
|
Assignee: nobody → sleroux
tracking-fxios:
--- → 1.1+
Updated•9 years ago
|
Status: NEW → ASSIGNED
Comment 1•9 years ago
|
||
Not sure if we want to do this. Chrome doesn't close the tabs when the app is backgrounded and keep them open. I think the experience would be too jarring for the user to come back to the app and have everything change. For example, if the user was in a private tab and they come back from being backgrounded, what do we show?
Flags: needinfo?(dhenein)
Updated•9 years ago
|
Flags: needinfo?(dhenein)
Summary: Don't restore private tabs if "Close Private tabs when leaving private browsing" is enabled → Don't restore private tabs after killing the app if "Close Private tabs when leaving private browsing" is enabled
Updated•9 years ago
|
Whiteboard: [nicetohave1.1]
Comment 2•9 years ago
|
||
Not sure if this is something we want to address for 2.0? Adding :tecgirl as well.
Flags: needinfo?(randersen)
Updated•9 years ago
|
Comment 3•9 years ago
|
||
Maybe remove this option and leave PB mode instead?
Assignee: sleroux → randersen
Rank: 7
Hardware: Other → All
Whiteboard: [nicetohave1.1]
Comment 4•9 years ago
|
||
Leave the setting, kill the tabs—if we indeed can tell the difference between a crash and a hard kill. If crash, offer to restore with dialog on next session. Do not offer to restore on kill.
Flags: needinfo?(randersen)
Comment 5•9 years ago
|
||
On crash with "Close Private tabs when leaving private browsing" enabled:
Oops! Firefox crashed
Would you like to restore your private tabs?
[YES][NO]
Updated•9 years ago
|
Assignee: randersen → sleroux
Comment 6•9 years ago
|
||
Would we show this as an additional dialog after the current 'Restore Tabs' after a crash one? If "Close Private tabs when leaving private browsing" is disabled, we should restore all tabs and if it is enabled we show the 'Restore Private Tabs' one as well?
Comment 7•9 years ago
|
||
(In reply to Stephan Leroux [:sleroux] from comment #6)
> Would we show this as an additional dialog after the current 'Restore Tabs'
> after a crash one? If "Close Private tabs when leaving private browsing" is
> disabled, we should restore all tabs and if it is enabled we show the
> 'Restore Private Tabs' one as well?
My assumption is that we're providing this prompt in case it's one of the tabs causing the crash, correct?
Are we able to determine which tab caused the crash?
If so, then we should not load that tab and load the rest automatically, and prompt for Private tabs.
If not, then no, two dialogs is too much. Prompt to restore normal tabs. If they have the option to Close Private tabs enabled then kill those tabs. An expectation of loss should be apparent.
Updated•8 years ago
|
Assignee: sleroux → nobody
Status: ASSIGNED → NEW
Updated•8 years ago
|
Whiteboard: [PrivateBrowsing]
Assignee | ||
Updated•7 years ago
|
Assignee | ||
Comment 8•7 years ago
|
||
Attachment #8920382 -
Flags: review?(fpatel)
Updated•7 years ago
|
Attachment #8920382 -
Flags: review?(fpatel) → review+
Assignee | ||
Comment 9•7 years ago
|
||
Landed on master:
https://github.com/mozilla-mobile/firefox-ios/commit/f04a94ea636ea596ddae3533e73aafc2b461d251
Landed on v10.x:
https://github.com/mozilla-mobile/firefox-ios/commit/d47275d36a78a39cf2562c91a4d5a5878f4c4691
Status: ASSIGNED → RESOLVED
Closed: 7 years ago
Resolution: --- → FIXED
Comment 10•7 years ago
|
||
Verifying as fix on master 9653a62c5 & 10.0(7233).
You need to log in
before you can comment on or make changes to this bug.
Description
•