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

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

From: CSS Meeting Bot via GitHub <sysbot+gh@w3.org>
Date: Tue, 03 Jul 2018 07:43:35 +0000
To: public-css-archive@w3.org
Message-ID: <issue_comment.created-402044040-1530603814-sysbot+gh@w3.org>
The Working Group just discussed `font-synthesis forwards-compat with new values`, and agreed to the following:

* `RESOLVED: move font-synthesis to long-hands, and simplify the shorthand`

<details><summary>The full IRC log of that discussion</summary>
&lt;fantasai> Topic: font-synthesis forwards-compat with new values<br>
&lt;fantasai> github: https://github.com/w3c/csswg-drafts/issues/1641<br>
&lt;frremy> fantasai: at a f2f we resolve to change font-synthesis to invert the behavior since we change from you have to specify what you want to synthetize<br>
&lt;frremy> fantasai: to specify instead what you don't want to synthetize<br>
&lt;frremy> fantasai: wanted to clarify the resolution<br>
&lt;frremy> myles: not much thought, except I'd not want to break existing content<br>
&lt;frremy> astearns: but are you fine with the resolution?<br>
&lt;frremy> TabAtkins: (discussion about what rule maps to the spec)<br>
&lt;frremy> fantasai: the table doesn't help with forwards-compat<br>
&lt;frremy> fantasai: the current behavior if you don't specify font-synthesis which allows weight+style+font-caps<br>
&lt;astearns> s/the resolution/tab's table/<br>
&lt;frremy> fantasai: if you say font-synthesis: weight you already weight+font-caps<br>
&lt;frremy> TabAtkins: the table is meant to ease the compat<br>
&lt;frremy> TabAtkins: font-caps is not a legacy value<br>
&lt;frremy> TabAtkins: unspecified parts of the property default to on/off depending on legacy requirements<br>
&lt;frremy> florian: we had a similar discussion with font-...-skip and we had settled on a shorthand<br>
&lt;frremy> chris_: we can keep adding long-hands as we see fit<br>
&lt;frremy> florian: I think this is the only sane thing to do<br>
&lt;frremy> myles: then we can use Tab's table for the shorthand<br>
&lt;frremy> myles: ok, so the proposal is to have three properties "font-synthesis-weight, font-synthesis-style, etc..."<br>
&lt;frremy> myles: three values, each should have default to "auto" and "none", two first one are auto, last one is none<br>
&lt;frremy> fantasai: I don't like font-synthesis no-caps disable everything<br>
&lt;frremy> myles: since nobody implemented font-caps, we get rid of them in the shorthand<br>
&lt;frremy> myles: so the problem just disappears<br>
&lt;TabAtkins> s/font-caps/small-caps/<br>
&lt;TabAtkins> font-synthesis: all | none | [weight || style], with effects as in my table<br>
&lt;myles> Proposal: 3 new properties: font-synthesis-weight, font-synthesis-style, and font-synthesis-small-caps, all with grammar "auto | none" with initial values "auto", all inherited, and the "small-caps" "no-small-caps" and "no-style" and "no-weight" values are removed from the font-synthesis grammar, and the no<br>
&lt;astearns> 'as in my table' could also be 'as currently specified in fonts-3'<br>
&lt;myles> s/and the no//<br>
&lt;frremy> (joke on a "force synthesis" option)<br>
&lt;TabAtkins> "joke"<br>
&lt;frremy> astearns: any objection on the proposal as stated in irc<br>
&lt;frremy> RESOLVED: move font-synthesis to long-hands, and simplify the shorthand<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-402044040 using your GitHub account
Received on Tuesday, 3 July 2018 07:43:42 UTC

This archive was generated by hypermail 2.3.1 : Tuesday, 3 July 2018 07:43:42 UTC