Open
Bug 760776
Opened 13 years ago
Updated 3 years ago
There is no notice/feedback/warning when a program/application is started upon clicking a downloaded file
Categories
(Firefox :: Downloads Panel, enhancement)
Tracking
()
NEW
People
(Reporter: Aleksej, Unassigned)
Details
(Whiteboard: [testday-20120601] Actual & Expected results are mixed up in #c0)
2012-06-01-03-05-20-mozilla-central-firefox-15.0a1.en-US.linux-x86_64
Steps to Reproduce:
1. Have an application chosen for a file type for clicking in the Downloads Panel.
2. Download a file.
3. Click an entry in the Downloads Panel.
Actual results:
There is some notice that a program is being started because of the click, then the program starts.
Expected results:
A program starts, quietly.
![]() |
Reporter | |
Updated•13 years ago
|
Whiteboard: [testday-20120601]
Comment 1•13 years ago
|
||
(In reply to Aleksej [:Aleksej] from comment #0)
> Actual results:
> There is some notice that a program is being started because of the click,
> then the program starts.
>
> Expected results:
> A program starts, quietly.
If I read this correctly, you're saying that a confirmation message appears before
the program starts. This is expected for some file types, like executable files.
Or is this a different issue?
![]() |
Reporter | |
Comment 2•13 years ago
|
||
Oops, sorry, I mixed actual and expected results up. It should be:
Expected results:
There is some notice that a program is being started because of the click, then the program starts.
Actual results:
A program starts, quietly.
Comment 3•13 years ago
|
||
There's already a preference for this, see "browser.download.manager.alertOnEXEOpen" in about:config. The default value is 'true', you will receive a warning when you start an executable. In that warning, you have a "don't ask" box to shut it off for the future. That would set the configuration value to 'false'.
![]() |
Reporter | |
Updated•13 years ago
|
Whiteboard: [testday-20120601] → [testday-20120601] Actual & Expected results are mixed up in #c0
Comment 4•12 years ago
|
||
Sorry, I still find unclear what's the bug about, comment 3 seems to explain the correct behavior, is not this what happens?
Updated•3 years ago
|
Severity: normal → S3
You need to log in
before you can comment on or make changes to this bug.
Description
•