Closed Bug 1484508 Opened 6 years ago Closed 6 years ago

Option to automatically unblock downloaded files on Windows

Categories

(Toolkit :: Downloads API, enhancement)

61 Branch
All
Windows
enhancement
Not set
normal

Tracking

()

RESOLVED WONTFIX

People

(Reporter: oleg, Unassigned)

References

(Blocks 1 open bug)

Details

User Agent: Mozilla/5.0 (Windows NT 6.1; Win64; x64; rv:61.0) Gecko/20100101 Firefox/61.0
Build ID: 20180807170231

Steps to reproduce:

Downloaded a file via built-in download manager. Windows OS.


Actual results:

File is marked as dangerous as it comes from the Internet. One can change that by right clicking the file and pressing the Unblock button after the download.


Expected results:

There could be an option (say in about:config) to make this attribute change automatically. Various download managers (like FDM) do this automatically for every download. There is a workaround to alter Windows registry, but i would prefer to do this on a browser/app level.
Severity: normal → enhancement
Correction: by right clicking the file, going to Properties and pressing the Unblock button.

Prior to moving to Quantum i was using FDM with FlashGot extension. But aas FlashGot is not WE compatible i'm now exploring the option of using only the built-in download manager. So far the blocking of files is the only major annoyance stopping me from getting rid of FDM.
Such a preference existed and was removed multiple times:
1. browser.download.manager.skipWinSecurityPolicyChecks was removed; check merged with
2. browser.download.manager.scanWhenDone which passed the check on to the new
3. browser.download.saveZoneInformation which was removed in favor of
4. the Windows Group Policy Editor.
Blocks: 443215
Component: Untriaged → Downloads API
OS: Unspecified → Windows
Product: Firefox → Toolkit
Hardware: Unspecified → All
Whiteboard: [WONTFIX?]
Yes, this can be controlled with system settings.
Status: UNCONFIRMED → RESOLVED
Closed: 6 years ago
Resolution: --- → WONTFIX
Whiteboard: [WONTFIX?]
You need to log in before you can comment on or make changes to this bug.