Closed
Bug 116541
Opened 23 years ago
Closed 21 years ago
Support for ircnet's !-channels broken.
Categories
(Other Applications :: ChatZilla, defect)
Other Applications
ChatZilla
Tracking
(Not tracked)
RESOLVED
FIXED
People
(Reporter: jv, Assigned: rginda)
References
Details
From Bugzilla Helper:
User-Agent: Mozilla/5.0 (X11; U; Linux i686; en-US; rv:0.9.7+) Gecko/20011220
BuildID: 2001122008
Joining safe channel on ircnet (http://www.stealth.net/~kalt/irc/channel.html)
using short name creates two tabs - one for !channel and second for !PREFXchan.
The window for !channel can't be closed, since when trying to "leave" the
channel (there seems to be no other way to close window) server replies
"!channel: No such nick/channel" and window is not closed. (same hapens during !
channel creation)
Reproducible: Always
Steps to Reproduce:
Join any existing !channel, or create new !channel via joining !!chan.
Actual Results: Mozilla creates tab immediately.
Expected Results: Wait for JOIN comming from server.
![]() |
||
Updated•23 years ago
|
Status: UNCONFIRMED → NEW
Ever confirmed: true
Comment 1•22 years ago
|
||
Reporter: Does this problem still occour?
Reporter | ||
Comment 2•22 years ago
|
||
Checked with 2002100911 - Yes, still ocurrs.
Comment 3•21 years ago
|
||
Is this simply a case of the server joining you to a channel with a different
name to that used in the original JOIN command?
Currently (as far as I know) ChatZilla will create the tab as you execute the
/join command locally, perhaps specifically not doing this for !-channels would
help (since it'll create the tab when the server replys anyway)?
Comment 4•21 years ago
|
||
Since the problem only exists for attempting to join channels starting with "!",
I think we could safely hold off on the tab/view creation in such situations.
This would mean nothing happens client-side until the server replies saying
we've join !PREFIXchannel, at which point we create that tab.
Comment 5•21 years ago
|
||
Chatzilla 0.9.54 is now available and has landed on the trunk (cvs). This should
have resolved this bug; if it has not, please reopen it.
Status: NEW → RESOLVED
Closed: 21 years ago
Resolution: --- → FIXED
Updated•20 years ago
|
Product: Core → Other Applications
You need to log in
before you can comment on or make changes to this bug.
Description
•