155831 - ChatZilla does not correctly handle IRC channels that are set as +i (invite only).

Status: RESOLVED DUPLICATE of bug 190747

(Other Applications Graveyard :: ChatZilla, defect)

Description

[Ben Meeks]

When trying to join an invite only channel, ChatZilla should simply give the
user a message saying that the channel is invite only without opening a tab for
that channel.

Currently, ChatZilla opens a new channel tab for the channel before checking to
see whether or not the channel is +i or +k (invite only or key-locked).  Then
the program displays a message warning the user than the channel is invite only
(in the channel window).

---
[INFO]Channel view for ``#warezwarez'' opened.
===#warezwarez: Cannot join channel (+i)
---

However, once that window is open, it cannot be closed by using the traditional
/part command.

---
===#warezwarez: You're not on that channel
---

So the channel tab remains open and cannot be closed until the entire ChatZilla
client is closed.

Comment 1

[Samuel Sieb]

Under the View menu is an item that says "Close View".  That will close the tab.

Comment 2

[Garth Wallace]

While it's possible to work around the extra view, current behavior is still
counterintuitive. Either Chatzilla should only open a view on a successful join,
or it should close the view automatically if the join is unsuccessful (and leave
an error message in the appropriate server view). Leaving the view open serves
no purpose.

Comment 3

[Adrian Ulrich]

The problem is, that chatzilla opens a new tab, before he could join..

Try to connect to a (slow) irc server and while chatzilla trys to connect type

/join #foobar..

You'll get a 'You have not registeret' message in a new tab.. and after
connecting, you can't use /part (because you are not in a channel..)


So imho chatzilla should just open a new tab when i could enter a new channel,
not while he is trying to enter..

Couldn't find a dup, mark it as NEW
-> OS/PLATFORM ALL
-> SEVERTY Minor (as a easy workaround is aviable..)

Comment 4

[Koike Kazuhiko]

This bug can be fixed with bug 190747.

*** This bug has been marked as a duplicate of 190747 ***