- From: Lea Verou via GitHub <sysbot+gh@w3.org>
- Date: Thu, 26 Aug 2021 13:02:48 +0000
- To: public-css-archive@w3.org
> > Do note that instead of `unicode-range` (which would be a pain, I agree), one could also use `not` in `@supports` instead of having a bare `@font-face` as the fallback. > > Yes, using `@supports not ...` would avoid this. That gets a bit cumbersome in complex cases: e.g. if there are two or three color-font techologies being queried, as well as variations and a couple of shaping technologies, the `@supports` rule wrapping the fallback that doesn't support any of these could become pretty unwieldy. One way to make this easier would be to define aliases like `color-any` or `color-COLR` (which encompasses both v0 and v1). -- GitHub Notification of comment by LeaVerou Please view or discuss this issue at https://github.com/w3c/csswg-drafts/issues/6520#issuecomment-906392822 using your GitHub account -- Sent via github-notify-ml as configured in https://github.com/w3c/github-notify-ml-config
Received on Thursday, 26 August 2021 13:02:53 UTC