Open Bug 1125121 Opened 7 years ago Updated 7 years ago

"Forget about some browsing history" has unintended results

Categories

(Firefox :: General, defect)

35 Branch
x86_64
Windows 7
defect
Not set
normal

Tracking

()

UNCONFIRMED

People

(Reporter: gizmokid2005, Unassigned)

Details

User Agent: Mozilla/5.0 (Windows NT 6.1; WOW64; rv:35.0) Gecko/20100101 Firefox/35.0
Build ID: 20150108202552

Steps to reproduce:

1) Visited some websites.
2) Clicked the "Forget about some browsing history" toolbar button.
3) Selected 5 minutes as the timeframe and hit "Forget!"


Actual results:

Firefox was closed upon the button press.
Expected history was forgotten.
All tabs and tab groups, including pinned tabs, were closed.


Expected results:

Firefox should be closed to remove the history, cookies, cache and tabs/windows associated with the desired timeframe to remove.

Existing tabs/groups, including pinned tabs, should *not* be removed.
AFAIK, they are part of history and need to be removed too.
Component: Untriaged → Bookmarks & History
(In reply to Loic from comment #1)
> AFAIK, they are part of history and need to be removed too.

Which is fine if they're part of the same history period I told it to delete. They're not though, in fact 1/4 of the tabs that were removed were pinned tabs. What's the point of pinned tabs if "forgetting some recent history" gets rid of them? (Yes, I know there's more use to them than just persisting, but for sake of this point...)
Pinned tabs have always been part of history. That's why they are removed too if you selected to remove the history after exiting Firefox.
(In reply to Loic from comment #3)
> Pinned tabs have always been part of history. That's why they are removed
> too if you selected to remove the history after exiting Firefox.

I won't argue that, of course they are. They're tabs I visited pages with.

However, if those tabs were visited/created 2 hours ago and I told FF to forget the last 5 minutes, why did they get nuked?
Component: Bookmarks & History → General
You need to log in before you can comment on or make changes to this bug.