Re: [community-group] Computed Token Values (#81)

Thanks for the reply @c1rrus!

Yeah, I can definitely see how it makes the spec much more complex to support custom functions. I’d probably draw the line at basic arithmetic like I think CSS does with `calc()`, but your point on how far that could go is valid.

I want to make sure it’s clear that I’m fully on board with using `rem` units, perhaps my statement of “only having value in the Web” could’ve been phrased better. In terms of Android I agree `sp` is closer to `rem` since it bases off the users text-size, but it makes me think of the idea of `dp` which they use for a unit relative to screen density.

I’m not sure I have any answers here, but I think it’s interesting to be able to define how parts of a system are relative to each other versus relative to some other master unit. That said, a pre-processor, or doing a little basic math (paired with a comment denoting the relative nature) when defining tokens could also do that.

-- 
GitHub Notification of comment by tonyjwalt
Please view or discuss this issue at https://github.com/design-tokens/community-group/issues/81#issuecomment-993958867 using your GitHub account


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

Received on Tuesday, 14 December 2021 20:34:24 UTC