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

Re: [csswg-drafts] [css-fonts] value of `font-style`: `normal` vs. `oblique 0deg; `

From: CSS Meeting Bot via GitHub <sysbot+gh@w3.org>
Date: Wed, 11 Apr 2018 15:00:28 +0000
To: public-css-archive@w3.org
Message-ID: <issue_comment.created-380484089-1523458825-sysbot+gh@w3.org>
The Working Group just discussed `(distinction -- or not -- between 'oblique 0deg' and 'normal' for font-style)`, and agreed to the following resolutions:

* `RESOLVED: leave font-style computed values as-is; change font-style animation behavior so that 'normal' can animate with 'oblique <num>'`

<details><summary>The full IRC log of that discussion</summary>
&lt;dael> Topic: (distinction -- or not -- between 'oblique 0deg' and 'normal' for font-style)<br>
&lt;ChrisL> apropriate means weight, style, stretch<br>
&lt;dael> github: https://github.com/w3c/csswg-drafts/issues/2505<br>
&lt;dael> dbaron: The spec for font styles says normal represents an oblique value of 0.<br>
&lt;dael> dbaron: Jonathan writes it's not clear to him what this means [reads from issue]. HIs test shows chrome and edge disagrees.<br>
&lt;dael> jpamental: There's two variations<br>
&lt;dael> ChrisL: It's the slant one. His point is valid is if it's the same as 0 you have the endpoints of the animation. I think oblique:0 should match.<br>
&lt;dael> myles: ChrisL is right. We impl that it's just a number becasue we treat italic and oblique the same. So normal = oblique 0deg.<br>
&lt;dael> fantasai: Computed value?<br>
&lt;dael> myles: Prob the keyword? DOn't know.<br>
&lt;dael> fantasai: Matters for animations.<br>
&lt;dael> myles: Sure then we make computed values always the oblique. Question is what is the coputed value of the font style property. If computed value is normal for ital you can't animate.<br>
&lt;dael> TabAtkins: You can animate from oblique 0.<br>
&lt;dael> myles: Computed value of normal should be oblique 0. Computed value of oblique with nothing...<br>
&lt;dael> fantasai: I don't htink it' sbackwards compat.<br>
&lt;dael> fantasai: Computed value shoulds tay the same.<br>
&lt;dael> TabAtkins: We can also make the animation value handle that.<br>
&lt;dael> myles: Is there precedent for that?<br>
&lt;dael> TabAtkins: Sure we can make it work.  We have special behavior for transforms from none<br>
&lt;dael> myles: This is the same.<br>
&lt;dael> myles: SO we'll punt<br>
&lt;dael> TabAtkins: Change animation so that normal can animate with oblique as if normal is 0.<br>
&lt;dael> fremy: And if you put 0 in your style sheet computed value is 0.<br>
&lt;dael> TabAtkins: Some UA map italic to oblique and if they do so they should be able to animate between italic and oblique.<br>
&lt;dael> fantasai: A variable font with both italic and oblique axis and I spec font-style italic<br>
&lt;dael> myles: We keep a flaot for the oblique angle and we keep a bit to know if that came from oblique or italic axis.<br>
&lt;dael> fantasai: isn't it 2d pspace?<br>
&lt;dael> myles: It's just not a variable thing.<br>
&lt;dael> fantasai: Can variable fonts have variable italic?<br>
&lt;dael> ChrisL: No.<br>
&lt;dael> jpamental: Intent was italic to be on or off.<br>
&lt;dael> florian: If you want a font to have stanges between you have a custo axis?<br>
&lt;dael> ChrisL: Yes.<br>
&lt;dael> fantasai: So you have parallel tracks<br>
&lt;dael> ChrisL: You can have a custom axis and then it doesn't inteset with CSS properties.<br>
&lt;dael> myles: mechanically it's possible to have fonts that do that but many experts have not seen a variable angle of italic.<br>
&lt;dael> jpamental: Italic is either ital or not, it's not a degree of ital.<br>
&lt;dael> fantasai: All writing systems?<br>
&lt;dael> ChrisL: Most don't have ital.<br>
&lt;dael> dbaron: Trying to understand in font matching algo of 5.2 bullet 4 sub bullet 2.<br>
&lt;dbaron> If the value of font-style is oblique and the requested angle is greater than or equal to 0deg and less than 20deg,<br>
&lt;dael> dbaron: It's about font style. The 3rd unnumbered sub clause. Sentence starts with ^<br>
&lt;dael> dbaron: This includes an oblique font 0deg. THis is sep from normal clause and it's not clear to me if sub point 2 includes normal fonts.<br>
&lt;dael> dbaron: It says if it's oblique and the angle is >=0 and &lt;20 if you have an exact match use that but if yo have smaller look down to 0. It doesn't say if it include 0 and, if it does, if it's normal 0.<br>
&lt;dael> myles: Do we need a resolutoin to make it more clear?<br>
&lt;dael> dbaron: I think it's fine if you just clear the spec up.<br>
&lt;dael> astearns: We've got the proposed resolution that TabAtkins put: leave font-style computed values as-is; change font-style animation behavior so that 'normal' can animate with 'oblique &lt;num>'; if the UA treats 'italic' as an oblique value, also allow it to animate with 'oblique &lt;num>'.<br>
&lt;dael> astearns: Objections or issues with it?<br>
&lt;dael> ChrisL: sgtm<br>
&lt;dael> myles: cool.<br>
&lt;dael> fantasai: We have UA defined behavior in the resolution and I don't like it.<br>
&lt;dael> astearns: It's reiterating behavior we have<br>
&lt;dael> fantasai: Changes to if you can anmate it.<br>
&lt;dael> fantasai: I'm not sure what's going on with the ones that can annimate and not.<br>
&lt;dael> myles: I think it's if you are a browser that treats oblique and ital as the same you should be able to animate between. If not you can't.<br>
&lt;dael> florian: I'm not sure about that. The author chooses ital, why animate?<br>
&lt;dael> TabAtkins: Some browsers don't distinguish.<br>
&lt;dael> fantasai: But then they can't tell which they should download. Seems like a problem. If I said ital I should get ital first.<br>
&lt;dael> many: not how it works.<br>
&lt;dael> fantasai: As an author I'll never get italic?<br>
&lt;dael> florian: In some browsers, yes.<br>
&lt;dael> myles: There's one signal.<br>
&lt;dael> myles: You'll get something consistant if they're both there.<br>
&lt;dael> fantasai: I load a font with an ital variant and an oblique varient and I can only get one. Why is this good?<br>
&lt;dael> myles: It's how it's always been.<br>
&lt;dael> fremy: This was in css 2.<br>
&lt;dael> astearns: We can choose not to extend.<br>
&lt;dael> ChrisL: Do browsers do this? Treat them as identical?<br>
&lt;fantasai> https://www.w3.org/TR/CSS2/fonts.html#font-styling<br>
&lt;dael> myles: The bit doesn't effect font selection, it's only to have the right axis.<br>
&lt;dael> astearns: I suggest we take the proposal and strike the UA part<br>
&lt;dael> Prop: leave font-style computed values as-is; change font-style animation behavior so that 'normal' can animate with 'oblique &lt;num>'<br>
&lt;dael> astearns: Objections?<br>
&lt;fantasai> “A value of 'italic' selects a font that is labeled 'italic', or, ****if that is not available****, one labeled 'oblique'.”<br>
&lt;dael> RESOLVED: leave font-style computed values as-is; change font-style animation behavior so that 'normal' can animate with 'oblique &lt;num>'<br>
</details>


-- 
GitHub Notification of comment by css-meeting-bot
Please view or discuss this issue at https://github.com/w3c/csswg-drafts/issues/2505#issuecomment-380484089 using your GitHub account
Received on Wednesday, 11 April 2018 15:00:32 UTC

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