![]() To learn more, see Properly configuring server MIME types and Common MIME types at MDN web docs. For example, Firefox may display the content as plain text instead of opening the file in an application. The the Media type, also called the MIME type or Content type, as configured by the web server, will determine what action Firefox will take.įirefox will not be able to properly handle a file if a misconfigured web server sends it with an incorrect content type. When you click on a link to download a file, you may see a dialog asking whether you want to save the file or open it with a specific application, if there is no download action already set for that file type. 4 Resetting download actions for all content types.3.3 "What should Firefox do with this file?" prompt does not show an application.3.2 "What should Firefox do with this file?" prompt.2.1 Set Firefox to ask you what to do for files with no defined content type.So this is a design flaw that causes data loss. ![]() If you then subsequently make changes to this file and same them, the changes will appear to have been lost when you subsequently open the file in its true location, and when the temporary directory gets cleaned up, they will truly be permanently lost. If you click “show in folder” or “open file” then the temporary download file/folder will be opened, if it still exists, otherwise nothing happens. This bug also affects opening files and directories from the download manager. ![]() It is simply impossible for it to know the information it needs. So this is in fact a fundamental design flaw in the way portals work, and there is no way for Firefox to take this into account. Because portals patch the file selection dialogs, there is no way for Firefox to know the real path of a file the user selected. I haven’t run this to confirm, but logically I’d suspect that this could quite easily be happening, and should be investigated.įirefox is not taking into account that it is using the document portal and is blindly saving that portal directory as the assumed target that the user chose. Since Firefox has changed it’s behavour recently to automatically download files without asking, this means that Firefox is likely saving directly to the documents store and will experiencing data loss as per Xdg-desktop-portal file loss It’s opening a file and inferring the folder from the path of the file. The second issue is that Ubuntu 20.04 portals don’t have support for opening folders at all. This is fixed on Ubuntu 21.04+, files will only be mirrored in /run if the snap didn’t originally have access, so this is much less likely to be user visible. This means that EVERY file/folder, even those in $HOME will be proxied via /run, even if they don’t need to be. The first lesser problem is that on Ubutu 20.04 with snaps, the portals are old and don’t check if the snap already has access to the selected file/folder. There’s two issues here, and one of them is potentially severe but I’ve not tested it, but it’s worth looking into. I'd appreciate any ideas and solutions for fixing this issue as it is not an option for me to manually set the download path each time I download a file. Ubuntu Mate Version 20.04.4 LTS (Focal Fossa) 64-bit I’ve recently changed to the snap version of firefox because the newest firefox version wasn’t available through apt anymore. You just proved it’s a SNAP issue and not Mozilla. There the “solution” is to blame it on snap: Similar issue (if not the same) I found on the Mozilla Firefox help forums:
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |