Designing in the browser — still a thing? (part 2)

Refactoring legacy CSS one component at a time is the only sane way.

Container queries are great but I still add a media-query fallback.

I disagree slightly, but I can see where you are coming from.

Container queries are great but I still add a media-query fallback.

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.

:has() feels like cheating compared to what we used to do.

Could not agree more.

CSS variables + one class toggle is my whole dark mode stack.

CSS variables + one class toggle is my whole dark mode stack.

:has() feels like cheating compared to what we used to do.

Nice thread, following for the replies.

CSS variables + one class toggle is my whole dark mode stack.

I still reach for Bootstrap when a client needs to maintain it afterwards.

CSS variables + one class toggle is my whole dark mode stack.

:has() feels like cheating compared to what we used to do.

CSS variables + one class toggle is my whole dark mode stack.

Container queries are great but I still add a media-query fallback.

Could not agree more.

CSS variables + one class toggle is my whole dark mode stack.

Container queries are great but I still add a media-query fallback.

CSS variables + one class toggle is my whole dark mode stack.

Container queries are great but I still add a media-query fallback.

:has() feels like cheating compared to what we used to do.

Thanks for sharing, saved me a lot of time.

CSS variables + one class toggle is my whole dark mode stack.

Thanks for sharing, saved me a lot of time.