Open Bug 1509988 Opened 6 years ago Updated 4 months ago

Noto Color Emoji is partially used


(Core :: Graphics: Text, defect, P5)

63 Branch




(Reporter: pachoramos1, Unassigned)




(Keywords: fonts)

User Agent: Mozilla/5.0 (X11; Linux x86_64) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/70.0.3538.102 Safari/537.36

Steps to reproduce:

This comes from

In summary, with Google Chrome and Firefox, sometimes some emojis are shown with Noto Color Emoji while others are shown with the old B&W style.

For example you can see many examples simply looking to the comments of many youtube videos as people seems to like to use a lot of emojis on them and you can see some use Noto Color Emoji while others not: (and many other random examples)

Looking to "Inspect element" Firefox tool, in "Fonts" section, I see that "Dejavu Sans" is being used to show emojis instead of Noto Color Emoji. I have seen that current default /etc/fonts/conf.avail/60-generic.conf only sets Noto Color Emoji for emoji while, probably, it should also be listed for other "families" to be used over ugly emoji fonts from other font sets.

I suggested that to fontconfig people, but they disagree and think that it's an issue in the application instead:

Probably a duplicate of bug 1323050.
Component: Untriaged → Graphics: Text
Keywords: fonts
OS: Unspecified → Linux
Product: Firefox → Core
Hardware: Unspecified → x86_64
Since Official binary has Twemoji Mozilla, most emoji characters use Twemoji Mozilla instead of Noto Color Emoji.  When you want OS configuration for emoji, it is bug 1424675 (or you set by about:config) for fontconfig 2.12.6+.
Then, why am I still getting some fonts rendered with B&W Dejavu Fonts instead of Twemoji Mozilla? I don't care about Noto Color Emoji or Twemoji being used, but the main issue is that some emojis are being shown with Twemoji while others with the B&W from system fonts :/

As a side note, this are the reports for Chrome and Webkit GTK: (contains more information from fontconfig maintainer and suggestions about how to solve it)

Ever confirmed: true
Priority: -- → P5

This was finally fixed in WebkitGTK :)

Severity: normal → S3
You need to log in before you can comment on or make changes to this bug.