Bug 454372 - Fx aborts all downloads when going offline due to NetworkManager
Fx aborts all downloads when going offline due to NetworkManager
Status: CLOSED UPSTREAM
Product: Fedora
Classification: Fedora
Component: firefox (Show other bugs)
9
All Linux
low Severity low
: ---
: ---
Assigned To: Gecko Maintainer
Fedora Extras Quality Assurance
:
Depends On:
Blocks:
  Show dependency treegraph
 
Reported: 2008-07-07 21:57 EDT by Miloslav Trmač
Modified: 2008-07-08 13:12 EDT (History)
1 user (show)

See Also:
Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of:
Environment:
Last Closed: 2008-07-08 13:12:41 EDT
Type: ---
Regression: ---
Mount Type: ---
Documentation: ---
CRM:
Verified Versions:
Category: ---
oVirt Team: ---
RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: ---


Attachments (Terms of Use)

  None (edit)
Description Miloslav Trmač 2008-07-07 21:57:37 EDT
Version-Release number of selected component (if applicable):
firefox-3.0-1.fc9.i386

Steps to Reproduce:
1. Start a few large downloads (e.g. an ISO image, long video)
2. In the middle of the download, shut down your wifi router - or do something
   similar to simulate a temporary loss of internet connection (e.g. when the
   signal is weak).
3. Observe that Fx has gone into offline mode, and:
   a. terminated all downloads
   b. shows a separate dialog box for each terminated download
4. Go online again, restart the downloads, and observe that the previously
   downloaded data is being downloaded again.
  
Expected results:
At minimum, 4. should be able to resume downloads.  [Perhaps this depends on
server capabilities?]

Expected is that Fx doesn't terminate downloads, and lets them time out - or
continue if the network connection comes back up.

Terminating the downloads might perhaps be the right thing if the user went
offline intentionally - but definitely not when the offline state is transient.

Additional info:
Comment 1 Christopher Aillon 2008-07-08 13:12:41 EDT
https://bugzilla.mozilla.org/show_bug.cgi?id=437415

Note You need to log in before you can comment on or make changes to this bug.