- From: Oriol Brufau via GitHub <sysbot+gh@w3.org>
- Date: Sat, 15 Oct 2022 19:56:47 +0000
- To: public-css-archive@w3.org
I think this can be considered as 2 different proposals:
- Being able to define value aliases for a custom property
So e.g. you can have a custom property `--button-text-color` with syntax `<color>`, but then define the aliases `--normal = #000` and `--disabled = #6d6d6d`. So then you can have things like
```css
button:disabled { --button-text-color: --disabled }
button.disabled { --button-text-color: --disabled }
```
if for some reason you want to avoid a selector list, without having to repeat or remember `#6d6d6d`.
This would be similar to ` --button-text-color: var(--disabled)` with `--disabled: #6d6d6d`, but without exposing `--disabled` to all properties.
Aliases should probably not be allowed on properties with syntax `*`, they should be dashed idents to avoid ambiguities (e.g. `<color>` accepts idents), and they shouldn't be combined with other values.
- Being able to define a custom property as a basic shorthand
Just redirecting the provided values to different properties. No transformation of values nor complex things. The longhands should probably be custom properties too.
And then you could use them together.
--
GitHub Notification of comment by Loirooriol
Please view or discuss this issue at https://github.com/w3c/csswg-drafts/issues/7879#issuecomment-1279822580 using your GitHub account
--
Sent via github-notify-ml as configured in https://github.com/w3c/github-notify-ml-config
Received on Saturday, 15 October 2022 19:56:49 UTC