- From: Roman Komarov via GitHub <sysbot+gh@w3.org>
- Date: Fri, 31 Jul 2020 10:11:39 +0000
- To: public-houdini-archive@w3.org
Why have defaults anywhere then? Why gradients have a default direction? Borders — default thickness? backgrounds — default repeat? And so on? Or these were CSS design mistakes and if these would be designed today it would be different? What are other places in CSS that require explicitness, especially on the level of whole declarations? And not just one required declaration — the need to have four different ones, without a shorthand, just to enable any of these declarations? Right now custom properties registration can be used for these features: 1. Enabling transitions/animations. 2. Preventing inheritance. 3. Providing a default value. These features are not connected, but we can't use any one of them without explicitly mentioning the others. In my this coupling is unnecessary and introduces an extra barrier for usage of any of these, and an extra potential for a mistake or a type, where a mistake in one declaration makes the whole thing incorrect, which kinda goes against what CSS is currently is. -- GitHub Notification of comment by kizu Please view or discuss this issue at https://github.com/w3c/css-houdini-drafts/issues/994#issuecomment-667046603 using your GitHub account -- Sent via github-notify-ml as configured in https://github.com/w3c/github-notify-ml-config
Received on Friday, 31 July 2020 10:11:41 UTC