Open
Bug 1265356
Opened 10 years ago
Updated 3 months ago
Downloads with blocked data should be deleted after some time
Categories
(Toolkit :: Downloads API, defect, P3)
Toolkit
Downloads API
Tracking
()
NEW
| Tracking | Status | |
|---|---|---|
| firefox48 | --- | affected |
People
(Reporter: Paolo, Unassigned)
References
(Blocks 2 open bugs)
Details
(Keywords: papercut, privacy, Whiteboard: [fxprivacy])
Downloads with blocked data should be deleted from disk after some time if they are not unblocked first. The expiration time may be the same for all downloads, or different based on the associated verdict.
The deletion check could be done at shutdown, similarly to what is done for downloads that don't need to be persisted, or at startup when past downloads are deserialized. The latter has the advantage of not blocking shutdown. On the other hand, the former may be simpler to implement and would only block shutdown when there are blocked downloads to expire, which should be rare.
|
||
Updated•10 years ago
|
Priority: -- → P3
Whiteboard: [fxprivacy][triage] → [fxprivacy]
|
Reporter | |
Updated•9 years ago
|
Blocks: jsdownloads
|
||
Updated•3 years ago
|
Severity: normal → S3
|
||
Comment 1•2 years ago
|
||
Apart from the privacy problem, there's also an annoyance where if the user doesn't cancel or unblock the download, we may be asking about it on every restart. We could maybe just remove blocked downloads (and eventual data) after 2 sessions on non consecutive days (for example)
|
|
||
Comment 3•2 years ago
|
||
It looks like the annoyance was solved in Bug 1685737 for mixed-content, not for other kind of blocked downloads.
See Also: → 1685737
You need to log in
before you can comment on or make changes to this bug.
Description
•