Open Bug 463553 Opened 16 years ago Updated 2 years ago

Add tabs to the Clear Recent History dialog box

Categories

(Firefox :: General, enhancement, P4)

enhancement

Tracking

()

REOPENED

People

(Reporter: faaborg, Unassigned)

References

(Blocks 2 open bugs)

Details

The difference between browser history and session data exists primarily on an implementation level, and not necessarily inside of the user's mind (unless the user has been involved with Firefox development.)  I think we should add tabs to the Clear Recent History dialog, since clearing all information from a particular time period, but leaving certain tabs open from that time period is counter intuitive.

Another issues is how the Clear Recent History dialog relates to private browsing mode:

Something that I am worried about is that the user opens several embarrassing
tabs, and then opens up private browsing mode.  As the start page suggestions,
they clear their recent history using the Clear Recent History dialog.  Of
course, history isn't the same thing as active tabs (in the implementation
model, but not the user's mental model), so these embarrassing tabs are
persisted in the previous session.  The user eventually closes down Firefox,
and leaves.  The next person to load Firefox will see the sensitive tabs, even
though the user thought they were taking every action they needed to in order
to cover their tracks.
(In reply to comment #0)
> since clearing all information from a particular time period, but leaving
> certain tabs open from that time period is counter intuitive.

That's actually a bug (see bug 463188 comment #7). All data saved by SessionStore should be discarded when clearing browser History. We currently fail to do that in the case where you've entered Private Browsing mode. No need for new UI.
OS: Mac OS X → All
Hardware: PC → All
This bug as it stands was FIXED in bug 463188.
Status: NEW → RESOLVED
Closed: 16 years ago
Resolution: --- → FIXED
>All data saved by
>SessionStore should be discarded when clearing browser History. We currently
>fail to do that in the case where you've entered Private Browsing mode. No need
>for new UI.

A few questions just to make sure I understand how this currently works:

-Can we clear based on the specific time period that the user specifies in the Clear Recent History Dialog?

-Does this include currently open tabs, recently closed tabs, both?

The intended feature was to clear any tabs (open or closed) that exist from new navigation events (open a new tab, enter a new URL In the location bar, click on link from external app) during the selected time period.
Simon, a few questions in the last comment ^^
(In reply to comment #3)
> -Can we clear based on the specific time period that the user specifies in the
> Clear Recent History Dialog?

No. This is currently all-or-nothing.

> -Does this include currently open tabs, recently closed tabs, both?

This includes anything we're tracking.

> The intended feature was to clear any tabs (open or closed) that exist from
> new navigation events

Right, I misread your bug description as to only affecting the remembered tabs in private browsing mode. Note the issues raised in bug 464417.
Severity: normal → enhancement
Status: RESOLVED → REOPENED
Component: Session Restore → General
QA Contact: session.restore → general
Resolution: FIXED → ---
>No. This is currently all-or-nothing.

Ok, resolving this bug would need to involve clearing information based on the specified time range.
Can be marked FIXED or DUP by bug 480169 ??
Status: REOPENED → RESOLVED
Closed: 16 years ago15 years ago
Resolution: --- → FIXED
(In reply to comment #7)
> Can be marked FIXED or DUP by bug 480169 ??

No, that bug did not add "tabs" to the list of selections in the CRH dialog.
Status: RESOLVED → REOPENED
Resolution: FIXED → ---
Blocks: 493151
I have an issue with the fact that when I remove certain pages (manually) from my history they remain accessible from the "Recently closed tabs" menu.  Does that fall under this particular bug?
No, bug 493124 seems to be what I was looking for.
Blocks: 1074244
Blocks: 1102808
Flags: firefox-backlog+
Priority: -- → P4
Severity: normal → S3
You need to log in before you can comment on or make changes to this bug.