Open
Bug 1752349
Opened 4 years ago
Updated 4 years ago
[Linux] Downloads panel for the first download overlaps other windows
Categories
(Firefox :: Downloads Panel, defect, P5)
Tracking
()
NEW
People
(Reporter: hyacoub, Unassigned)
References
Details
Affected versions
Firefox 98.0a1 (2022-01-27)
Affected platforms
Ubuntu 20.04 x64
Steps to reproduce
- Open Firefox and maximise it.
- Open other program (for example a terminal window) and return to Firefox.
- Use a site that triggers a download in the background (after some time; you can use gdocs' export function which usually takes a little while to actually generate stuff).
- Switch to a different window/app before the download starts
Expected result
Downloads panel shouldn't overlap other windows.
Actual Result
Downloads panel for the first download overlaps other windows.
Comment 1•4 years ago
|
||
This is a result of the code at:
let shouldOpenDownloadsPanel =
aType == "start" &&
Services.prefs.getBoolPref(
"browser.download.improvements_to_download_panel"
) &&
DownloadsCommon.summarizeDownloads(this._downloads).numDownloading <= 1 &&
browserWin == Services.focus.activeWindow &&
gAlwaysOpenPanel;
if (
this.panelHasShownBefore &&
aType != "error" &&
!shouldOpenDownloadsPanel
) {
// For new downloads after the first one, don't show the panel
// automatically, but provide a visible notification in the topmost
// browser window, if the status indicator is already visible.
DownloadsCommon.log("Showing new download notification.");
browserWin.DownloadsIndicatorView.showEventNotification(aType);
return;
}
this.panelHasShownBefore = true;
browserWin.DownloadsPanel.showPanel();
specialcasing whether we've shown the panel before.
When we remove the browser.download.improvements_to_download_panel pref, we can just remove the tracking of whether we've shown the panel before, and this bug will go away.
If someone feels strongly we could fix it in the meantime but I don't think it's a big deal, given it's a one-off, and the logic here is a little tedious.
Priority: -- → P5
You need to log in
before you can comment on or make changes to this bug.
Description
•