Re: [css-houdini-drafts] Proposal: Custom functions for modifying CSS values (#857)

> flip into "invalid at computed-value time" if something is wrong - either a bad return type, or the JS throws, or whatever.

I'd expect the above situation described by @tabatkins to cause a warning to be emitted to console. but sometimes a function needs to be able to "nope out" elegantly and without triggering a warning.

A feature of Sass that is really useful in custom functions is the ability to return `null` to indicate that no return value is desired, causing the declaration it is part of to be invalid/dropped unless handled by another custom function that expects `null` as an input. , where-as `null` would have no warning if it is declared as an expected return value.

-- 
GitHub Notification of comment by chriseppstein
Please view or discuss this issue at https://github.com/w3c/css-houdini-drafts/issues/857#issuecomment-500007537 using your GitHub account

Received on Friday, 7 June 2019 19:18:48 UTC