Firefox 98+: 'File Download Complete' prompt never disappears
Since Firefox 98, whenever a file is downloaded or a page is captured (using add-on Page Saver WE) a display/pop-up appears in the top right-hand corner of the screen (or possibly under the 'Display Download Progress 'button'). Previously, this prompt/display/pop-up would disappear after a few seconds. Now it stays there until there is a mouse click anywhere on the screen (including outside the Firefox window). This is presumably a bug and it is also extremely irritating. Please change this back to the way it used to be (disappearing after a few seconds) or provide an option to specify how long the prompt/display/pop-up should be visible - like the 'new mail' prompt from Thunderbird. Many thanks.
Всички отговори (10)
Try changing this preference in about:config to false. browser.download.alwaysOpenPanel
https://support.mozilla.org/en-US/kb/about-config-editor-firefox
In a future update, a menu item to control whether the panel opens after each download could be added to the right-click context menu for the Downloads button. I'm not completely sure if or when that would happen.
Terry, thank you for your reply. To my knowledge, there was no mention of a change to the download prompt from being temporary to being permenant at Firefox 98....I do look at the release notes. I am aware that Firefox can be tweaked using about:config. However, this makes 'your version' non-standard, to a degree. It's also possible to screw things up. I have been using Firefox for 15+ years, in that time download prompts have never been permenant, to my knowledge. So why the change? Do people really want download prompts hanging around until they physically do something...and it's not just the latest download, it's EVERY download in that session. Why was the default changed to be permenant? Is there a requirement for it to be permenant? If there is a good proportion of users who now require it to be permenant, then why not add the option to SETTINGS rather than have people fiddle about with about:config. It's a shame Mozilla no longer accept any feedback on releases [the 'button' is present but doesn't go anywhere]. Is it really just another instance of a company that doesn't want to speak to it's users?
...by the way 'Hide Button WhenEmpty' does not solve the problem - thanks though.
rob3109buy said
I have been using Firefox for 15+ years, in that time download prompts have never been permenant, to my knowledge. So why the change? Do people really want download prompts hanging around until they physically do something...and it's not just the latest download, it's EVERY download in that session.
The panel opens to inform users that the download was saved successfully. Why doesn't it close itself after some period of time? No idea. How long would be long enough for a person who wanted to then launch one of those files?
If there is a good proportion of users who now require it to be permenant, then why not add the option to SETTINGS rather than have people fiddle about with about:config.
The intention is to add a right-click context menu option, but perhaps it could be in Settings instead. UI people need to decide on that.
It's a shame Mozilla no longer accept any feedback on releases [the 'button' is present but doesn't go anywhere]. Is it really just another instance of a company that doesn't want to speak to it's users?
Which one are you using?
- menu button > Help > "Share Ideas and Feedback"
- (menu bar) Help > "Share Ideas and Feedback"
both should go to https://ideas.mozilla.org/ and that should redirect automatically to the new site at https://connect.mozilla.org/
rob3109buy said
...by the way 'Hide Button WhenEmpty' does not solve the problem - thanks though.
Correct, that is the current menu. We're hoping for a new menu option above or below that item in a future release along the lines of Open List After Every Download. It's not in the Nightly release (future Firefox 101) yet, and I don't know when we can expect it.
Hello jscher2000....thanks for your reply again.....
'The panel opens to inform users that the download was saved successfully. Why doesn't it close itself after some period of time?...'
That's exactly my point. It used to close but it no longer does.
'....How long would be long enough for a person who wanted to then launch one of those files?'
Presumably there would need to be a 'time' parameter [similar to the 'email received' prompt in Mozilla Thunderbird]. It's something that needs to be planned and implemented properly.
'The intention is to add a right-click context menu option, but perhaps it could be in Settings instead. UI people need to decide on that.'
'The intention' ???.....I'm sorry but it just seems so obvious to me. It appears that someone has had an idea but not decided how to completely implement it and made some of it 'live' before the full functinality is present. It like building a ground floor and a first floor and then *thinking* about how/where/when to put the stairs in.
I'm sorry but one does not implement half a facility and leave users with a problem/issue. The change should be regeressed until complete functionality has been planned/specified/coded/tested. I was in IT for 30+ years. I would have got the sack if I did something like this. Sorry but I do feel strongly about this [and the other problem/change re:'Firefox Duplicate PDF File downloads']
Both are instances of incomplete, badly thought out changes.
sorry....the 'feedback' was via the Release info page.
For me, the downloads panel never auto-opened before. There was a subtle animation on the toolbar button (the level of subtlety has varied over the years) and that was it.
Obviously someone felt that there would be users who didn't want the panel to open, so they created a preference accessible via about:config. But it wasn't considered a big enough issue to create a UI control for it. The intention to add a menu item came up in a recently filed bug after blowback from users.
Sure, it would be nice if that had been included all along, but I guess the people who test new features in the Nightly and Beta versions of Firefox are comfortable using about:config and didn't agitate strongly enough for UI controls during the testing cycle (usually at least 8 weeks, sometimes more than 8 weeks).
How can Mozilla get better feedback earlier in the process to avoid problems like this in the future?
Hello..With due respect: [1] are you the only person on here? [2] do ypou actually work for Mozilla/Firefox? Your last reply is, I'm afraid, irrelevant. 1. It doesn't matter **exactly** what was displayed prior to F/Fox98. The fact is that it did not get in the way, whereas what happens now DOES get in the way and is very irritating. 2. From what you've previously said, this is a PARTIAL impletmentation. Thart in itself is crazy. Yopu don't implement half of something...as I said before...you plan/design/specify/code/ytest the WHOLE thing BEFORE sending it live....which has not happened in this case. WHAT WE REALLY NEEED is someone from Mozilla/Firefox to state what the actual situation is and what is or is not going to happen.....but Mozilla no longer accept any feedback. ... ... If there is anyone out there who actually works for Mozilla/Firefox and is involved in planning updates, could they please give some input....thanks very much.
rob3109buy said
Hello..With due respect: [1] are you the only person on here? [2] do ypou actually work for Mozilla/Firefox?
No and No.
Your last reply is, I'm afraid, irrelevant. 1. It doesn't matter **exactly** what was displayed prior to F/Fox98. The fact is that it did not get in the way, whereas what happens now DOES get in the way and is very irritating.
I understand what you don't like, I was just correcting the comparison for the record.
2. From what you've previously said, this is a PARTIAL impletmentation. Thart in itself is crazy. Yopu don't implement half of something...as I said before...you plan/design/specify/code/ytest the WHOLE thing BEFORE sending it live....which has not happened in this case.
As far as I know, they thought it was good to go based on the regular testing cycle. If I gave you a different impression before, I apologize for making post-release proposed fixes sound like previously planned changes.
If there is anyone out there who actually works for Mozilla/Firefox and is involved in planning updates, could they please give some input....thanks very much.
This is a support forum, not a place to research development history or engage with UI designers. You already have the other link: https://connect.mozilla.org/