Open Bug 1025086 Opened 6 years ago Updated 6 years ago

When auto-opening tabs at startup to the same nickname on different networks, one of them gets a <2> suffix even if the tabs have different labels due to use of the pref extensions.irc.networks.NETWORK.user.NICKNAME.tabLabel

Categories

(Other Applications :: ChatZilla, defect, trivial)

defect
Not set
trivial

Tracking

(Not tracked)

People

(Reporter: tonymec, Assigned: rginda)

Details

Mozilla/5.0 (X11; Linux x86_64; rv:30.0) Gecko/20100101 Firefox/30.0 SeaMonkey/2.27a1 ID:20140214003001 c-c:1ce77c2f9bd0 m-c:d275eebfae04

ChatZilla 0.9.90.1

Reproducible: Always

Steps to Reproduce:
1. Have at least two networks auto-connected at startup (in the following STR I used moznet and freenode).
2. Make sure you are registered to NickServ on both networks. (If you don't know how, see "/query NickServ help register" and continue from there.)
3. Have the command "/query NickServ" followed by "/nickserv identify PASSWORD" among your startup comands for both networks, replacing PASSWORD by the passwords you defined at step 2. The use of these separate commands avoids displaying your password on your screen.
4. Include the following preferences in about:config (and create any of them that wouldn't yet exist):
    extensions.irc.networks.freenode.user.nickserv.hasPrefs    boolean   true
    extensions.irc.networks.freenode.user.nickserv.tabLabel    string    NF
    extensions.irc.networks.moznet.user.nickserv.hasPrefs      boolean   true
    extensions.irc.networks.moznet.user.nickserv.tabLabel      string    NM
Notes:
   1. This assumes that you haven't defined NF or NM as tab labels for any other tab.
   2. It is important to have the nickname in all lowercase (nickserv) in the pref name even though it actually refers to a mixed-case nick (NickServ).
5. Quit ChatZilla, then start it again.

Expected result:
The NickServ tabs for both networks should be labeled just NF and NM with nothing else added to them.

Actual result:
One of them has <2> immediately following the tab label defined at step 4.

Additional info:
The same happens for any nickname common to more than one network; I used NickServ in the above STR because it is "natural" to interact with NickServ at startup and possibly again later (e.g. querying it "info NICKNAME" for any registered nickname, or to know if a nickname is registered, and to see when it last quit). I think that the same would also happen for any duplicated channel name but I haven't found a suitable one.
Summary: When opening tabs to the same nickname on different networks, one of them get a <2> suffix even if the tabs have different labels due to use of the pref extensions.irc.networks.NETWORK.user.NICKNAME.tabLabel → When auto-opening tabs at startup to the same nickname on different networks, one of them gets a <2> suffix even if the tabs have different labels due to use of the pref extensions.irc.networks.NETWORK.user.NICKNAME.tabLabel
You need to log in before you can comment on or make changes to this bug.