Closed Bug 317121 Opened 19 years ago Closed 19 years ago

stored nicknames containing brackets break Chatzilla

Categories

(Other Applications :: ChatZilla, defect)

defect
Not set
normal

Tracking

(Not tracked)

RESOLVED WORKSFORME

People

(Reporter: bugzilla, Assigned: rginda)

Details

User-Agent:       Mozilla/5.0 (Windows; U; Windows NT 5.1; en-US; rv:1.7.12) Gecko/20050915 Firefox/1.0.7
Build Identifier: Chatzilla 0.9.68.5.1 [Firefox 1.0.7/20050915]

When a nickname containing brackets is set in the preferences before connecting to a network, once connected the commands /part and /nick have no effect. Additionaly the context menu for a channel does not show the option to leave that channel (offers rejoin instead). The user has just no way to leave a channel or change his nickname.




Reproducible: Always

Steps to Reproduce:
1. in chatzilla:

/network-pref nickname [bug]me

2. restart chatzilla
3. connect to the network on which the pref has been set
4. join a channel
5. try to part or change the nickname
Actual Results:  
the commands /part and /nick have no effect

the context menu for a channel does not show the option to leave that channel (offers rejoin instead)

The user has just no way to leave a channel or change his nickname.

Expected Results:  
software functionnality should not be affected by the nickname
Dup of bug 278900, almost certainly.
Reporter, please state on what server/network you experienced this problem. Even better, copy-paste the output of /supports into a bug comment. I'm fairly sure James is right, but to be 100% sure, the /supports message would certainly help.
For clarity, that would be the output of /supports as shown when executed on the tab for the server/network you experience the problem on.

Fixing summary.
Summary: stored nickinames containing brackets break Chatzilla → stored nicknames containing brackets break Chatzilla
Two months later, no more comments. >> WFM
Status: UNCONFIRMED → RESOLVED
Closed: 19 years ago
Resolution: --- → WORKSFORME
You need to log in before you can comment on or make changes to this bug.