Re: [csswg-drafts] [css-fonts] avoid fallback from oblique to italic (#9389)

The CSS Working Group just discussed `[css-fonts] avoid fallback from oblique to italic`, and agreed to the following:

* `RESOLVED: Disallow fallback from oblique to italic. Also, unless synthesis is prevented, synthesize oblique from normal font when oblique is requested.`

<details><summary>The full IRC log of that discussion</summary>
&lt;TabAtkins> florian: currently we define that if the user requests eitehr italic or oblique, and you dont' have one, you give them the other<br>
&lt;TabAtkins> florian: unless you've opted out like we've just discussed, i think falling back from italic to oblique is reasonable. less convinced falling back from oblique to italic is reasoanble. but we do both ways.<br>
&lt;TabAtkins> florian: because italic has the fallback, and it's what people usually know about, they'll usually ask for italic. And if there's no italic they'll get oblique, which is what they wanted anyway.<br>
&lt;TabAtkins> florian: But if you specifically asked for oblique, I think you should get oblique, not fall back to italic.<br>
&lt;TabAtkins> florian: and unless I'm confused, we have two levels of falling back - we try this first, and if it doesn't work we use the font stack<br>
&lt;ChrisL> q+<br>
&lt;TabAtkins> florian: result is if you ask for oblique, find the font, it has normal and italic, you get italic. you dont' search further for an oblique.<br>
&lt;TabAtkins> jfkthame: i'd argued we shoudl be synthing an oblique from the regular at that point.<br>
&lt;TabAtkins> florian: agree. synth oblique instead of natural oblique is reasonable.<br>
&lt;ChrisL> So we would delete "For the purposes of font matching, User agents may treat italic as a synonym for oblique."<br>
&lt;TabAtkins> florian: currently we dont' do that if italic is avaialbe. we should jsut synth oblique instead as you asked.<br>
&lt;astearns> ack ChrisL<br>
&lt;TabAtkins> ChrisL: I agree we shoudl synth oblique<br>
&lt;TabAtkins> ChrisL: we have language in the spec that says [quote above]<br>
&lt;TabAtkins> ChrisL: that's a stupid thing to say, we shoudl delete that sentence<br>
&lt;TabAtkins> astearns: i'm looking nthru the issue, we had a previous proposed resolution to not allow fallback between italic and oblique, and that failed to get consensus. what does that mean?<br>
&lt;TabAtkins> florian: Chris, you mentioend resistence, but cited my comment and I wasn't resisting<br>
&lt;ChrisL> https://github.com/w3c/csswg-drafts/issues/9389#issuecomment-2049382909<br>
&lt;TabAtkins> ChrisL: it was domenic that had the objection<br>
&lt;TabAtkins> s/domenic/drott/<br>
&lt;TabAtkins> astearns: in my reading, part of his problem is the proposed reoslution only removed the fallback oblique->italic, and didn't mention we shoudl be synthing oblique rather than doing stack fallback<br>
&lt;TabAtkins> astearns: so a resolution that says "if you ask for oblique and the first matching font doesn't have it, synthesize it" and not allowing fallback from oblique to italic<br>
&lt;TabAtkins> astearns: jfkthame, that make sense?<br>
&lt;TabAtkins> jfkthame: i think so<br>
&lt;TabAtkins> astearns: shall we try that resolution?<br>
&lt;TabAtkins> proposed resolution: above<br>
&lt;TabAtkins> RESOLVED: Disallow fallback from oblique to italic. Also, unless synthesis is prevented, synthesize oblique from normal font when oblique is requested.<br>
</details>


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


-- 
Sent via github-notify-ml as configured in https://github.com/w3c/github-notify-ml-config

Received on Thursday, 30 January 2025 18:51:55 UTC