For bugs in Firefox Desktop, the Mozilla Foundation's web browser. For Firefox user interface issues in menus, bookmarks, location bar, and preferences. Many Firefox bugs will either be filed here or in the Core product. Bugs for developer tools (F12) should be filed in the DevTools product. (more info)
Watch This Product File Handling ▾ Firefox :: File HandlingFor issues dealing with helper applications, and guessing Content Types when they aren't specified/known (ftp:, file:, jar:, but generally not http:). This component does not cover: backend networking issues, such as those covered by Networking: FTP or Networking: File, nor does it cover the Download Manager which has its own component in the Toolkit product.
Watch This Component| Performance Impact |
| Webcompat Priority |
| Accessibility Severity |
| a11y-review |
| Tracking | Status |
|---|---|
| relnote-firefox | |
| firefox-esr115 | |
| firefox-esr128 | |
| firefox130 | |
| firefox131 | |
| firefox132 |
When user chooses to open a downloaded file served as application/force-download, Firefox associates this MIME type with the type *detected from the extension*. This is really wrong, since this blocks the detection of file type based on extension for future files, which have no reasons to be of the same type. For example, on two machines, one running Linux and the other Mac OS X, Firefox 7 was reporting application/force-download files as "Word document". This lead to several issues: - the correct handler application wasn't suggested - on the Mac, the .pdf extension wasn't preserved when renaming the file Removing the associations I found in mimeTypes.rdf[1], fixed the problem. Note there's no way to do this from the GUI, since you can change the handler application, but not the *file type*. So I think this MIME type should be blacklisted, just like application/octet-stream: the "Always perform this action for this file type" checkbox should be greyed out. Also, since users upgrading from previous releases are likely to have added this wrong association by mistake, it should be removed from the config file, or ignored.$ This bug is easily reproducible from a clean configuration in Firefox 7: you just need to open an application/force-download and check the box. 1: I found four mentions of this type actually, some of which quite weird. Here are the relevant excerpts, and I'm attaching one of the files.