- From: Dominik Röttsches via GitHub <sysbot+gh@w3.org>
- Date: Mon, 03 Apr 2023 11:59:03 +0000
- To: public-css-archive@w3.org
I agree with @dbaron that lack of feature detection is a problem for use of `font-variation-position`. I admit I am mainly looking at it from the perspective of how to make it more useful without automatic synthesis - as experience with bold and italic synthesis shows that these have often caused undesirable effects or have hidden issues with correct usage of @font-face (aside from being complex to implement).
Two questions:
1) Is the proposal here for `font-synthesis-position` to only affect synthesis behavior in `font-variant-position`? If so, let's clarify that. (vs. synthesis behavior for `<sub>`, `<sup>` - which I interpret to be unrelated from this proposed property.
2) As the two proposed values are only `auto | none`, what would be the canonical and reliable way to feature-detect that there is no synthesis for font-variant-position? Would `!CSS.supports('font-synthesis-position', 'auto')` mean that, or how would we reliably encode that? Or would it need to mean a UA not supporting synthesis for font-variant-position should better not implement this property altogether?
--
GitHub Notification of comment by drott
Please view or discuss this issue at https://github.com/w3c/csswg-drafts/issues/7441#issuecomment-1494188578 using your GitHub account
--
Sent via github-notify-ml as configured in https://github.com/w3c/github-notify-ml-config
Received on Monday, 3 April 2023 11:59:05 UTC