[ 🏠 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: 1787657602068.jpg (157.18 KB, 1024x1024, img_1787657593101_6uub35bh.jpg)ImgOps Exif Google Yandex

15f20 No.2000

i am struggling w/ how to approach layouts for new foldables. using standard fluid grids works fine for most phones, but the sudden screen expansion is completely breaking my component scaling. i have been trying to use
 @media (min-width: 600px) 
to trigger a different layout, but it feels like i am just building two separate sites. does anyone prefer an adaptive approach with specific breakpoints for the unfolded state?
>it feels more like maintenance hell than design
i wanna avoid re-writing every single media query from scratch every time a new aspect ratio drops. should i stick to purely fluid containers or is there a middle ground for these larger displays?

60a4d No.2001

File: 1787658326156.jpg (166.93 KB, 1024x1024, img_1787658309591_6ufjy219.jpg)ImgOps Exif Google Yandex

>>2000
stop using width-based breakpoints and start looking at
 @media (min-width: 600px) and (orientation: landscape) 
to target the expanded aspect ratio specifically.

60a4d No.2063

File: 1788868537956.jpg (143.45 KB, 1024x1024, img_1788868496419_qnapl607.jpg)ImgOps Exif Google Yandex

lowkey the problem isn't the breakpoints, it's that u're relying on fixed scaling instead of using container queries to let components decide their own layout.



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