WebKit Bugzilla
New
Browse
Log In
×
Sign in with GitHub
or
Remember my login
Create Account
·
Forgot Password
Forgotten password account recovery
NEW
196299
Incompatibility with emoji-one-mozilla Fontconfig. Weird Spaces
https://bugs.webkit.org/show_bug.cgi?id=196299
Summary
Incompatibility with emoji-one-mozilla Fontconfig. Weird Spaces
Griffin
Reported
2019-03-27 09:24:41 PDT
Hi there, So a few days back I filed a bug with Geary Email, which ended up being a webkit rendering bug. You can see the report here
https://gitlab.gnome.org/GNOME/geary/issues/328
After doing some digging of my own, I found out that the issue came down to fonts.conf and the way I was allowing Firefox to display my emoji font, as the way they do it is different than the way that everyone else does it. Why? I don't really know. I found that the match config that broke webkit, but fixed Firefox emojis was , and <match> <test name="family"> <string>sans-serif</string> </test> <edit name="family" binding="strong" mode="prepend"> <string>Noto Color Emoji</string> </edit> </match> If this match is enabled, emojis will work in Firefox, but will cause the weird text spacing as seen in the bugreport above. If the line is removed, the font spacing will work fine, but emojis in Firefox will not work. My guess is that there are a few solutions. One is me being dumb and needing a better match to make both webkit and firefox happy. Another that is less likely is to have firefox use the standard that like everyone else is using, which would be a different bug report. The last is that there is something wrong with how Webkit is rendering this emoji font (I am using Fedora's twemoji package seen here
https://aur.archlinux.org/packages/ttf-twemoji/
), and that this match should not be breaking the text spacing if it was handled properly. Please let me know what the best solution is! Thank you so much!
Attachments
Add attachment
proposed patch, testcase, etc.
Note
You need to
log in
before you can comment on or make changes to this bug.
Top of Page
Format For Printing
XML
Clone This Bug