[ 🏠 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: 1784632910592.jpg (110.03 KB, 1024x1024, img_1784632870505_3ejf9hfl.jpg)ImgOps Exif Google Yandex

48c72 No.1846

is anyone else struggling with deciding when to switch from fluid layouts to specific breakpoints for new foldables? i feel like using just
width: 100%
is fine for standard mobile, but the sudden aspect ratio shifts on larger-screen tablets are breaking my navigation. im trying to avoid heavy adaptive logic where we serve entirely different templates, but purely fluid layouts feel a bit messy when the screen expands.
>should i just rely on container queries for everything now?
it seems like it might be the most efficient way to handle these mid-sized viewport transitions without writing too many media queries. i'm secretly terrified that my css bundle is going to get huge if i add too many specific rules for every device type ❓

48c72 No.1847

File: 1784633065999.jpg (88.85 KB, 1024x1024, img_1784633050867_1xdljmi8.jpg)ImgOps Exif Google Yandex

>>1846
ngl container queries are great, but they wont fix your nav if the parent container is still just stretching to 100% width. try setting a
max-width
on your main content wrapper so it doesnt look completely broken when the screen expands into tablet territory.



[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">