304834 - /query doesn't support nicknames containing umlauts

Status: RESOLVED WORKSFORME

(Other Applications :: ChatZilla, defect)

Description

[Götz Waschk]

User-Agent:       Mozilla/5.0 (X11; U; Linux i686; en-US; rv:1.7.8) Gecko/20050511
Build Identifier: Mozilla/5.0 (X11; U; Linux i686; en-US; rv:1.7.8) Gecko/20050511

/query püppy
results in an error message.

Reproducible: Always

Actual Results:  
[ERROR]	Internal error dispatching command “query”.
	[ERROR]	[Exception... "Component returned failure code: 0x80070057
(NS_ERROR_ILLEGAL_VALUE) [nsIGlobalHistory.addPage]" nsresult: "0x80070057
(NS_ERROR_ILLEGAL_VALUE)" location: "JS frame ::
chrome://chatzilla/content/static.js :: openQueryTab :: line 1077" data: no]

Expected Results:  
open a private channel with püppy

Comment 1

[:Gijs (he/him)]

1) What version of ChatZilla are you using, and does this still happen in the
latest versions (trunk cvs and 0.9.68.5 on addons.mozilla.org)

2) What server do you test this on? It works for me, but I can't try it with a
nick which actually exists (it opens a query tab saying the nick doesn't exist,
and I can't use a nick with umlauts myself because unreal ircd doesn't allow
umlauted characters in nicknames)

Comment 2

[Götz Waschk]

1. Yes, it happens with 0.9.68.5 as well. I haven't tried trunk yet.
2. irc.xentonix.net

Comment 3

[:Gijs (he/him)]

Okay, thank you :-). I tried on the network in question, changed my nickname to
'Hännibal', and was able to open a query tab to myself, which worked fine.

I am using a tad outdated version of trunk cvs, I'll update that in a bit to see
if it matters (doubtful).

If this doesn't matter, then I'm wondering what difference between 0.9.68.5 and
trunk exists that creates this problem... James Ross may be able to shed some
light on this. I'm not sure (currently there's still a rather large diff between
0.9.68.5 and trunk, because the tree has been closed for so long and reviews are
going slowly).

Comment 4

[Samuel Sieb]

From the error message, it's not chatzilla giving the error, it's mozilla.  Please try in a newer version and see if it's still a problem.

Comment 5

[:Gijs (he/him)]

Marking WFM, I can't reproduce, the problem seems to be within Mozilla anyway and the reporter hasn't touched this bug for ages.

Anyone is free to reopen provided they can reproduce the problem with the latest ChatZilla release (0.9.69.1 at time of writing) and/or ChatZilla trunk, using trunk or 1.8 branch builds. If you  reopen, please provide careful instructions for others, and maybe try to figure out if this happens on any other servers.