278740 - Unicode is not properly displayed when used in a TITLE tag

Status: RESOLVED INVALID

(Core :: Internationalization, defect)

Description

[Jim Tuttle]

User-Agent:       Mozilla/5.0 (Windows; U; Windows NT 5.0; en-US; rv:1.7.5) Gecko/20041107 Firefox/1.0
Build Identifier: Mozilla/5.0 (Windows; U; Windows NT 5.0; en-US; rv:1.7.5) Gecko/20041107 Firefox/1.0

Visit http://mysite.verizon.net/hypert/multimedia.html.  The TITLE tag is set to
"Multimedia ♫", which is the word "Multimedia" (duh) followed by a
musical-notes symbol/character.

Firefox does NOT properly display this symbol/character in the Title Bar. 
However, if you navigate to another page (anything - even just go Home), and
then hold down the Back Arrow (or pull down the Go menu), you will see the
symbol/character properly displayed!

So, the bug is primarily that Firefox does not display Unicode properly in the
Title Bar (yes, I've tried other characters).  Since Firefox is able to display
Unicode properly in the Back Arrow and Go menu histories, I think it's just
something in the Title Bar code.

Reproducible: Always

Steps to Reproduce:
See Details.
Actual Results:  
A box is displayed instead of the Unicode symbol/character.

Expected Results:  
The musical notes symbol/character should have been displayed.

Comment 1

[Phil Ringnalda (:philor)]

Worksforme on first load in WinXP, 1.0 and 20050115.

Comment 2

[Simon Montagu :smontagu]

I think this is just a limitation with the font used by Win2K in the title bar. 

Do you see the correct character in other browsers? 

What happens if you use Control Panel | Display | Appearance to change the
Active Titlebar font, e.g. to Arial?

Comment 3

[Jim Tuttle]

Simon, thank you for the suggestion.  If I change from the default Tahoma to
Arial, the correct character is displayed.  Didn't realize that some Windows
fonts were not fully Unicode compliant!

Shall I close this?

Comment 4

[Simon Montagu :smontagu]

(In reply to comment #3)
> Didn't realize that some Windows fonts were not fully Unicode compliant!

A font is not obliged to support every single Unicode character to be Unicode
compliant, in fact I believe it's impossible to do so with current font technology.
 
> Shall I close this?

I've done so (I also considered WONTFIX and WORKSFORME, but after all it doesn't
work with a default installation of W2K, and there isn't really anything here we
could be fixing).