- From: Christopher Kirk-Nielsen via GitHub <sysbot+gh@w3.org>
- Date: Mon, 01 Aug 2022 21:22:31 +0000
- To: public-css-archive@w3.org
I am not privy to the parsing but it seems you want to declare scoped custom properties, per selector, and I am not sure that's possible with the `@property` rule. Maybe some new stuff in the spec regarding container queries or scoping would enable this but I honestly do not know. Additionally, in your proposed form, the browser has no way to know the difference between a custom property value and custom property registration, since `--foo: color brown;` is a totally valid custom property value in itself. That is also a bit different from your initial proposal in some ways so I am not sure it's viable in its latest form, but still believe the one-line syntax `@property --foo...` could be exploited (`@property --foo, --bar as '<syntax>' initialValue` would be my preferred approach but that's another discussion). -- GitHub Notification of comment by chriskirknielsen Please view or discuss this issue at https://github.com/w3c/csswg-drafts/issues/7523#issuecomment-1201736270 using your GitHub account -- Sent via github-notify-ml as configured in https://github.com/w3c/github-notify-ml-config
Received on Monday, 1 August 2022 21:22:33 UTC