When going to: http://www.sky.com/home/ the Stop button and the Mozilla icon in the top right corner goes crazy! Build 20000517
this should all get fixed when rpotts lands his progress and loadgroup cleaning effort. ->rpotts.
Assignee: gagan → rpotts
Summary: http://www.sky.com/home/ → Stop button goes crazy: http://www.sky.com/home/
Confirmed with 2000-05-18-08-M16 on WinNT. Just as important, the page never loads, Mozilla eats all available CPU, and Mozilla stops responding.
Arg... It looks like this is *not* the only problem... It appears that when a HTTP channel is cancelled, the NS_ERROR_BINDING_ABORTED error code is *not* propagated through the OnStopRequest(...). In nsHTTPChannel::Cancel(nsresult) FireNotifications() is called which uses NS_OK as its status code :-( I'm not sure yet if this is also contributing to the bug, but is is definately wrong!
it is really getting late :-( After looking at the HTTPChannel::Cancel() code some more, it appears that the correct status code *is* being propagated out through the OnStopRequest(...) A comment (or two) in the code explaining how/why everything works would be *very* helpful!!!
Status: NEW → ASSIGNED
OS: Windows 2000 → All
Hardware: PC → All
Whiteboard: have fix
Target Milestone: --- → M17
cc'ing ruslan who might be able to help...
Well. If OnStop was queued up already and cancel was fired after that - the status won't get reflected of course. As we've discussed earlier - EVERY CONSUMER MUST check EXPLICITLY for the channel's status and not rely on the status provided in notification because of asynchronous nature of our events.
I have a fix for this bug... It is not really network related... -- rick
Crashing on build 2000061820
I've checkine in a fix for this...
Status: ASSIGNED → RESOLVED
Last Resolved: 19 years ago
Resolution: --- → FIXED
Verified. Going to http://www.sky.com/home/ with build 2000062008 now correctly redirects to http://www.sky.com/home/GeneralIndex.html
Status: RESOLVED → VERIFIED
You need to log in before you can comment on or make changes to this bug.