- From: Joël Galeran via GitHub <sysbot+gh@w3.org>
- Date: Wed, 11 Apr 2018 15:58:44 +0000
- To: public-css-archive@w3.org
Thanks @litherum for opening the issue ;-) _This issue is related with the color font `format()` specifier: https://github.com/w3c/csswg-drafts/issues/633_ Based on creatives’ feedback regarding the use of color fonts on the web, there are cases when color fonts will lack of a viable fallback design, which will require specific layout adjustments. For instance: 1. The color font may have been designed without any fallback glyphs 2. The fallback glyphs may be irrelevant (i.e. when fallback glyphs are automatically created: a colored alphabet that fits within square shapes would be converted into illegible black squares) 3. The fallback font may require different CSS styling (i.e. when its metrics are different from the color font) In these cases, adding a feature detection of font formats (including color) would give web designers greater control over the fallback experience - specially during the transition phase until broad color font support is reached. One potential solution could be to leverage `@supports` to identify the supported font flavors (this would be handy for both color and variable fonts). One could argue that a fallback font should always be designed and match the color version, but from a creative’s standpoint, some color fonts will simply never have a fallback version (for aesthetic or practical reasons, as the the complexity and amount of work needed to create a color font with its fallback would prevent many to venture into color font creation). What do you think? -- GitHub Notification of comment by Jolg42 Please view or discuss this issue at https://github.com/w3c/csswg-drafts/issues/2540#issuecomment-380504843 using your GitHub account
Received on Wednesday, 11 April 2018 15:58:53 UTC