Closed
Bug 463813
Opened 17 years ago
Closed 16 years ago
Join Channel dialog includes private channel marker and it breaks sorting
Categories
(Other Applications Graveyard :: ChatZilla, defect)
Other Applications Graveyard
ChatZilla
Tracking
(Not tracked)
RESOLVED
FIXED
People
(Reporter: bugzilla-mozilla-20000923, Assigned: bugzilla-mozilla-20000923)
Details
(Whiteboard: [cz-0.9.86])
Attachments
(1 file)
762 bytes,
patch
|
Gijs
:
review+
|
Details | Diff | Splinter Review |
When you do /LIST on a server with at least one private channel, you get a channel entry with a name of "*" (and no user count or topic) to show that there are >0 private channels.
The Join Channel dialog dislikes this entry, showing users and topic as undefined and the sorting refuses to sort that entry (meaning the channels returned before and after get sorted as two distinct groups).
I propose we make the dialog disregard the "*"-named entry upon reading it.
Comment 1•17 years ago
|
||
Sounds good! :-)
Assignee | ||
Comment 2•17 years ago
|
||
There seems to be some unknown server behaviour involved here, as I just got moznet and the other network I use (which is where the problem originally occured) to show the * channel entry with a user count. It might be that it shows that if there's only 1 private channel, and omits it when there's >1.
Either way, I don't think we should bother including the * entry, as you can't join it in any case.
Assignee | ||
Comment 3•16 years ago
|
||
Assignee: rginda → silver
Status: NEW → ASSIGNED
Attachment #415644 -
Flags: review?(gijskruitbosch+bugs)
Comment 4•16 years ago
|
||
Comment on attachment 415644 [details] [diff] [review]
Exclude "*" channel entries from list
Excellent, r=me.
Attachment #415644 -
Flags: review?(gijskruitbosch+bugs) → review+
Assignee | ||
Comment 5•16 years ago
|
||
Pushed --> FIXED.
Status: ASSIGNED → RESOLVED
Closed: 16 years ago
Resolution: --- → FIXED
Whiteboard: [cz-0.9.86]
Updated•2 months ago
|
Product: Other Applications → Other Applications Graveyard
You need to log in
before you can comment on or make changes to this bug.
Description
•