Closed
Bug 1305010
Opened 8 years ago
Closed 5 years ago
FF50b1: Some Unicode 9 Emoji not recognized.
Categories
(Core :: Graphics: Text, defect)
Tracking
()
RESOLVED
DUPLICATE
of bug 1281448
People
(Reporter: bugzilla, Unassigned)
References
Details
User Agent: Mozilla/5.0 (Windows NT 6.1; WOW64; rv:50.0) Gecko/20100101 Firefox/50.0 Build ID: 20160920155715 Steps to reproduce: Testing out FF 50beta1 on my Windows 7 Pro 64bit system. Viewed the following page: http://emojipedia.org/unicode-9.0/ and https://en.wikipedia.org/wiki/Emoji Actual results: The following Emojis are displayed as number blocks:
It chopped off some information. The Emojis I listed were: Boxing Glove, Martial Arts Uniform, and Drum with Drumsticks on the http://emojipedia.org/unicode-9.0/ pages. The Wiki page had numerous ones that did not display correctly. Also, most of the Flags here didn't render how one would expect: http://emojipedia.org/unicode-6.0/ Screenshot: http://i.imgur.com/dpV5A77.png
FF doesn't support Unicode 9.0 at the moment (bug 1281448).
Comment 3•8 years ago
|
||
Windows 7 hasn't color emoji font and it will use EmojiOne into browser/fonts. But EmojiOne doesn't support Unicode 9.0 glyph, so it doesn't render newer glyph. On Windows 10 Anniversary update has Unicode 9.0 font, so it can render it correctly.
Component: Internationalization → General
Product: Core → Firefox
See Also: → https://github.com/mozilla/fxemoji/issues/14
Updated•5 years ago
|
Component: General → Graphics: Text
Product: Firefox → Core
Comment 4•5 years ago
|
||
I guess that this is fixed at the latest version of Firefox since we update default emoji font. Does this still occur?
Flags: needinfo?(bugzilla)
What wasn't working is now working in 64, as far as what I linked to in this bug. I guess Unicode 11 will be the next one that needs to be added if possible: https://emojipedia.org/unicode-11.0/ (none render).
Flags: needinfo?(bugzilla)
Updated•5 years ago
|
Status: UNCONFIRMED → RESOLVED
Closed: 5 years ago
Resolution: --- → DUPLICATE
You need to log in
before you can comment on or make changes to this bug.
Description
•