Closed
Bug 1387688
Opened 8 years ago
Closed 8 years ago
linux platform, chinese character font display error on firefox52, but ok on fireofx54
Categories
(Core :: Graphics: Text, defect, P3)
Tracking
()
People
(Reporter: hwjeastd07, Unassigned)
Details
(Keywords: intl, Whiteboard: [gfx-noted])
Attachments
(2 files)
User Agent: Mozilla/5.0 (Windows NT 6.1) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/59.0.3071.86 Safari/537.36
Steps to reproduce:
1: start firefox52.
2: open https://wenku.baidu.com/view/a8ad8d55a45177232f60a2c6.html?from=search
3:click download, and display download Dialog box.
Actual results:
4:display file name error.
Expected results:
5:display chinese file name ok.
| Reporter | ||
Updated•8 years ago
|
Summary: linux platform, chinese character font display error on firefox52, but ok on fireofx53 → linux platform, chinese character font display error on firefox52, but ok on fireofx54
Updated•8 years ago
|
Updated•8 years ago
|
Component: Widget: Gtk → Graphics: Text
Priority: -- → P3
Whiteboard: [gfx-noted]
Comment 1•8 years ago
|
||
I don't think this is a Graphics:Text bug; it looks to me like the issue is that the encoding of the filename sent by the site has not been handled correctly.
Not sure where this does belong, though. The problem could be at the level of receiving and interpreting the site's response (in which case it might be platform-independent, though perhaps dependent on things like the OS locale, default codepage, accept-languages setting, etc), or it could be at the level of passing the filename to the Gtk file dialog (in which case it would be specific to Linux -- and could still be affected by various system/environment settings).
In any case, it sounds like the issue no longer occurs with current versions (though as long as we're not sure what the problem was, or what fixed it, then we can't have much confidence it is truly/permanently resolved).
| Reporter | ||
Comment 2•8 years ago
|
||
hi,I supplement more information。
1)test the problem on one machine(the same OS , same hardware...);
2)check out code from https://hg.mozilla.org/releases/mozilla-release code; build with same Compile options.
3)test result is that FIREFOX_AURORA_54_BASE tag is OK . but FIREFOX_BETA_53_END tag code is failed。
so maybe the patch between the two tag?
| Reporter | ||
Comment 3•8 years ago
|
||
hi,I supplement more information。
1)test the problem on one machine(the same linux OS [default unicode], same hardware...);
2)check out code from https://hg.mozilla.org/releases/mozilla-release code; build with same Compile options.
3)test result is that FIREFOX_AURORA_54_BASE tag is OK . but FIREFOX_BETA_53_END tag code is failed。
so maybe the patch between the two tag?
| Reporter | ||
Comment 4•8 years ago
|
||
I found the patch. see
https://hg.mozilla.org/mozilla-central/rev/2922efcfc78d
It should merge into esr52?
| Reporter | ||
Comment 5•8 years ago
|
||
Updated•8 years ago
|
status-firefox55:
--- → fixed
status-firefox56:
--- → fixed
status-firefox57:
--- → fixed
status-firefox-esr52:
--- → affected
Since this is fine in nightly, marking fixed.
Status: UNCONFIRMED → RESOLVED
Closed: 8 years ago
Resolution: --- → FIXED
You need to log in
before you can comment on or make changes to this bug.
Description
•