- From: Christoph Päper via GitHub <noreply@w3.org>
- Date: Wed, 15 Oct 2025 05:36:37 +0000
- To: public-css-archive@w3.org
Since this is still open and [Blink intents to prototype](https://groups.google.com/a/chromium.org/g/blink-dev/c/nCUNGmfAOMU/m/YOCfBQV6BwAJ), I’m not opening a new issue: Is there any chance the [`inherit()` function](https://drafts.csswg.org/css-values-5/#inherit-notation) could behave more like [`inherit` global keywords](https://drafts.csswg.org/css-values-5/#inherit-notation) in that it always refers to the (custom) property it is used within? That means, drop the first parameter, thus only expect an optional fallback value. For accessing ancestral values from arbitrary properties, there could either be a separate function like `parent()` / `parental()` or the first parameter could just be made optional although I don’t see how that would work reliably. -- GitHub Notification of comment by Crissov Please view or discuss this issue at https://github.com/w3c/csswg-drafts/issues/2864#issuecomment-3404593711 using your GitHub account -- Sent via github-notify-ml as configured in https://github.com/w3c/github-notify-ml-config
Received on Wednesday, 15 October 2025 05:36:38 UTC