- From: Lea Verou via GitHub <sysbot+gh@w3.org>
- Date: Thu, 12 Nov 2020 13:15:51 +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.
Come on folks, let's not pretend that `inherits` is required for API design purposes. That implies that there is a usability reason for this, which is false. If usability was the only factor, `inherits` would be optional and would default to `true`, because this is the default for non-registered properties. The reason it's required is performance, and thus, is a case of implementation affecting UI decisions, which is actually a usability anti-pattern, not to mention a violation of the Priority of Constituencies ("users before implementors").
I do understand the reasons, and I'm not saying we should make it optional, but telling @kizu that this is done for API design purposes is disingenuous. It's done to discourage use of a value that is performance intensive, plain as that.
--
GitHub Notification of comment by LeaVerou
Please view or discuss this issue at https://github.com/w3c/css-houdini-drafts/issues/994#issuecomment-726070467 using your GitHub account
--
Sent via github-notify-ml as configured in https://github.com/w3c/github-notify-ml-config
Received on Thursday, 12 November 2020 13:15:53 UTC