W3C home > Mailing lists > Public > public-css-archive@w3.org > July 2018

Re: [csswg-drafts] [css-text] [css-fonts] Variation selectors are underspecified

From: CSS Meeting Bot via GitHub <sysbot+gh@w3.org>
Date: Tue, 03 Jul 2018 07:50:31 +0000
To: public-css-archive@w3.org
Message-ID: <issue_comment.created-402045813-1530604230-sysbot+gh@w3.org>
The Working Group just discussed `Variation selectors are underspecified`.

<details><summary>The full IRC log of that discussion</summary>
&lt;fantasai> Topic: Variation selectors are underspecified<br>
&lt;fantasai> github: https://github.com/w3c/csswg-drafts/issues/854<br>
&lt;frremy> (koji to read the issue, as he doesn't remember commenting on it)<br>
&lt;frremy> myles: there isn't a proposal, it's more of a discussion topic<br>
&lt;frremy> fantasai: the question is that there is a text<br>
&lt;frremy> fantasai: and the main font supports the base char, not the variation selector<br>
&lt;frremy> fantasai: the fallback font supports both<br>
&lt;frremy> fantasai: do you fallback or not?<br>
&lt;frremy> myles: there are two special ones that doesn't need font fallback<br>
&lt;frremy> myles: but unicode doesn't support font-fallback<br>
&lt;frremy> koji: it seems reasonable to make 15 and 16 specials<br>
&lt;frremy> myles: they should affect fallback<br>
&lt;frremy> myles: they should match together<br>
&lt;frremy> fantasai: so you must match a font that supports both<br>
&lt;frremy> myles: correct<br>
&lt;frremy> myles: the way we implemented this is that when you have a color indicator<br>
&lt;frremy> myles: we will only search color fonts<br>
&lt;frremy> myles: if there is a font that supports the glyph but not the color variations, we will skip it<br>
&lt;frremy> myles: it's not that I'm proposing this, because each OS might do this differently, but this is a reference to keep in mind<br>
&lt;frremy> fantasai: for cjk, there is the option of doing a two-pass behavior or a single-pass variant<br>
&lt;frremy> fantasai: but there seems to be use cases for both<br>
&lt;frremy> florian: for instance an ID name want to right char<br>
&lt;frremy> fantasai: but as a designer, you want to stay with the same font, and dropping the variation is better<br>
&lt;frremy> florian: I recall discussing this at the first meeting I ever attended<br>
&lt;frremy> florian: that was long ago<br>
&lt;frremy> myles: I don't think we are going to make any progress on this issue<br>
&lt;frremy> myles: we should probably switch<br>

GitHub Notification of comment by css-meeting-bot
Please view or discuss this issue at https://github.com/w3c/csswg-drafts/issues/854#issuecomment-402045813 using your GitHub account
Received on Tuesday, 3 July 2018 07:50:35 UTC

This archive was generated by hypermail 2.4.0 : Tuesday, 5 July 2022 06:41:33 UTC