88943 - closing chatzilla should not depend on server response

Status: RESOLVED FIXED

(Other Applications :: ChatZilla, defect)

Description

[Jesse Ruderman]

Steps to reproduce:
1. Open Chatzilla.
2. Type /attach moznet.
3. Hit Alt+F4 or click the close button on the Chatzilla window.

Result: Chatzilla prints "Closing Chatzilla...".  If you're not behind a
firewall, it prints an error message and closes the window about a second later.
 If you're behind the Netscape or Harvey Mudd College firewall, the window won't
close until half a minute later, because the IRC server won't respond to your
/quit command until while it's waiting for an ident response.

When a user tries to close a Chatzilla window, Chatzilla should send a /quit
command to the server, but instead of leaving the connection open and waiting
for a reply to the quit command, it should close the connection immediately and
close the window.  This only applies to trying to close the window -- it's fine
to wait for a server response if the user types /quit.

Comment 1

[Robert Ginda]

Click close a second time to close the window without waiting for a response.

This is by design.  In Bug 79311, we changed from a synchronous write to an
async write, to avoid "issues" in necko.  We now need to wait for the async
write to take place before we can close the window, or our the write will never
take place and our quit message will always be "Connection closed by peer", or
something similar.

Comment 2

[Samuel Sieb]

Reopening.  This doesn't mean that it will be fixed anytime soon.  It's a very
difficult problem, but it would be nice to have it fixed.

Comment 3

[Samuel Sieb]

This appears to be fixed.  Please reopen if you still see it.