User-Agent: Mozilla/5.0 (Windows; U; Windows NT 5.1; en-US; rv:1.7.8) Gecko/20050511 Firefox/1.0.4 Build Identifier: Mozilla/5.0 (Windows; U; Windows NT 5.1; en-US; rv:1.7.8) Gecko/20050511 Firefox/1.0.4 The classification of this bug is dependant on the intention of how superior Firefox was intended to be over its competition, but I consider it critical, only because if I have 10 tabs opened and I am interrupted, I have to quickly bookmark most of the tabs, close the browser, open a new session, and click each bookmark to reload it. A momentary 'disconnect' or 'interruption' in the network connection renders the browser session useless, quite the opposite of how the download manager works, when running a simple sequence of steps to avoid losing the entire session. The steps to allow Download Manager to work have equivalent steps on a browser session as well. In addition, this also occurs in IE and Netscape, so it could be strictly Windows XP inherited, how hardware IDs with Wireless & Wired sessions work that I am not too fully familiar with it. But, I do think that if Firefox can overcome this (assuming that the OS is not the one that is preventing it), it would be a grave hidden advantage for FireFox for continuous 'uninterrupted' Internet service and a nice 'marketing' advantage. In the additional information section (part -b-) of this bugzilla form, I describe how Download Manager avoids this issue that the browser can't overcome. Seems like two different developers worked on either part of Firefox. I figure a design should be consistent in approach for the majority of the product, so it can easily be debugged, if there are any problems. Reproducible: Always Steps to Reproduce: Before proceeding, please see the additional information section - part a for environment information. This occurs in one of two following ways. Way #2 is the typical way, but #1 is more simplified to show a similar point & avoid filing two bugs that I think are essentially the same. WAY #1: 1. Turn on PC with LAN connected. 2. Open Firefox. Load any internet URL that is accessible. 3. Leave Firefox open. 4. Disconnect LAN Connection. 5. Turn on the wireless connection. 6. Go back to Firefox, access a different page (that isn't cached). WAY #2: 1. Open Firefox. 2. Double-click on the Icon which represents the Wireless Connection. 3. Browse & download files as one normally would, all the while monitoring the wireless connection signal strength and transfer speed. 4. Monitor it when it reaches 'Low' (or 1-2 bars) signal strength and '1.0' mbps transfer speed. 5. Read Actual Results - Way #2 - 'a' before proceeding. 6. A regular 'patient' user would simply wait until the Wireless regained its strength or simply move their PC around until it was viable. But, a power user would disable the wireless on the PC (popping out the PC Card, using XP to disable it, or use the button above the keyboard), and re-enable it thereafter. Windows XP would have a delayed off-beep and on-beep response. Go back to Actual Results - step 'b'. Actual Results: WAY #1 - Browser states 'Document has no data'. WAY #2 - 'a' - Firefox is still actively attempting to access the page or download that is in progress. But, it looks to be halted. Go back to Steps to Reproducing - Step '6'. WAY #2 - 'b' - Firefox is still in its hung state. This is OK. Try to re-load the same page, it says 'Document has No Data'. Even if I close the tab, open a new tab, and copy & paste the URL, it still says Document has No Data. How to reset this issue? I must close all the tabs and re-open Firefox. Expected Results: Firefox should reattempt any available connection and send the request through that connection to reestablish (handshaking, etc.) with the other end and resume as if nothing had occurred. -a- It shouldn't matter what type of wireless router & card one uses, but for informational purposes, I am using: 1. Use a PC with both a built-in wired connection and a built-in Intel-based Wireless Network Connection (mine is a Compaq NC8000 Laptop). 2. Use a Netgear WGR614 Router (v3+) 3. Setup is presumed to be a suburban area, not a city urban area or downtown. 4. Assuming that you are in a typical home, where by the Wireless router is on the 2nd level on the other side of the house and the PC is on the other side of the house in a room with the door closed. -b- In Download Manager, when an interruption has occurred, it simply hangs, as the browser counterpart does as well. But, it can be re-enabled without losing the entire session by doing the following steps (and equivalent steps in a browser): 1. Cancel the Current Download (Click Stop Icon in Browser Session). 2. Retry the Current Download (Click Reload Icon in Browser Session). As a result, the download manager will attempt to connect to ANY available network connection, even if it's different from the original one, but on the browser it cannot. Since, IE has no download manager, there's no way for me to confirm that IE can do the same. Netscape has that same ability, so it must be a Mozilla-inherent design.

This is a problem with the way win xp is set up on your computer to handle network connections. It is not an issue with Firefox neither anything Mozilla can do to improve the connection. You also say it occurs in IE and Netscape as well. If winxp looses the connection aned doesn't reestablish it then that is a Win XP issue. Please post in the forums at forums.mozillazine.org for assistance. If I have misread the problem that is occuring and there is something you think that firefox is able to do then please resummarise the bug as it is rather hard to understand what you think Firefox can do to help this issue. -> Invalid as an OS issue.

How would that explain the reason Download Manager can reconnect on the same session despite a momentary loss in the Network connection? It can query to see which connection is available, even if it's a different network connection. If you can offer a viable response, then move the bug back to 'Leave as RESOLVED INVALID' (Above Response for comment #1)

I think you misunderstand it. Windows XP can reestablish the connection, using a different way to access the Internet. So, first it shows the Wireless is connected, then I disconnect that, then reconnect using the Wired LAN. If I open a new IE or Netscape session while the Firefox session is still open, IE and Netscape can access the Wired LAN, so I know for sure that the Wired LAN has an Internet connection. Once I close Firefox and open it again, it will use the Wired Lan. I am wondering if Firefox can automatically detect a connection as it seems it should be able to do in the Proxies setup of the Firefox Connection Settings.

*** This bug has been marked as a duplicate of 230870 ***

Not a dupe, thats a different issue.

bug 291163 , which seems to be the same problem (or at least incredibly close), was duped to that bug, so i duped this one to it as well.

Mozilla/5.0 (Windows; U; Windows NT 5.1; en-US; rv:1.8b2) Gecko/20050528 Firefox/1.0+ ID:2005052805 Right, I now understand your problem. Open firefox, loose wireless connection, plug in wired connection or switch to different wireless connection. On my laptop firefox is able to continue browsing without restarting. Of course I might get a site not found error when switching connections but I am still able to go to the url when a connection becomes avaliable. -> WFM.

(In reply to comment #4, comment #5, & comment #6) No, this isn't a duplicate issue. Though I make reference to the Download Manager, the problem is in the Browser itself. The Download Manager as used as a reference to make a point that the browser itself should operate in the same fashion as the Download Manager, that if a download is paused (or in the case of a browser page, is stopped), and then the internet connection is switched from wireless to wired, then the download manager can 'retry' (or in the case of a browser page, click the reload button) and continue as if nothing interrupted it. (In reply to comment #7) What is WFM? Works for a Minute? 1. Wireless connected. 2. Firefox opens and goes to Google by default (set as homepage). 3. Wireless disconnected. 4. LAN connected. 5. Using same Firefox session as in step #2, go to another page, and get a no data found in document error. 6. If I open IE or Netscape after the LAN is connected, I can browse anywhere with no problem, but as long as the current firefox session is open, it cannot.

WFM = Works For Me. As comment 7 said, > On my laptop firefox is able to continue browsing without > restarting. Of course I might get a site not found error > when switching connections but I am still able to go to > the url when a connection becomes avaliable. You may want to try a firefox 1.1alpha to see if this issue has been resolved on the latest builds. You can grab a copy at: - http://weblogs.mozillazine.org/asa/archives/008227.html But I'd advise you make a new profile for it.

Mozilla/5.0 (Windows; U; Windows NT 5.1; en-US; rv:1.8b2) Gecko/20050530 Firefox/1.0+ WFM on my laptop, Verifying.