News for hackers. Stuff that matters.

A comment on Signals for Tailwind CSS (styling based on ancestor state via style queries). Parent comment

Re:Signals for Tailwind CSS (styling based on ancestor state... by krsdcbl on Saturday August 31, 2024 @07:48PM (#41412933)
if the styles only concern the context you work on, this could easily be done with vanilla scoped inline styles

If those declarations are relevant to multiple components within your codebase, then you'll still need to leave the context when your styles are inlined and therefore declared in multiple places

[ Parent | on HN ]
Re:Signals for Tailwind CSS (styling based on ancestor state... by aidos on Sunday September 01, 2024 @03:34AM (#41415022)
No. That’s the point of tailwind. You can include things like hover states. Inline css hits a roadblock there and you’re forced to go out to a style tag. Then you have to start naming things. Then you risk conflicts.

That’s the problem tailwind solves.

[ Parent | on HN ]