On some devices, losing the connection during a download (switching to airplane mode, unplugging the router, etc) will immediately fail that download. The expected behavior is that the download will switch to an idle state, then resume once the connection is restored. This bug can will likely be annoying for users downloading larger files - particularly those users who have a spotty connection. I looked into this some in bug 747388 (see comments 13-15). It looked like we were getting an ETIMEDOUT error, but I wasn't able to figure anything out beyond that. This bug had the side effect of leaving the .part file behind after failure; this was fixed in bug 747388 by checking for any temp files after a dl-failed, but it would be better if we could fix the actual failure. So far, this has only been confirmed on Samsung Devices (Galaxy S, Galaxy Note, and Galaxy Nexus). My Droid RAZR does not have this problem.
Also please note that on some devices the download notification indicates the download as being complete when the connection is lost - covered in Bug 753710.
status-firefox30: --- → affected
status-firefox31: --- → affected
status-firefox32: --- → affected
status-firefox33: --- → affected
status-firefox36: --- → affected
status-firefox37: --- → affected
status-firefox38: --- → affected
status-firefox39: --- → affected
status-firefox48: --- → affected
status-firefox49: --- → affected
status-firefox50: --- → affected
status-firefox51: --- → affected
As it can be seen in the duplicate bug 1301896 mentioned above, the bug still exists. I'm using Samsung Galaxy S5, running Android 6.0.1. Switching from mobile data over to a Wi-Fi network (and vice versa) while a download is in progress makes it fail. If you need any more info, feel free to ask.
status-firefox57: --- → affected
status-firefox58: --- → affected
status-firefox30: affected → ---
status-firefox31: affected → ---
status-firefox32: affected → ---
status-firefox33: affected → ---
status-firefox36: affected → ---
status-firefox37: affected → ---
status-firefox38: affected → ---
status-firefox39: affected → ---
status-firefox48: affected → ---
status-firefox49: affected → ---
status-firefox50: affected → ---
status-firefox51: affected → ---
status-firefox57: affected → wontfix
status-firefox58: affected → wontfix
You need to log in before you can comment on or make changes to this bug.