Open
Bug 853473
Opened 12 years ago
Updated 2 years ago
Clearing downloads list while in private browsing mistakenly clears about:downloads entries
Categories
(Firefox :: Downloads Panel, defect)
Tracking
()
NEW
People
(Reporter: sbadau, Unassigned)
Details
Mozilla/5.0 (Windows NT 6.1; rv:22.0) Gecko/20130321 Firefox/22.0
Build ID: 20130321030940
Steps to reproduce:
1. Launch Firefox
2. Enter Private Browsing mode (File menu-> New Private Window)
3. Perform several downloads of your choice
4. Open the downloads panel -> right click on any of the downloads and select Clear List
5. Open the downloads manager (Ctrl+J)
Expected results:
All the downloads from the panel are cleared, but not the ones from the downloads manager (about:downloads tab).
Actual results:
The downloads are cleared both from the downloads panel and from the downloads manager (about:downloads tab). This behavior is not encountered in normal browsing - when Clear List is used, only the downloads from the panel are cleared.
Note:
Reproducible also on latest Aurora and on Firefox 20 beta 6.
I'm still investigating if this is a regression or not and I'll post the results as soon as possible.
Reporter | ||
Comment 1•12 years ago
|
||
"Clear List" option deletes the downloads from both the panel and the downloads View since December 30th (until then the downloads made in Private Browsing were not visible in the downloads view). I wouldn't say this is a regression, it's the initial implementation.
Summary: Clear List in private browsing → Clearing downloads list while in private browsing mistakenly clears about:downloads entries
Comment 2•12 years ago
|
||
Since they don't exist in history, they are removed from the manager when removed from the panel.
In non-pb mode they are removed from the panel, but their history persists in the manager.
It's surely not a regression, I'm not sure if it's a bug since it's working by design, the bug could mostly be a somwhow confusing behavior for the user, at a maximum.
Updated•2 years ago
|
Severity: normal → S3
You need to log in
before you can comment on or make changes to this bug.
Description
•