Vanilla JavaScript support for Tailwind Plus

Post by omnimus » Sat, Jul 26, 2025, 8:57 AM UTC

MrJohz wrote: post #105

lemonberry wrote: post #89

Earlier quoted context omitted.

I believe it's regular old css. The :has() pseudo class. https://developer.mozilla.org/en-US/docs/Web/CSS/:has

It's not even :has, it's just how child selectors in CSS have always worked. // Not actually needed, here // for competition .group {} // Child selector .group:hover group\/hover\:bg-black { background-color: black; } // Which is essentially the same as .group:hover child { background-color: black; }

Post by omnimus » Sat, Jul 26, 2025, 9:06 AM UTC

vitaflo wrote: post #80

monkey_monkey wrote: post #68

Earlier quoted context omitted.

Yes I agree - it's nice to be able to see exactly what's happening without needing to dive into a rats nest of fragile CSS cascades.

This is literally a rats nest of css cascades.

Post by MrJohz » Sat, Jul 26, 2025, 9:38 AM UTC

omnimus wrote: post #131

MrJohz wrote: post #105

Earlier quoted context omitted.

It's not even :has, it's just how child selectors in CSS have always worked. // Not actually needed, here // for competition .group {} // Child selector .group:hover group\/hover\:bg-black { background-color: black; } // Which is essentially the same as .group:hover child { background-color: black; }

Isn’t it funny that in a thread about how Tailwind is bad and people should learn real css… people also think css selectors require JS?

Post by JoeyJoJoJr » Sat, Jul 26, 2025, 9:45 AM UTC

reactordev wrote: post #86

judah wrote: post #21

Looks like it's done using standards-based web components[0]. The page says these components don't require any existing JavaScript framework; because web component support is built-in to the browser. Nice to see devs picking up web components. [0]: https://developer.mozilla.org/en-US/docs/Web/API/Web_compone...

12 years I’ve been saying this… 12, damn, years. React graduates look at me crazy. Angular devs say it’s not needed anyway. Svelte bros say get bent. I’m so happy that someone is paying attention. You don’t need a shadow dom, you don’t need rerendering of everything when a simple value changes. You simply need web components and scoped js/ts with vite or whatever rollup you use.

Post by timeon » Sat, Jul 26, 2025, 9:52 AM UTC

gloosx wrote: post #119

ricardobeat wrote: post #67

Lovely. Verbosity aside, now on top of knowing CSS you need to learn another hierarchical system within class names.

Oh yeah, when I open a typical big project with Tailwind I always love to see some: Team Settings Manage your team permissions, invites, roles, and integrations here. Changes apply instantly across all team workspaces. Cancel Save Changes