Designing in the browser — still a thing?

Thread Rating:

0 Vote(s) - 0 Average
1
2
3
4
5

Threaded Mode

« Previous 1 2 3 4 5 Next »

VinylVera

Member

217 23 Nov 2025 0

#11

07-26-2026, 12:09 PM

(07-26-2026, 11:01 AM)QuietQuokka Wrote:
(07-26-2026, 10:53 AM)DoodleDom Wrote: :has() feels like cheating compared to what we used to do.

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

Thanks for sharing, saved me a lot of time.

Find

PatchPat

Moderator

246 22 Aug 2026 0

#12

07-26-2026, 01:44 PM

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

Could not agree more.

Find

admin

Administrator

234 20 Nov 2026 0

#13

07-26-2026, 03:42 PM

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

Nice thread, following for the replies.

Find

LunarLily

Member

235 21 Dec 2025 0

#14

07-26-2026, 05:33 PM

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

Find

BinaryBen

Member

238 23 Jun 2026 0

#15

07-26-2026, 06:21 PM

(07-26-2026, 05:33 PM)LunarLily Wrote: 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.

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

Nice thread, following for the replies.

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

Find

FluxFiona

Member

229 22 Oct 2026 0

#16

07-26-2026, 07:26 PM

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

Could not agree more.

Find

~~SpammySteve~~

Banned

209 16 Oct 2025

#17

07-26-2026, 07:54 PM

(07-26-2026, 07:26 PM)FluxFiona Wrote: Refactoring legacy CSS one component at a time is the only sane way.

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

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

Thanks for sharing, saved me a lot of time.

Find

DevDan

Member

230 15 May 2026 0

#18

07-26-2026, 09:44 PM

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

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

Nice thread, following for the replies.

Find

ZenZara

Super Moderator

231 26 Mar 2026 0

#19

07-26-2026, 11:27 PM

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

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

Thanks for sharing, saved me a lot of time.

Find

RetroRex

Member

209 15 Mar 2026 0

#20

07-27-2026, 01:15 AM

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

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

Nice thread, following for the replies.

Find

« Next Oldest | Next Newest »

« Previous 1 2 3 4 5 Next »

Users browsing this thread: 2 Guest(s)

Forum Jump: