Closed
Bug 385939
Opened 18 years ago
Closed 18 years ago
Auto-whowas doesn't work on freenode
Categories
(Other Applications Graveyard :: ChatZilla, defect)
Other Applications Graveyard
ChatZilla
Tracking
(Not tracked)
RESOLVED
FIXED
People
(Reporter: rdmsoft, Assigned: rdmsoft)
Details
(Whiteboard: [cz-0.9.79])
Attachments
(1 file, 1 obsolete file)
|
2.09 KB,
patch
|
Details | Diff | Splinter Review |
When you do /whois on a non-existent nick, freenode sends the 401 message (no such nick), but doesn't send the 318 (end of whois). As a result ChatZilla doesn't display anything and doesn't trigger the whowas.
| Assignee | ||
Comment 1•18 years ago
|
||
This moves the whowas call to on401 so it happens even if the "end of whois" message isn't received. Tested on all the built-in networks, except hybridnet which I couldn't connect to.
Assignee: rginda → rdmsoft
Status: NEW → ASSIGNED
Attachment #281694 -
Flags: review?(gijskruitbosch+bugs)
Comment 2•18 years ago
|
||
Comment on attachment 281694 [details] [diff] [review]
patch
<snip>
>- // If this user isn't here, don't display anything and do a whowas
>+ // If we already sent a whowas, don't display anything
I would prefer to keep the notion of the user not being there, because the if statement doesn't really have anything to do with the fact that we sent a whowas - it's just confusing like this. Feel free to use 2 lines of comments if you can't fit it otherwise... :P
with that,
r=gijs
Attachment #281694 -
Flags: review?(gijskruitbosch+bugs) → review+
| Assignee | ||
Comment 3•18 years ago
|
||
Just changed the comment.
Attachment #281694 -
Attachment is obsolete: true
Comment 4•18 years ago
|
||
Checking in mozilla/extensions/irc/xul/content/handlers.js;
/cvsroot/mozilla/extensions/irc/xul/content/handlers.js,v <-- handlers.js
new revision: 1.155; previous revision: 1.154
done
Status: ASSIGNED → RESOLVED
Closed: 18 years ago
Resolution: --- → FIXED
Whiteboard: [cz-0.9.79]
Updated•7 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
•