78973 - Some font name still display old value after changing

Status: VERIFIED FIXED

(Core :: Internationalization, defect)

Description

[Yuying Long]

Build: 05-04 Win32 and Mac

Steps to reproduce:
1. Launch browser, Edit | Preferences | Appearance | Fonts
2. Change some fonts, what I did:
   a. Win2k-CN, Change Simp. Chinese Serif font from "Fixedsys" to "Songti" 
      Note: the default font is Fixedsys, and old version trunk build(e.g.       
      04-23) will show "Songti" by default on same OS.
   b. Mac9.0-Ja, Change Japanese Serif font from "Osaka" to any other one.
3. Click "OK" to close Preferences window.
4. Then open Preferences window again, and check the font that changed in step2.
 
Result:
1. You will see the font value still keep the name before change(e.g. Fixedsys 
for Simp. Chinese on Windows and Osaka for Mac).
2. Not every language has same result, like western will show the changed value, 
even some CJK languages.  And so far, I didn't see it on Linux(I didn't try 
every font though), no same result on old version trunk build neither.

Comment 1

[nhottanscp]

ylong, is this a regression?

Reassign to jbetak.

Comment 2

[Yuying Long]

It is regression for me.  Add regression keywords.  Note the new font menu is a 
little bit difference than old one, like Simp. Chinese are default as Fixedsys, 
and before it was Songti.

Comment 3

[nhottanscp]

ylong, do you know when did it start?

Comment 4

[Yuying Long]

I might be some time between 04-25 and 04-30.  Also with latast build, after you 
changed the font and click on "OK", you will see the font slightly changed - it 
might just didn't display the changes.

Comment 5

[[e-mail] (away - not reading bugmail)]

accepting

Comment 6

[[e-mail] (away - not reading bugmail)]

last checking to pref-fonts.js: loadrunner%betak.net May 1 15:08   bug 64231, 
r=nhotta, sr=alecf. This might have caused the regression. Will retest with 
04/30 and 05/01 builds.

Comment 7

[[e-mail] (away - not reading bugmail)]

ylong, did you see any errors/exceptions/warning on the JS console? I can't see 
the reported problem on my home W2K-US machine. 

Perhaps I'll have to install the same fonts you are using first. Maybe it's 
just limited to Win2k-CN and Mac9.0-Ja. Have you seen anything on e.g. W2K-JP?

Comment 8

[Yuying Long]

I guess I didn't get any error message about this on the JS console.  Seems as 
far as the name changed to non-latin, will see this problem.
However, it seems has been fixed on today's Win32 build.  I'll double check 
it on Mac once we have good Mac. build.

Comment 9

[[e-mail] (away - not reading bugmail)]

just filling in some more observations I've made, when discussion this with 
Yuying: 

- it appears to affect only the commercial build
- apparently affects only font names containing non-Latin characters
- the pref value is saved correctly to prefs.js
- JS console doesn't show any errors (this still needs to be double-checked)

Since there were some changes to the commercial skin, as Yuying observed, my 
theory is that the changes might have affected the drop-down widgets in a way, 
which prevents them from finding and selecting a list value containing non-
Latin characters. 

Depending on the incoming information and provided this problem persists in 
future builds, I'd recommend moving the bug to Bugscape and if we can validate 
the drop-down list behavior assigning it to XP-Toolkit.

Comment 10

[Yuying Long]

I checked it on 05-08 Mac commercial build.  Seems it works pretty much OK. I
guess the change of latast commercial skin fixed this problem.
I'll mark it as fixed right now.

Comment 11

[Yuying Long]

Verified.