question-mark
Stuck on an issue?

Lightrun Answers was designed to reduce the constant googling that comes with debugging 3rd party libraries. It collects links to all the places you might be looking at while hunting down a tough bug.

And, if you’re still stuck at the end, we’re happy to hop on a call to see how we can help out.

SVG+COLRv1+CBDT font renders CBDT on Chrome Canary, COLRv1 only shows when no CBDT

See original GitHub issue

The BlakaInk-Regular.ttf font includes three color flavors: SVG (the SVG table), COLRv1 (the COLR and CPAL tables) and CBDT (the CBDT and CBLC tables).

The BlakaInk-Regular-color-multiflavor.zip contains the same font (as SVG-COLRv1-CBDT), and also a SVG-COLRv1 font where I removed the CBDT flavor with sfntedit -d CBDT,CBLC BlakaInk-Regular-SVG-COLRv1.ttf.

On my macOS 12.3.1:

Firefox 100.0b3

Firefox renders the SVG flavor for both fonts:

scr- 2022-04-12 at 12 53 22

Safari

Safari Technology Preview Release 143 (Safari 15.4, WebKit 17614.1.7.7), and Safari Version 15.4 (17613.1.17.1.13) render the SVG flavor for both fonts:

scr- 2022-04-12 at 12 53 27

Chrome Canary

Chrome Canary Version 102.0.4999.0 (Official Build) canary (x86_64) renders the low-res bitmap version (the CBDT flavor) for the SVG-COLRv1-CBDT font — that’s NOT GOOD:

scr- 2022-04-12 at 12 53 17

It only renders the vector COLRv1 flavor for the SVG-COLRv1 font, which does not contain the CBDT and CBLC tables:

scr- 2022-04-12 at 12 56 59

So Chrome needs to be fixed — it should give preference to COLRv1 flavor even if the CBDT flavor exists in the font.

I guess this is an issue that should be filed into the Chrome project, but I’m not sure how to do it. (Or perhaps this is already filed, but feel free to add a link to this very report there).

Issue Analytics

  • State:closed
  • Created a year ago
  • Comments:10 (2 by maintainers)

github_iconTop GitHub Comments

0reactions
rsheetercommented, Jul 28, 2022

In re-reading this I believe there is nothing to do for this issue in this repo, the work will be done on https://bugs.chromium.org/p/skia/issues/detail?id=12945. Closing, please reopen if you believe there is something to be done in nanoemoji wrt Chrome preference for CBDT over COLR.

Read more comments on GitHub >

github_iconTop Results From Across the Web

COLRv1 Color Gradient Vector Fonts in Chrome 98
Compact, compression-friendly, color vector fonts with all your favorite gradient flavors. In Chrome 98, the Chrome and Fonts teams have ...
Read more >
Intent to Ship: Variable COLRv1 - Google Groups
COLRv1 color vector fonts have been previously released in Chrome 98 ... side to ensure interoperability of the resulting variable COLRv1 glyph renderings....
Read more >
Shipping COLRv1 Color Vector Fonts in Chrome [BlinkOn 15]
Dominik Röttsches presenter: COLRv1 vector fonts are a new highly compact font format enabling breakthrough usage of color fonts on the web.
Read more >
Fix text that isn't displaying properly - Google Chrome Help
Text looks fuzzy or blurry (Windows only). If text doesn't look clear on your computer, try changing your font settings. Step 1: Use...
Read more >
Issues with Chrome - Smart Slider Documentation - Help Scout
In this article Fonts are pixelated or blurred Video layer's cover image isn't used There are no images in the lightbox Layer animation...
Read more >

github_iconTop Related Medium Post

No results found

github_iconTop Related StackOverflow Question

No results found

github_iconTroubleshoot Live Code

Lightrun enables developers to add logs, metrics and snapshots to live code - no restarts or redeploys required.
Start Free

github_iconTop Related Reddit Thread

No results found

github_iconTop Related Hackernoon Post

No results found

github_iconTop Related Tweet

No results found

github_iconTop Related Dev.to Post

No results found

github_iconTop Related Hashnode Post

No results found