- From: andruud via GitHub <noreply@w3.org>
- Date: Tue, 04 Nov 2025 10:32:37 +0000
- To: public-css-archive@w3.org
Good point, @kizu. Since that lets you grab the outer-frame value unilaterally (i.e. no change on the call site), that seems sufficient for now. Then how about the following: Within a custom function: * Functional equivalents for CSS-keywords resolve as they would on the real element. * CSS-wide keywords behave as their functional equivalent, i.e. `--x:inherit` => `--x:inherit(--x)`, `--x:initial` => `--x:initial(--x)`. * This is to reinterpret the value using the local type. The spec [already does this](https://drafts.csswg.org/css-mixins-1/#resolve-function-styles:~:text=Resolves%20like%20an%20inherit()%20function) for `inherit`. * `initial()` does not exist yet, but you know what I mean. * CSS-wide _keywords_ (not functional equivalents) are still left unresolved on the `result` descriptor. (No change.) -- GitHub Notification of comment by andruud Please view or discuss this issue at https://github.com/w3c/csswg-drafts/issues/12987#issuecomment-3485193123 using your GitHub account -- Sent via github-notify-ml as configured in https://github.com/w3c/github-notify-ml-config
Received on Tuesday, 4 November 2025 10:32:38 UTC