- From: Mike Bremford via GitHub <sysbot+gh@w3.org>
- Date: Fri, 15 Jul 2022 11:24:47 +0000
- To: public-css-archive@w3.org
> Giving the descriptor precedence seems more reasonable, and also aligns with implementations. If others agree, that means Fonts 4 should be changed, Conveniently (as there's going to be a conversation on this) I would have gone the other way. As font-stylesheets seem to be commonly created by someone other than the document author (eg fonts.google.com), giving them precedence over any `font-variant` properties used in the main document stylesheet seems the wrong way around to me. It would force authors to use the `font-feature-settings` property to override the descriptor, which is too low-level. > That seems like a bug For context, `rlig`, `liga`, `clig`, `calt`, `locl`, `ccmp`, `mark`, `mkmk` are the only features on by default. `liga` and `clig` can be controlled by `font-variant-ligatures: common-ligatures` property, and `calt` can be controlled by `font-variant-ligatures: contextual`. So those three features the only ones where the current precedence rules would mean that setting them in the `font-feature-settings` descriptor would have no effect. It doesn't seem like a big issue to me, they're in this testcase but I can't imagine it happening much in the real world. The cases I imagine for the `font-feature-settings` descriptor aren't ligatures: they're default stylistic alternates or weird custom shaping rules, that sort of thing. But I'm preprared to be corrected on that. -- GitHub Notification of comment by faceless2 Please view or discuss this issue at https://github.com/w3c/csswg-drafts/issues/7498#issuecomment-1185450632 using your GitHub account -- Sent via github-notify-ml as configured in https://github.com/w3c/github-notify-ml-config
Received on Friday, 15 July 2022 11:24:49 UTC