Re: [csswg-drafts] [css-fonts-4] We can't add new values to the font-synthesis property

The CSS Working Group just discussed `can't add new values to font-synthesis`, and agreed to the following resolutions:

* `RESOLVED: change font-synthesis to all pairs of keywords and no-keywords`

<details><summary>The full IRC log of that discussion</summary>
&lt;fremy> Topic: can't add new values to font-synthesis<br>
&lt;fremy> github: https://github.com/w3c/csswg-drafts/issues/1641<br>
&lt;fremy> myles_: font-synthesis is a property that allows to turn on/off the font synthesis<br>
&lt;fremy> myles_: for example font-synthesis: weight allows to generate bolder variants<br>
&lt;fremy> myles_: by default you can synthetize everything<br>
&lt;fremy> myles_: the issue is that if you want to turn one on, you turn off all the other ones<br>
&lt;fremy> myles_: which means that new flags will be aciddentally turned off by older styles<br>
&lt;fremy> fantasai: we have a similar problem with text-decoration-skip<br>
&lt;fremy> fantasai: we decided to create sub longhands properties<br>
&lt;fremy> Florian: we don't have quite resolved that but ok<br>
&lt;fremy> fantasai: the other option is to only reset to false what you specify as off, but if you don't specify things we use the default<br>
&lt;fremy> Florian: wait, don't you want the reverse?<br>
&lt;fremy> fantasai: if you omit them, they default to true if true is the default, yes<br>
&lt;Rossen> !add<br>
&lt;fremy> fantasai: there was a proposal that was similar but used + and - in front of keywords<br>
&lt;fantasai> s/proposal/proposal from ChrisL/<br>
&lt;fremy> TabAtkins: text-decoration only allows to append new decoration styles but not remove inherited ones<br>
&lt;fremy> Florian: the reason we rejected the equivalent bold/no-bold for text-decoration because it cascades poorly which is the case for text decoration<br>
&lt;fremy> Florian: this is not quite the case for font-synthesis though so the option is still open now<br>
&lt;fremy> fantasai: given that we want to follow that pattern for other things like variant, I think we should do that as well<br>
&lt;fremy> fantasai: ... for font-synthesis<br>
&lt;fremy> myles_: this is my opinion as well<br>
&lt;fantasai> s/want to/already/<br>
&lt;fantasai> s/other things like /font-<br>
&lt;fremy> myles_: plus some rule that explains what happens if you ask both<br>
&lt;fremy> Florian: should we also also have no-everything?<br>
&lt;fremy> myles_: we can discuss this as part of another issue<br>
&lt;fantasai> s/do that/use the bold|no-bold pattern/<br>
&lt;fremy> alan: is this ok to make this change?<br>
&lt;fremy> myles_: we added font-caps and didn't see a problem<br>
&lt;fremy> myles_: but the window is closing of course, the more we add the more difficult it gets to change<br>
&lt;fremy> alan: so, proposed resolution is to use pair-keywords values for this property<br>
&lt;fremy> alan: any objection?<br>
&lt;fremy> RESOLVED: change font-synthesis to all pairs of keywords and no-keywords<br>
&lt;fremy> fantasai: do we need to change text level 3?<br>
&lt;fremy> myles_: don't think so<br>
&lt;fantasai> s/text/fonts/<br>
&lt;myles_> https://github.com/w3ctag/design-reviews/issues/183<br>
</details>


-- 
GitHub Notification of comment by css-meeting-bot
Please view or discuss this issue at https://github.com/w3c/csswg-drafts/issues/1641#issuecomment-319947707 using your GitHub account

Received on Thursday, 3 August 2017 11:53:43 UTC