- From: Dominik Röttsches via GitHub <sysbot+gh@w3.org>
- Date: Thu, 11 Apr 2024 13:13:50 +0000
- To: public-css-archive@w3.org
> What I think we need is a system where if italic is missing, authors can chose whether to fall back to oblique or not, and if yes, synthetic oblique is always acceptable when non-synthetic oblique is not available. Also, we might want an ability to turn off synthetic oblique when `font-style: oblique` has been requested, though I doubt there's much demand for that. Generally, I am not sure how urgent of an issue this is, if authors control the content, they can control that just with providing the right web fonts, attributing the web fonts with the correct `font-style:` descriptors and setting `font-synthesis-style: none;` and then using either only `italic` or `oblique` for styling. I have not seen more than one font family (and that was a test font) that both has an oblique and an italic style. I am not in favor of re-purposing font-synthesis-x: for influencing font matching, I find that an architecturally strange side effect of a property. Fallback is not the same as synthesis. In that case, I'd rather see us make a choice and change the font matching algorithm to not perform fallback from italic to oblique, even if that's a breaking change. Perhaps we can assess the impact of that. Agree that font-synthesis: none should not add slant when the variable axis range is exhausted - but I think that's already spec'ed. -- GitHub Notification of comment by drott Please view or discuss this issue at https://github.com/w3c/csswg-drafts/issues/9390#issuecomment-2049668236 using your GitHub account -- Sent via github-notify-ml as configured in https://github.com/w3c/github-notify-ml-config
Received on Thursday, 11 April 2024 13:13:50 UTC