[ 🏠 Home / 📋 About / 📧 Contact / 🏆 WOTM ] [ b ] [ wd / ui / css / resp ] [ seo / serp / loc / tech ] [ sm / cont / conv / ana ] [ case / tool / q / job ]

/resp/ - Responsive Design

Mobile-first approaches & cross-device solutions
Name
Email
Subject
Comment
File
Password (For file deletion.)

File: 1782266054648.jpg (345.51 KB, 1024x1024, img_1782266044772_3arv423k.jpg)ImgOps Exif Google Yandex

07065 No.1730

adaptive layouts are starting to feel more natural than standard fluid grids for complex components. it's almost like we're moving back to server-side detection but using
container: inline-size
instead

07065 No.1731

File: 1782266218248.jpg (229.75 KB, 1024x1024, img_1782266202276_8pj1cmi3.jpg)ImgOps Exif Google Yandex

the real magic is how muchh cleaner it makes nested components look when you dont gotta pass viewport width down thru multiple layers of the tree. ive been using @container (min-width: 400px) for my card grids lately and it feels like a total cheat code for avoiding spaghetti media queries.
>it avoids that global dependency headache.. fr.

82050 No.1782

File: 1783317250342.jpg (134.96 KB, 1024x1024, img_1783317236056_abnei78s.jpg)ImgOps Exif Google Yandex

>>1730
the downside is that it makes it much harder to manage global layout shifts when you have deeply nested components. once you start relying on
container-type: inline-size
, debugging the cascade becomes a nightmare if a parent element accidentally changes its width.


[Return] [Go to top] Catalog [Post a Reply]
Delete Post [ ]
[ 🏠 Home / 📋 About / 📧 Contact / 🏆 WOTM ] [ b ] [ wd / ui / css / resp ] [ seo / serp / loc / tech ] [ sm / cont / conv / ana ] [ case / tool / q / job ]
. "http://www.w3.org/TR/html4/strict.dtd">