Downloads in Private Window are canceled if about:downloads is open and you close the last tab if new tab is set to blank page or an extension page
Categories
(Firefox :: Private Browsing, defect)
Tracking
()
Tracking | Status | |
---|---|---|
firefox42 | + | verified disabled |
firefox63 | --- | wontfix |
firefox64 | --- | wontfix |
firefox65 | --- | fix-optional |
People
(Reporter: tchevalier, Unassigned)
References
Details
(Keywords: regression)
Comment 1•9 years ago
|
||
Reporter | ||
Comment 2•9 years ago
|
||
Reporter | ||
Comment 3•9 years ago
|
||
Reporter | ||
Comment 4•9 years ago
|
||
Comment 5•9 years ago
|
||
Comment 6•9 years ago
|
||
Comment 7•7 years ago
|
||
Comment 9•6 years ago
|
||
Updated•6 years ago
|
Comment 10•6 years ago
|
||
Comment 12•4 years ago
|
||
Did not encounter the issue for a while, but now with Firefox 80 (Developer Edition 80.0b5), the issue seems to return. So there is probably a regression compared with Firefox 79 and older where the issue was apparently already fixed.
You start a download in a private window, you close the last tab, an empty tab is automatically opened instead, downloads are cancelled and disappearing as if there were no downloads running at all. No even a need for about:downloads
to be opened for the issue to appear.
Comment 13•4 years ago
|
||
This one is very easily reproducible and started happening with Firefox 80. Even if about:downloads tab is open, if you close all the other tabs in Private Mode when downloading files that were triggered on these Private Tabs, then the downloads are cancelled without a warning.
Comment 15•4 years ago
|
||
I can reproduce this. It appears the problem is that a last-pb-context-exited
notification is sent by docshell or ContentChild, because the about:downloads page is loaded with system principal and doesn't have private browsing state, so it is not counted.
Johann (feel free to forward), is there a straightforward way of fixing this? Feels like we should just be tracking user-visible private windows in the parent process (though I guess that's messy for Fenix?
Comment 16•3 years ago
|
||
Looks like switching to the new user interface in Firefox 89+ fixed the issue.
Comment 17•3 years ago
|
||
Can confirm this was fixed in 91.
Fixed by Bug 1701303.
Description
•