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!

Funkcionalnosć tutoho sydła so přez wothladowanske dźěła wobmjezuje, kotrež maja waše dožiwjenje polěpšić. Jeli nastawk waš problem njerozrisuje a chceće prašenje stajić, wobroćće so na naše zhromodźenstwo pomocy, kotrež na to čaka, wam na @FirefoxSupport na Twitter a /r/firefox na Reddit pomhać.

Pomoc přepytać

Hladajće so wobšudstwa pomocy. Njenamołwimy was ženje, telefonowe čisło zawołać, SMS pósłać abo wosobinske informacije přeradźić. Prošu zdźělće podhladnu aktiwitu z pomocu nastajenja „Znjewužiwanje zdźělić“.

Dalše informacije

Firefox android v 82.1.2 files download issue

  • 1 wotmołwa
  • 2 matej tutón problem
  • 1 napohlad
  • Poslednja wotmołwa wot p.oltarzewski

more options

Latest release Firefox for Android, 82.1.2, dont let download any files from the web! As pdf,zip,apk,ecc! When you solve this issue?!

Latest release Firefox for Android, 82.1.2, dont let download any files from the web! As pdf,zip,apk,ecc! When you solve this issue?!
Připowěsnjene fota wobrazowki

Wšě wotmołwy (1)

more options

Device info: - Redmi Note 8 Pro - Android 9 PPR1.180610.011

Firefox Browser info: - 82.1.1 (Build #2015770923) (latest available on Google Play Store at the time of writing)

Reproduction scenario: - Find any website with a link to a PDF file - Click on the link; the download starts and download icon appears in notification area - The download continues for several minutes (even for ~60KB file on ~20Mbit link) - After several minutes a 'download failed' notification appears - No downloaded files are present in Firefox downloads folder

The same download works fine when external download manager is selected. Firefox has all necessary privileges enabled (i.e. access to device memory).

This seems to be a bug already reported in August: https://support.mozilla.org/en-US/questions/1297466

However the thread was closed by moderator AliceWyman, since OPs problem was solved (oh, wait - actually a question is marked as chosen solution... huh?). It is nice that you stick so close to Mozilla Support guidelines and props to you for 'solving' another issue, but wouldn't it be nicer to... I don't know... move the discussion to a separate issue and honestly look into it (since there clearly is a problem) instead of axing the thread? Show a little commitment to users? It's common courtesy in many opensource projects, nothing out of the ordinary...