- From: Isiah Meadows via GitHub <sysbot+gh@w3.org>
- Date: Sun, 09 Jun 2019 06:35:49 +0000
- To: public-houdini-archive@w3.org
@chriseppstein > As far as I know, CSS has no boolean type. But custom functions really need them as an intermediate value to allow custom functions to interoperate. Otherwise developers will end up with some sort of cargo-culted convention of using `true` and `false` idents but only be able to declare an input as accepting `<ident>` which is a much bigger input space. Just to add to that point, it's not like there isn't precedent. Less does this very thing internally IIUC, just making `true` and `false` just special identifiers after people started using it that way. -- GitHub Notification of comment by isiahmeadows Please view or discuss this issue at https://github.com/w3c/css-houdini-drafts/issues/857#issuecomment-500189010 using your GitHub account
Received on Sunday, 9 June 2019 06:35:50 UTC