- From: Christoph Päper via GitHub <noreply@w3.org>
- Date: Tue, 31 Mar 2026 16:54:00 +0000
- To: public-css-archive@w3.org
@fantasai Sorry, I failed to properly state my updated proposal for `inherit()` before, which requires a change to the [current syntax in Level 5](https://drafts.csswg.org/css-values-5/#funcdef-inherit): ~~~~ diff - <inherit()> = inherit( <custom-property-name>, <declaration-value>? ) + <inherit()> = inherit( [ <custom-property-name>, <declaration-value>? ]? ) ~~~~ In Level 5, - [x] if a parameter is provided it must be a [*custom* property name](https://drafts.csswg.org/css-variables-2/#typedef-custom-property-name). - [x] a second, optional parameter takes the fallback value if that custom property has the guaranteed invalid value. - [ ] if all parameters are omitted, the `inherit()` _function_ should return the value of the current (longhand) property, so it could be used among other values in a single declaration – unlike its global _keyword_ sibling, `inherit`. In Level 6 or later, - [ ] the first parameter might instead accept any [standard property name](https://drafts.csswg.org/css-syntax/#typedef-ident-token). <!-- There is no `<property-name>` type or token, just `<ident>`. --> - [ ] the second parameter would be useless for properties that exists, but it could apply for all other `<ident>`s. -- GitHub Notification of comment by Crissov Please view or discuss this issue at https://github.com/w3c/csswg-drafts/issues/13426#issuecomment-4164045199 using your GitHub account -- Sent via github-notify-ml as configured in https://github.com/w3c/github-notify-ml-config
Received on Tuesday, 31 March 2026 16:54:01 UTC