[csswg-drafts] [css-mixins-1] 3.1.11 seems to make it impossible to have a return type (#12256)

romainmenke has just created a new issue for https://github.com/w3c/csswg-drafts:

== [css-mixins-1] 3.1.11 seems to make it impossible to have a return type ==
`3.1.6`:

> If custom function has a return type, create a custom property registration with the name "return" (violating the usual rules for what a registration’s name can be), a syntax of the return type, an inherit flag of "false", and no initial value. **Add the registration to registrations**.

`3.1.11`:

> For each custom property registration of registrations, set its initial value to the corresponding value in argument styles, **set its syntax to the universal syntax definition**, and prepend a custom property to body rule with the property name and value in argument styles.

_emphasis mine_

This seems to erase any return type.

Should `set its syntax to the universal syntax definition` only apply to registrations that have corresponding argument styles, this skipping `return`?

Or is `set its syntax to the universal syntax definition` intended to only be applied to those registrations that do not yet have any type?

Please view or discuss this issue at https://github.com/w3c/csswg-drafts/issues/12256 using your GitHub account


-- 
Sent via github-notify-ml as configured in https://github.com/w3c/github-notify-ml-config

Received on Sunday, 1 June 2025 09:11:32 UTC