Re: [csswg-drafts] Proposal: Custom CSS Functions & Mixins (#9350)

@tabatkins I think colon followed by value makes more sense for default arguments, with an optional wrapper if the value itself includes commas; though this is one of these cases where semicolon separators would actually make a lot of sense. Also, types are specified as strings in `@property` so having a completely different syntax here feels weird.

@nex3 
> This would make any kind of low-context parsing a _nightmare_ for tooling like Sass, for what it's worth. The saving grace of calculation syntax right now is that it only appears in consistent, easily-recognizable contexts. It would probably mean that we have to pessimistically treat _all_ plain-CSS function calls as effectively string quotes, which would be a severe usability hit.

That ship has sailed; literally all new math functions accept calculations for their arguments.
(Also, there’s [TAG Principle 2.12. Prioritize usability over compatibility with third-party tools](https://www.w3.org/TR/design-principles/#third-party-tools))

That said, while off-topic for this thread, I’d love to understand the Sass problem better, as I firmly believe that few problems genuinely have no win-win solutions. I wonder if a better path forwards for Sass would be to simply deal with *fewer* calculations: wrap inline calculations with `calc()` and pass them to CSS for the actual computation. Then it can wrap in `calc()` optimistically, and these function calls would not be affected at all. Plus, it means you can do things like `width: 1em + 100px;` without getting an error, which is a usability win for Sass itself. I understand this won't work for all cases, but I think it might work for enough to relegate any negative impact from this to edge cases. I'm likely missing something major, but the overall sentiment is, let's try and figure out a solution to this together, that doesn't involve making CSS less usable.

-- 
GitHub Notification of comment by LeaVerou
Please view or discuss this issue at https://github.com/w3c/csswg-drafts/issues/9350#issuecomment-1924995215 using your GitHub account


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

Received on Saturday, 3 February 2024 01:18:15 UTC