- From: Sebastian Zartner via GitHub <noreply@w3.org>
- Date: Thu, 04 Dec 2025 11:23:10 +0000
- To: public-houdini-archive@w3.org
@Crissov You're mixing two things here, which I think should be discussed separately: 1. Allowing to overwrite and extend an existing custom property definition. (Currently [the last one wins](https://drafts.css-houdini.org/css-properties-values-api-1/#at-ruledef-property:~:text=the%20last%20one%20in%20stylesheet%20order%20%22wins%22%2E).) 2. Making all descriptors optional. So I suggest to open a separate issue to discuss point 1. Regarding point 2, it also tripped me up many times that the `inherits` descriptor is not optional. So yes, I'm also for making them optional. > For background the `inherits` descriptor was made mandatory because the obviously reasonable default value, is also more expensive so @tabatkins felt it should always be a conscious decision. What is the obvious reasonable default value? For me, it would be _not_ to inherit, as most of the properties I define don't need to inherit. (And yes, that goes against how unregistered properties behave, so against what @AtkinsSJ [wrote](https://github.com/w3c/css-houdini-drafts/issues/1162#issuecomment-3611356552).) But I get the point that it would be more consistent to let them inherit by default. Either way, I don't get the argument why that should be more expensive. If it's to inherit by default, then it's not different to declaring them via declarations, which is what authors usually do. And _not_ inheriting by default sounds less expensive to me. So maybe you or @tabatkins could provide some background here? Sebastian -- GitHub Notification of comment by SebastianZ Please view or discuss this issue at https://github.com/w3c/css-houdini-drafts/issues/1162#issuecomment-3611670179 using your GitHub account -- Sent via github-notify-ml as configured in https://github.com/w3c/github-notify-ml-config
Received on Thursday, 4 December 2025 11:23:11 UTC