"Always ask you where to save files" doesn't trigger save location with "Always open"
Categories
(Firefox :: Downloads Panel, defect)
Tracking
()
| Tracking | Status | |
|---|---|---|
| firefox-esr91 | --- | unaffected |
| firefox95 | --- | disabled |
| firefox96 | --- | disabled |
| firefox97 | --- | affected |
People
(Reporter: aflorinescu, Unassigned)
References
(Blocks 1 open bug)
Details
[Description:]
The "always ask where to save files" implies being able to set a download location on each download, followed by the action that the content type action specifies. Currently this works if the action is set to save, but not if the action is: open with default app or open with other app.
[Environment:]
Windows 10, Mac 11, Ubuntu 20.04
97.0a1 2021-12-22
[Preconditions:]
new profile (default download settings)
[Steps:]
- Go to about:preferences / General / Applications and set "Always ask you where to save files"
- Open https://ftp.mozilla.org/pub/firefox/releases/0.9.1/
- Click to download the zip file.
- From the download panel, right click and Always open.
- Download the zip file again.
- From the about:preferences / General / Applications, set the action for the zip to be open with other app (notepad for example)
- Download the zip file again.
[Actual Result:]
- Download location selector is displayed.
- Download location selector is not displayed
- Download location selector is not displayed
[Expected Result:]
For all cases, I would expect to be able to set the download location when the global settings is "Always ask you where to save files"
|
||
Comment 1•3 years ago
|
||
We should have communicated this better (or, indeed, at all), but this is the desired behavior. There's some elaboration here but the short version is that the per-type action setting is intended to take precedence over the global always ask setting.
|
Reporter | |
Comment 2•3 years ago
|
||
(In reply to Molly Howell (she/her) [:mhowell] from comment #1)
We should have communicated this better (or, indeed, at all), but this is the desired behavior. There's some elaboration here but the short version is that the per-type action setting is intended to take precedence over the global always ask setting.
No worry, but I will use this example to underline a possible bigger problem that I am concerned about in regards to comunicating our changes to our users. My first rule of thumb related to any kind of functionality change is how intuitive it is and even though what we're doing on the Downloads area looks and feel great, I belive I'm not exagerating by stating that we're doing a poor job communicating that to an enduser.
While i understand that we're already several cycles behind the initial schedule and resources short, I still feel we should do a minimal additional effort into figuring some ways to aleviate the learning curve of using advanced new download panel functionality.
Description
•