74753 - Can't use intl characters in <window title="...">

Status: RESOLVED FIXED

(Core :: XUL, defect)

Description

[Dan Rosen]

Mozilla and Linux in general have no problem displaying international (eg.
ISO-8859-1) characters in a window's titlebar, but on Linux you can not specify
a window title in XUL to contain those characters. This *does* work on Windows,
and I haven't tested Mac.

If you put a non-ascii character in a <window title="...">, such as en-dash
(&#8211; in XML), that character and all text following it do not appear in the
title.

Comment 1

[Dan Rosen]

I'm hoping this is something brainless like using a char* instead of a PRUnichar*...

Comment 2

[Dan Rosen]

Attachment: simple testcase

Comment 3

[Dan Rosen]

attached testcase. afaik, to see the window title, you have to put the testcase
in chrome and load mozilla with the chrome url you give it...

Comment 4

[Dan Rosen]

Attachment: another interesting testcase

Comment 5

[Dan Rosen]

Whoa. There's lots of strange fu going on in gtk/nsWindow.cpp::SetTitle:

  http://lxr.mozilla.org/seamonkey/source/widget/src/gtk/nsWindow.cpp#2044

It must work, though -- int'l characters in the subject line of a mail
composition window show up in the title bar just fine, and I assume that gets
set through here.

Comment 6

[Dan Rosen]

Man. I have no idea what's going on here. I tried to trace through the codepath
for setting window title from xul with danm, and compared that to the codepath
for setting window title via the subject line in mail compose, and we found
nothing telling. This also may or may not be related to bug 9449...

->future, helpwanted... Hopefully somebody knows how to stomp on this properly.

Comment 7

[Greg K.]

Reference also bug 36689 (Mac OS 8/9) and bug 92503 (Mac OS X).

Comment 8

[Dan Rosen]

[spam] [e-mail]'s bugs subject to redistribution by chofmann. R!

Comment 9

[Simon Montagu :smontagu]

*** Bug 110347 has been marked as a duplicate of this bug. ***

Comment 10

[Jungshik Shin]

This should have been resolved as fixed a long time ago because it's fixed in
2001. (see bug 9449 comment #39 and bug 110347 comment #11)