emoji variation sequence support is missing/incomplete
Categories
(Core :: Layout: Text and Fonts, defect)
Tracking
()
People
(Reporter: i, Unassigned)
Details
Attachments
(1 file)
User Agent: Mozilla/5.0 (X11; Linux x86_64; rv:67.0) Gecko/20100101 Firefox/67.0
Steps to reproduce:
Open https://unicode.org/Public/emoji/12.0/emoji-test.txt in Firefox
Search Japanese “secret” button
Actual results:
Many fully qualified emoji are not shown as emoji.
Expected results:
All fully qualified emoji should be shown as emoji, no matter what font family was specified. Emoji variation sequence should have higher priority than font-family property.
Comment 2•5 years ago
|
||
Mozilla/5.0 (X11; Ubuntu; Linux x86_64; rv:67.0) Gecko/20100101 Firefox/67.0
Hi,
I have tested your issue on latest FF release (68.0) and latest Nightly build 70.0a1 (2019-07-11) and could not reproduce it.
If the issue is still reproducible on your end, can you please retest this using latest FF release and latest Nightly build (https://nightly.mozilla.org/) and report back the results ? When doing this, please use a new clean Firefox profile (https://goo.gl/AWo6h8), maybe even safe mode (https://goo.gl/AR5o9d), to eliminate custom settings as a possible cause.
Further, I will move this over to a component so developers can take a look over it and give us an opinion about this issue. If is not the correct component please feel free to change it to an appropriate one.
Thanks for the report.
Updated•5 years ago
|
Updated•5 years ago
|
Comment 3•5 years ago
|
||
When the content is not explicitly styled with an emoji font, results will depend on the system's local font configuration; if the default text font happens to support emoji codepoints (even though it only has b/w glyphs), it will get used.
Better support for respecting the display style of default-emoji characters or explicit variation sequences (by selecting an appropriate color or non-color font, in preference to the default text font) is what bug 1371386 is about, so I'm dup'ing this there.
Hi Alin, to reporduce this issue, you need to have Noto Sans CJK fonts installed.
I agree with Jonathan, it is a duplicate of bug 1371386.
Description
•