3 ms·
Looks ok for me (Firefox 81 on Linux): https://i.imgur.com/7Pxmwyn.png https://i.imgur.com/7Pxmwyn.png
by uolot 6y ago
Looks ok for me (Firefox 81 on Linux): https://i.imgur.com/7Pxmwyn.png https://i.imgur.com/7Pxmwyn.png
- jefftk 6y agoFirefox 81 on Mac: https://imgur.com/a/JQGcfTQ https://imgur.com/a/JQGcfTQ Does not look good. It has something to do with the custom font. If I disable "font-family: AdobeSourceCodePro, monospace" the colors appear: https://imgur.com/a/mcUX5XD https://imgur.com/a/mcUX5XD
- jefftk 6y agoLooks like it's https://bugzilla.mozilla.org/show_bug.cgi?id=1520157 https://bugzilla.mozilla.org/show_bug.cgi?id=1520157: I think basically what's happening here is that the font includes some SVG glyphs (for a bunch of emoji, no doubt). This causes us to render it via a "color font" codepath, and color fonts ignore the CSS color property as the glyphs are painted with their inherent colors instead. But in this case many (most) of the glyphs do not actually have color versions, and so they simply paint as black. We need to be making the decision whether to paint "as a color font" (ignoring CSS color) on a per-glyph basis, not per-font-run, so that glyphs without inherent color don't just default to all-black all the time.