Closed
Bug 1255353
Opened 9 years ago
Closed 9 years ago
Incorrect Font Rendering for Chinese Characters in UI
Categories
(Core :: Graphics: Text, defect, P3)
Tracking
()
RESOLVED
DUPLICATE
of bug 1245811
People
(Reporter: gonwan, Unassigned)
References
Details
(Whiteboard: gfx-noted)
Attachments
(5 files)
User Agent: Mozilla/5.0 (X11; Linux i686 on x86_64; rv:45.0) Gecko/20100101 Firefox/45.0
Build ID: 20160303134406
Steps to reproduce:
See attachment.
Should be same root cause as bug 1245804.
Reporter | ||
Updated•9 years ago
|
Component: Untriaged → General
OS: Unspecified → Linux
Priority: -- → P3
Hardware: Unspecified → x86
Comment 1•9 years ago
|
||
Bug 1243226 is marked as fixed on 45, but apparently this is still broken on 45?
Same here. Web pages are OK in 45, but chrome level text has picked some weird fonts. And set gfx.font_rendering.fontconfig.fontlist.enabled to false solves this.
Whiteboard: gfx-noted
I'm on Arch Linux. This is the only font-related changes I've made to the system besides installing a lot of fonts. These are all the fonts I've installed (obtained via pacman -Qo /usr/share/fonts/):
acroread-fonts-systemwide adobe-source-han-sans-tw-fonts cantarell-fonts gsfonts openimageio ttf-antykwa-torunska ttf-arphic ttf-arphic-ukai ttf-arphic-uming ttf-asana-math ttf-bitstream-vera ttf-dejavu ttf-freefont ttf-hanazono ttf-inconsolata ttf-indic-otf ttf-liberation ttf-linux-libertine ttf-monofur ttf-myanmar3 ttf-togoshi-mincho ttf-ume wps-office wqy-zenhei xorg-font-util xorg-fonts-alias xorg-fonts-encodings xorg-fonts-misc
I also noticed some characters rendering incorrectly both in the UI and in web pages. Only on Firefox.
Comment on attachment 8734269 [details]
Correct 门 character
Google Chrome
Comment on attachment 8734266 [details]
Incorrect 门 character
Firefox
Reporter | ||
Comment 10•9 years ago
|
||
This issue should have affected multiple users, and still exists in Firefox 46b5.
Will someone look into this?
Comment 11•9 years ago
|
||
Interesting... The content has the right font matching but the chrome doesn't... Is there any difference for font matching between chrome and content?
Comment 12•9 years ago
|
||
Looks like it is an issue from the special keyword value of "font" property. This issue is reproducible in content with "font: message-box".
Status: UNCONFIRMED → NEW
Ever confirmed: true
Comment 13•9 years ago
|
||
It seems to me this has been fixed in this push: https://hg.mozilla.org/integration/mozilla-inbound/pushloghtml?fromchange=ada58caa17b4f4c5788b89ff28787ff5a774089f&tochange=21ad62cfce1989cfb2881db01bacc236cc5917f6
It should be bug 1245811, which has been uplifted to beta 47. And it seems to me the issue here is not reproducible in Firefox 47b8.
Status: NEW → RESOLVED
Closed: 9 years ago
Resolution: --- → DUPLICATE
You need to log in
before you can comment on or make changes to this bug.
Description
•