442722 - Be nice to warn when session restore option conflicts with remove private data

Status: NEW

(Firefox :: Settings UI, enhancement)

Description

[Maxi]

User-Agent:       Mozilla/5.0 (Windows; U; Windows NT 5.1; en-US; rv:1.9) Gecko/2008052906 Firefox/3.0
Build Identifier: Mozilla/5.0 (Windows; U; Windows NT 5.1; en-US; rv:1.9) Gecko/2008052906 Firefox/3.0

If you choose "Show my windows and tabs from last time" in Tools > Options >General but at the same time enable "Always clear my private data when I close Firefox" in Tools > Options > Privacy, no tab is restored as start up.


Reproducible: Always

Steps to Reproduce:
1. Choose "Show my windows and tabs from last time" in Tools > Options >General 2. Enable "Always clear my private data when I close Firefox" in Tools > Options > Privacy, no tab is restored as start up.
3. Open some tabs
4. Close Firefox
5. Restart Firefox

Actual Results:  
No tab is restored.

Expected Results:  
This is somewhat the desired behavior, since user wants personal data deleted, but at the same time he might expect tabs to be restored (see bug #398817 and #442632). It would be nice that a warning is issue when these conflicting options are chosen. Even better, the user could be allowed to choose to clean all data but that required to restore tab.

Comment 3

[niko.o]

Adding a warning is one possibility, but my issue is that the setting to clear the browsing and download history should not touch the tabs. Those can be completely independent. It's a sensible use case to clear the history but keep the tabs.

Comment 5

[zithro]

Posting here as still present in FF 113.0

I've linked my original bug report (1526556) to this one, which was closed by a clueless answer :
"Deleting the history on shutdown means that there is no data to restore the last session".
To which I replied :
"places.sqlite" and sessionstore/"recovery.js" are different files and have completely different functions

Also, I feel like either 839035 or 1526556 should be re-opened as the "main" bug report, and this very one should only be referenced to. Their titles are more appropriate to the "real" bug.
As niko.o said, it's not the fact that a warning is missing that hurts us, it's because FF behaves REALLY badly in that case !

Comment 6

[Jared Hirsch [:jhirsch] (he/him) (Needinfo please)]

Hello,

I wouldn't worry too much about which bug is duped to which other bug.

It is not clear if or when this work will be prioritized by our product managers, but if they decide to prioritize addressing this issue, I'm sure they will look at all the duped and related bugs in designing a solution.

Comment 7

[zithro]

Hello, got it !
However, and I can't do it as I'm not the OP, this bug is marked for version "3.0" (as it's a 15 years-long destructive-user-data bug).
Can you change it to FF 113.0 please ? TIA !

Comment 8

[Robert Longson [:longsonr]]

It's marked as discovered in version 3.0 Changing things to say it wasn't discovered till version 113.0 would be incorrect and I doubt it would get this bug fixed any more quickly either.