- From: Guillaume via GitHub <sysbot+gh@w3.org>
- Date: Mon, 15 Jul 2024 03:57:17 +0000
- To: public-css-archive@w3.org
I hope it is fine not top open a separate issue, but the same problem applies to `<type()>`: - in [CSS Mixins](https://drafts.csswg.org/css-mixins-1/#typedef-type): `type( <syntax> )` - in [CSS Images 4](https://drafts.csswg.org/css-images-4/#funcdef-image-set-type): `type( <string> )` If production rules should have context-insensitive value definitions, a solution could be to use an inline `type()` definition (like in CSS Images): `<css-type> = <syntax-component> | type( <syntax> )`. -- GitHub Notification of comment by cdoublev Please view or discuss this issue at https://github.com/w3c/csswg-drafts/issues/10557#issuecomment-2227660869 using your GitHub account -- Sent via github-notify-ml as configured in https://github.com/w3c/github-notify-ml-config
Received on Monday, 15 July 2024 03:57:18 UTC