- From: Guillaume via GitHub <sysbot+gh@w3.org>
- Date: Tue, 29 Nov 2022 13:03:02 +0000
- To: public-css-archive@w3.org
> Are you referring to the `<string>` production? Yes. Should it be invalid in `@supports` but valid in `src` for `@font-face`? If so, I will close my PR but I think it should be defined in prose (more simple) or in the syntax. I think rewriting the syntax would require to not define `font-tech()` as a type (`<font-tech()> = ...`) but as a context-sensitive function (`font-tech() = ...`). I did not check the result [in Bikeshed](https://api.csswg.org/bikeshed/), which reports an error for duplicate type refs of `<font-tech>` in CSS Conditional 5 and CSS Fonts 5, and generates a link to CSS Fonts 5 for `<font-format>`. I do not know well how it works in details and I do not really understand why it generates a link to CSS Fonts 5 for `<font-format>` but not `<font-tech>`. -- GitHub Notification of comment by cdoublev Please view or discuss this issue at https://github.com/w3c/csswg-drafts/issues/8110#issuecomment-1330621788 using your GitHub account -- Sent via github-notify-ml as configured in https://github.com/w3c/github-notify-ml-config
Received on Tuesday, 29 November 2022 13:03:11 UTC