Closed Bug 215730 Opened 21 years ago Closed 21 years ago

No "Close View" after joining +k channel without key

Categories

(Other Applications :: ChatZilla, defect)

x86
Windows XP
defect
Not set
minor

Tracking

(Not tracked)

RESOLVED FIXED

People

(Reporter: thib+mozilla, Assigned: rginda)

References

Details

User-Agent:       Mozilla/5.0 (Windows; U; Windows NT 5.1; en-US; rv:1.5b) Gecko/20030808
Build Identifier: Mozilla/5.0 (Windows; U; Windows NT 5.1; en-US; rv:1.5b) Gecko/20030808

When joining a channel that has a key (+k) without supplying the key, an "INFO"
message appears in the newly opened window to inform the user that the channel
has a key. But I could find no "easy" way to close that window.

Reproducible: Always

Steps to Reproduce:
1. Let's say there is a channel named "#nicechannel" that is in mode +k with
some key.
2. Type "/join #nicechannel"
3. A tab opens with the name "#nicechannel" and with the message "Cannot join
channel (+k)"

Actual Results:  
The resulting window has no "Close View" option in its right-click menu. It just
has "Open at Startup", "Leave #nicechannel", "Clear View" and "Connection
status". Using "Leave #nicechannel" or typing "/part #nicechannel" results in
the error message "You are not on that channel". There is no obvious way to
close that unnecessary window.

Expected Results:  
Instead, there should be a "Close View" option with shortcut "Ctrl + W" in the
right-click menu. Or even better: the message "Cannot join channel (+k)" could
have appeared in whichever window the "/join #nicechannel" command was typed
before a new tab was even opened.

There is a workaround, of course: typing "Ctrl + W" which is the shortcut for
"Close View" otherwise. But it's not that obvious for most end users.
This is fixed in the latest (beta) version.
Status: UNCONFIRMED → NEW
Depends on: 210744
Ever confirmed: true
Status: NEW → ASSIGNED
The chatzilla 0.9.x branch has landed on the trunk and should be available in
tomorrow's nightly build.  If you believe this bug has not actually been fixed,
please repoen it.
Status: ASSIGNED → RESOLVED
Closed: 21 years ago
Resolution: --- → FIXED
Product: Core → Other Applications
You need to log in before you can comment on or make changes to this bug.