This is a dup of bugsplat 124234, revived for new code base. Initially assigned to glynn to verify if it's still relevant once a new browser is available for testing. This may be an XP bug, it should be verified on all platforms. -------------------------------------------------------------------- ***On Mac with no established network connection; I used my Mac at home with modem off initially. System 8.1 on PPC 8500/120 Mac June 9 SF1 Gromit 5.0 1. Launch 5.0 app; you will get two no connection alerts after you ok profile selection as app launches fully, one right after profile and then when netscape default home page attempts to resolve. 2. Open a connection now while app is open; I dialed into Netscape. 3. Try to load a page now. • Page still will not load. Must quit app and relaunch to be able to load a page. We are not detecting dynamically when a connection is established if app is launched before a connection exists. Cannot check cross platform as I am at home. This did not occur in 4.05. ------- Additional Comments From sdagley 06/10/98 09:14 ------- Sounds like an NSPR issue to me but since we don't currently have a Mac specific NSPR engineer I'm just going to Cc: the NSPR folks rather than re-assign it. I'm also dropping the priority to P1 since it does NOT stop one from testing as long as a network connection exists before you launch Mozilla. ------- Additional Comments From freier 06/10/98 10:40 ------- This is approximately the same behavior I see running 4.05 at home on a PC, so perhaps the problem is more global than just MAC. On NT if you try to make a connection before establishing the PPP circuit, all hope is lost. It might time out and go revisit the issue, but for periods exceeding my patience, all lookups fail immediately (and locally). I've found exiting and restarting the communicator is the expediant solution. As far as looking for a MAC specific engineer, it's good of you to note that we don't specifically have one. But we still support NSPR on a MAC. The resources with which we do are our problem. ------- Additional Comments From brade 06/24/98 16:05 ------- OK, I find this bug to be particular annoying since I've been doing a lot of stuff on my portable lately and I intend to continue using Mozilla on my portable so I *really* need this fixed soon. In particular, after getting asserts on the first run of Mozilla, if I quit and run again, I crash. *Please* fix this bug soon so I can work remotely next week. :-)

This works with Seamonkey, albeit the app is not at the same level of completion our initial 5.0 codebase was. Marking as worksforme against Seamonkey Mac Jan 19. I simply unplugged Ether connection, launched and replugged and was able to connect without need to quit and relaunch Seamonkey.

Verified WFM

greg, can you humor me and try it on a dial-up ppp connection also? At least on a PC, dialing up and unplugging and plugging a cable effects two different responses.

Works fine with dialup connection, just checked with Jan 19. Launch and then connect, no problemo surfing.