- From: Tab Atkins Jr. via GitHub <sysbot+gh@w3.org>
- Date: Fri, 31 Jul 2020 16:13:37 +0000
- To: public-houdini-archive@w3.org
> Why have defaults anywhere then? Because API design is a complex and nuanced process, and no approach is correct 100% of the time. > and an extra potential for a mistake or a typo, where a mistake in one declaration makes the whole thing incorrect, which kinda goes against what CSS is currently is. No, that sort of thing does occur at times in CSS. For example, @counter-style requires a 'system' descriptor, and either 'symbols' or 'additive-symbols', even tho we *could* theoretically default 'system' to, say, `cyclic`. The 'font' shorthand requires you to specify a font-family, even tho we could theoretically default it to `serif` (the initial value). Etc. -- GitHub Notification of comment by tabatkins Please view or discuss this issue at https://github.com/w3c/css-houdini-drafts/issues/994#issuecomment-667205571 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 16:13:39 UTC