build id: 1999050408 seen on: windows nt if you follow a bad link, there is a message in the status bar that reads 'Unable to locate host .' The problem is the space just before the period - it shouldn't be there.

Should be easy to fix. Reassign to Hyatt.

QA assigning several orphaned UI/UE bugs. cpratt, I'm giving you the ones you wrote :-), and I'll take the rest.

I'm not the owner of navigator.xul. In the future, give bugs related to changes in navigator.xul to don. Thanks.

Hi there, Looks like ZuperDee of Penguin Land just detected another bug like bug 3839, and thought he might try to help--he **LOVES** fixing spelling errors like this!! First of all, this has **NOTHING** to do with navigator.xul, just so you know... So even don would probably be the wrong person for this. Unfortunately, this "spelling error" might be harder to fix than you think... Doing a 'grep' on the whole tree revealed this: [root@localhost mozilla]# grep -r "Unable to locate host ." * include/allxpstr.h:ResDef(XP_PROGRESS_UNABLELOCATE, XP_MSG_BASE+43, "Unable to locate host %.256s.") include/allxpstr.h:ResDef(XP_PROGRESS_5, XP_MSG_BASE+44, "Unable to locate host %.256s.") include/allxpstr.rc:ResDef(XP_PROGRESS_UNABLELOCATE, XP_MSG_BASE+43, "Unable to locate host %.256s.") include/allxpstr.rc:ResDef(XP_PROGRESS_5, XP_MSG_BASE+44, "Unable to locate host %.256s.") Those are the only places I could find this string... And in these instances, it looks to me like if 'foo' isn't found (for example), then it is supposed to say something to the effect of "Unable to locate host foo." I think therefore that you either had a hostname of NULL when you saw that message (and if so, I'd like to know when you could possibly have that situation), or you have encountered buggy code that is not displaying the hostname where it should for some reason. Does somebody want to look at this and tell me if I'm completely off base here??

Move to M10 ...

This actually does not do this anymore. You get an loading error instead. Bill can you close this out unless you are going to implement this?

That message originates in the networking library, I suspect. Those status messages were still not being passed to the browser, last I checked. Anyway, I'll determine what the deal is and close/re-assign as necessary.

This bug is irrelevant at the moment because we aren't getting status notifications from netlib. In any case, the message text comes from there so I'm reassigning it (changing the component).

I think I might have a dup for sending status bar messages. Rick do you have it?

looks like this got slipped. but status messages should be working fine now and be spelling error free!

I no longer see this status message at all - if I go to a host that's down/offline, I just see "Document: Done". So... I guess this is fixed. Marking verified.

Bulk move of all Networking-Core (to be deleted component) bugs to new Networking component.