We're calling on all EU-based Mozillians with iOS or iPadOS devices to help us monitor Apple’s new browser choice screens. Join the effort to hold Big Tech to account!

Sykje yn Support

Mij stipescams. Wy sille jo nea freegje in telefoannûmer te beljen, der in sms nei ta te stjoeren of persoanlike gegevens te dielen. Meld fertochte aktiviteit mei de opsje ‘Misbrûk melde’.

Mear ynfo

Dizze konversaasje is argivearre. Stel in nije fraach as jo help nedich hawwe.

about:settings seems to be inconsistant as to how files are handled according to type

  • 5 antwurd
  • 0 hawwe dit probleem
  • 1 werjefte
  • Lêste antwurd fan cor-el

more options

In about:preferences, in the ⚙ General tab, Firefox is set to handle the content of type "Zip archive" with the action "Use Archive Manager (default)".

To the question of what Firefox should do with other files, the set answer is "Ask whether to open or save files".

When I click on a link to a zip archive, said application indeed launches, no question asked, which is what I expect. However, the zip file is also saved in ~/Downloads which is, of course, where the files go when the corresponding action is set to "Save file".

In a similar vein, MP3 files are supposed to launch VLC but play in Firefox (which is also fine, just not what's set in about:preferences). M3U files do lauch VLC as set but are saved in ~/Downloads. PDF files are opened in Firefox, as the settings say they should.

Those inconsistancies seem to have started only a couple of weeks ago.

The nuisance is indeed moderate but still somewhat disconcerting.

The operating system is Debian 11, the desktop environment is XFCE4. The version of Firefox is 102.7.0esr (64-bit).

Is there something I misunderstood ? Some settings that I overlook ? A page in TFM that I didn't read ? Or is this random behavior something that comes with the territory ?

In about:preferences, in the ⚙ General tab, Firefox is set to handle the content of type "Zip archive" with the action "Use Archive Manager (default)". To the question of what Firefox should do with other files, the set answer is "Ask whether to open or save files". When I click on a link to a zip archive, said application indeed launches, no question asked, which is what I expect. However, the zip file is ''also'' saved in ~/Downloads which is, of course, where the files go when the corresponding action is set to "Save file". In a similar vein, MP3 files are supposed to launch VLC but play in Firefox (which is also fine, just not what's set in about:preferences). M3U files do lauch VLC as set ''but'' are saved in ~/Downloads. PDF files are opened in Firefox, as the settings say they should. Those inconsistancies seem to have started only a couple of weeks ago. The nuisance is indeed moderate but still somewhat disconcerting. The operating system is Debian 11, the desktop environment is XFCE4. The version of Firefox is 102.7.0esr (64-bit). Is there something I misunderstood ? Some settings that I overlook ? A page in TFM that I didn't read ? Or is this random behavior something that comes with the territory ?

Alle antwurden (5)

more options

Try making this preference in about:config true : browser.download.start_downloads_in_tmp_dir That restores the previous situation where files you want to open but not download are placed in your temp directory.

https://bugzilla.mozilla.org/show_bug.cgi?id=1738574#c133 https://support.mozilla.org/en-US/kb/about-config-editor-firefox

more options

Note that support for browser.download.start_downloads_in_tmp_dir got added with Firefox 102, so this should work for you.

more options

Terry's and cor-el's replies do restore the expected behaviour. Nevertheless, MP3s still open in Firefox instead of launching in VLC as set.

Again, not a big deal, it's just that the back-office and the UI do not agree.

more options

It does seem to be a mess. You could try "Always ask" instead of specifying an application.

more options

You can set this pref to false on the about:config page to prevent Firefox from playing media files you open in a tab via the HTML5 media player.

  • about:config => media.play-stand-alone = false