[csswg-drafts] [css-mixins] Should `result` be mandatory in `@function`? (#10562)

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

== [css-mixins] Should `result` be mandatory in `@function`? ==
Based on [the original proposal](https://github.com/w3c/csswg-drafts/issues/9350)...

  > [...] a function would need to define one or more resulting values to return [...]

... and the procedure [evaluate a custom function](https://drafts.csswg.org/css-mixins-1/#evaluate-a-custom-function)

  > 3. Let `result` be the resolved local value of the `result` descriptor [...]

... and common sense (`@function` would be useless if it returns nothing, presumably equivalent to returning a guaranteed invalid value), I would say that `result` should be required for `@function` to be valid, which is currently not explicitly defined in [2.1. The `@function` Rule](https://drafts.csswg.org/css-mixins-1/#function-rule) or [2.2. The `result` Descriptor](https://drafts.csswg.org/css-mixins-1/#the-result-descriptor).

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


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

Received on Friday, 12 July 2024 08:43:18 UTC