Closed Bug 173990 Opened 23 years ago Closed 23 years ago

Don't display "not found" warning after computer wake-up

Categories

(Camino Graveyard :: OS Integration, enhancement)

Product:
Camino Graveyard
Component:
OS Integration
Platform:
PowerPC
macOS
Type:
enhancement
Priority:
Not set
Severity:
normal

Tracking

(Not tracked)

Status:
RESOLVED FIXED

People

(Reporter: mu, Assigned: sfraser_bugs)

References

Details

When a user wakes up his cablemodem-connected computer from sleep and Chimera is already running, loading a page can result in a "page not found" message during the first awake seconds. My belief is that dhcp has not yet properly configured the network subsystem until that moment. After waiting a few seconds (less than 10), everything works fine. Displaying such a message on a "always connected" computer might confuse users and might lead them to the conclusion that they would have to restart Chimera or their complete system, instead of just waiting a few seconds. I suggest that Chimera should check the status of networking in such a case. If networking is being configured, Chimera should go into page loading/waiting status. When the configuration is finished, Chimera should proceed normally. That way, browsing looks like a seamless experience to the user.
*** Bug 173987 has been marked as a duplicate of this bug. ***
Michael, what build ID are you reporting this bug against? Does this also happen using Mozilla?
Summary: [RFE] Don't display "not found" warning after computer wakeup → [RFE] Don't display "not found" warning after computer wake-up
[RFE] is deprecated in favor of severity: enhancement. They have the same meaning.
Severity: normal → enhancement
Build ID is 2002.09.30.04. I haven't tried in Mozilla.
Summary: [RFE] Don't display "not found" warning after computer wake-up → Don't display "not found" warning after computer wake-up
Michael, please test using Mozilla.
(Sorry for the delay) I've tried in Mozilla 2002.10.16.12 and it's the same problem.
I'm not sure what to say about this ticket. It's not a Chimera issue so it should be moved, but I mean.. this is most likely an OS issue. When Mac OS X goes to sleep mode in a DHCP environment, it sets it's IP to 0.0.0.0 once woken up, and sends out a DHCP request. While all apps are affected by this, it's usually not noticed because a DHCP request is usually answered within the first second. This can all be confirmed by running "sudo tcpdump" and putting your machine to sleep and waking it up. At best, NSPR (or each individual browser) can see if the IP is 0.0.0.0 and do a loop for 10 seconds to see if an IP is successfully set, but.. that's pretty ugly. I'd almost wonder if it's just better to ask Apple to temporarily hang on network connections on wakeup until the DHCP request is made. Just my $0.02.
Does this still happen? I put a 1-second delay in some wakeup-code in the timer code, which probably fixes this. Will mark Fixed, please reopen if necessary.
Status: UNCONFIRMED → RESOLVED
Closed: 23 years ago
Resolution: --- → FIXED
You need to log in before you can comment on or make changes to this bug.