Re: [csswg-drafts] [css-fonts-4] Computed value for shorthand font: should describe serialization for font-variant-css21 and font-stretch-css3

The CSS Working Group just discussed `Computed value for shorthand font: should describe serialization for font-variant-css21 and font-stretch-css3`, and agreed to the following:

* `RESOLVED: Have computed value always be a percentage and have serialization always show a percentage. Neither deal with keywords`

<details><summary>The full IRC log of that discussion</summary>
&lt;dael> Topic: Computed value for shorthand font: should describe serialization for font-variant-css21 and font-stretch-css3<br>
&lt;dael> github: https://github.com/w3c/csswg-drafts/issues/1671#issuecomment-400863224<br>
&lt;dael> myles: There's...the issue here recently has migrated. The  thing discussed now is the font-stretch<br>
&lt;dael> myles: In L3 font-stretch took keywords. In L4 they're % number so you can animate. That's for variable fonts.<br>
&lt;dael> myles: Issue is about how the computed style of this property should be a number of % rather then keyword or a number<br>
&lt;dael> myles: If you're trying to animated from condenced to 139% if computed is % o r keyword you can't animate. Solution is always a number and getcomputedstyle function returns strings if the computed style is a magic number we define<br>
&lt;florian> the explanation did make sense<br>
&lt;dael> astearns: Are magic number spec orimpl dependent?<br>
&lt;dael> myles: There's a table<br>
&lt;chris> its the magic numbers that correspond to the keywords<br>
&lt;dael> myles: Not much of an issue, it's do you want to animate from keyword to number. If yes, and I think it's yes, we need backwards compat<br>
&lt;dael> florian: Makes total sense to me<br>
&lt;chris> +1 this seems good to me<br>
&lt;dael> astearns: me too<br>
&lt;dael> emilio: Serialize as number?<br>
&lt;dael> myles: We're discussing now if computed style of font-stretch shoudl b e a number or as specified.<br>
&lt;dael> emilio: Gecko and blink ship as number so web compat not problem.<br>
&lt;dael> myles: Backwards is gCS. If you set font-stretch to a value that used to be a keyword do you get numebr or keyword<br>
&lt;dael> emilio: number<br>
&lt;dael> chris: It's serialization of gCS and I think there's web compat on that<br>
&lt;dael> myles: I guess there isn't much web compat if blink and gecko give number.<br>
&lt;dael> florian: We can start with that and ifthere is web compat revisit<br>
&lt;dael> astearns: Perhaps a note in the draft saying may be web compat with always serialize as number and may need magic conversion at some point.<br>
&lt;dael> florian: Reasonable<br>
&lt;fremy> +1<br>
&lt;dael> astearns: Anyone with evidence that we need magic number to string conversion in gCS?<br>
&lt;dael> astearns: Prop: Have computed value always be a percentage and have serialization always show a percentage. Neither deal with keywords<br>
&lt;dael> astearns: Objections?<br>
&lt;dael> RESOLVED: Have computed value always be a percentage and have serialization always show a percentage. Neither deal with keywords<br>
</details>


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

Received on Wednesday, 29 August 2018 16:09:29 UTC