20445 - No network error messages thru dialog

Status: VERIFIED FIXED

(Core :: Networking, defect, P3)

Description

[Richard Zach]

There are, as yet, no warning messages displayed when a network error prevents a
page from loading, or a newsgroup from being opened, etc.  I'm thinking about
DNS lookup failures, refused connections, servers down.  I think this is pretty
important from the user's perspective since it is usually not obvious why
something isn't working in these cases.

To reproduce:
1. Enter nonexisting URI in location field
2. Press enter

Actual result: Throbber indicates page loading, progress bar shows "Document:
Done", but no new page is displayed

Expected result: A window with a warning message a la NS 4.x's "Netscape is
unable to locate the server xyz.  Please check the name and try again."

Comment 1

[Warren Harris]

Mass move of all bugs without target milestones to M13.

Comment 2

[leger]

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

Comment 3

[Gagan]

updating the summary.

Comment 4

[Warren Harris]

Subsumes 14696. Probably a dup of something else too, but I can't find it now.

Comment 5

[Warren Harris]

-> jud

Comment 6

[Warren Harris]

Socket transport needs to propagate up the right error codes, and the webshell
needs to notice them.

Comment 7

[Richard Zach]

Attachment: Drafts folder b/4 move

Comment 8

[Richard Zach]

Sorry, wrong bug.

Comment 9

[Judson Valeski]

DNS failure dialog is in. So is un-registered protocol.

We need to throw dialogs when a server is resolvable, but not connectable
(either it's down or won't accept a connection on that port).

Comment 10

[Richard Zach]

I noticed that there's also no error message for FTP file not found problems:

go to ftp://ftp.mozilla.org/test
Actual result:
Console shows "Error loading URL ftp://ftp.mozilla.org/test" but otherwise
nothign happens
Expected result: File not found error message

Comment 11

[Judson Valeski]

see 18007

Comment 12

[Judson Valeski]

I have a fix for the rest of this. Awaiting review.

Comment 13

[Judson Valeski]

fix checked in 1/24/00 7:50 pm pac time. I just added error capturing and dialog 
throwing for connection_refused errors and socket timeout errors.

Comment 14

[Richard Zach]

Would you be responsible also for local file errors (file not found, permission
denied)? Bug 26097.

Comment 15

[Judson Valeski]

*** Bug 28065 has been marked as a duplicate of this bug. ***

Comment 16

[Judson Valeski]

*** Bug 25507 has been marked as a duplicate of this bug. ***

Comment 17

[Tom Everingham]

verified:
Linux 2000022108
NT 2000022108
Mac 2000022108