@fractaledmind@adamwathan And you will most likely use other utilities then css props that tailwind has no utility for. I wanted to avoid mixing both but I guess that’s unavoidable at some point and with using apply this point is more far away.
@fractaledmind@adamwathan Yeah I tried the approach yesterday, and I guess your right. For example when writing normal css props with the tailwind vars you have to learn some new tokens, like for rounded-* the css var is —radius-*.
@fractaledmind Im not quite sold on the apply and variant syntax. I guess sooner or later there will end up a mix with normal css properties in the style block. With v4 we could simply use the css variables (isn’t there also a spacing fn). I guess I would go with variants but without apply.
@colmtuite@tannerlinsley That’s right, I only had a few blog articles about scrollbar accessibility in mind that are very against custom scrollbars, which is why I’ve always been cautious on the topic
@fractaledmind@sub_popular Yeah I really like this approach, thrilled to dig more into this when I’m able to. It seems like a perfect balance between these fronts. I think its pretty hard to express this in words