Thread Rating:
09-04-2026, 08:31 PM
Container queries changed how I build card layouts — the component adapts to its slot, not the viewport.
I design in the browser almost exclusively now; mockups only for client sign-off.
:has() finally lets me style parents without JavaScript, and support is good now.
I did a bit of searching but could not find a recent thread on this, so here we go.
I design in the browser almost exclusively now; mockups only for client sign-off.
:has() finally lets me style parents without JavaScript, and support is good now.
I did a bit of searching but could not find a recent thread on this, so here we go.
09-05-2026, 12:56 PM
:has() feels like cheating compared to what we used to do.
CSS variables + one class toggle is my whole dark mode stack.
CSS variables + one class toggle is my whole dark mode stack.
09-07-2026, 01:48 PM
Refactoring legacy CSS one component at a time is the only sane way.
Could not agree more.
Could not agree more.
09-07-2026, 06:05 PM
I still reach for Bootstrap when a client needs to maintain it afterwards.
Good point, I had not thought of it that way.
Good point, I had not thought of it that way.
09-09-2026, 02:38 PM
:has() feels like cheating compared to what we used to do.
I still reach for Bootstrap when a client needs to maintain it afterwards.
Could not agree more.
Nice thread, following for the replies.
I still reach for Bootstrap when a client needs to maintain it afterwards.
Could not agree more.
Nice thread, following for the replies.
09-10-2026, 05:40 PM
09-11-2026, 12:10 PM
:has() feels like cheating compared to what we used to do.
CSS variables + one class toggle is my whole dark mode stack.
Bumping this because I ran into the same thing today.
CSS variables + one class toggle is my whole dark mode stack.
Bumping this because I ran into the same thing today.
« Next Oldest | Next Newest »
Users browsing this thread: 2 Guest(s)
