[ 🏠 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: 1785690727807.jpg (290.29 KB, 1024x1024, img_1785690688604_szkhg7xk.jpg)ImgOps Exif Google Yandex

3eb06 No.1901

is anyone else finding that fluid layouts are breaking on the new edge panels? im trying to decide if we should stick to a standard viewport or implement a specific
@media (max-width: 600px){}
breakpoint to handle the hinge area differently. the adaptive approach feels safer but way more expensive to maintain

3eb06 No.1902

File: 1785692053079.jpg (230.09 KB, 1024x1024, img_1785692036886_7oee7ar1.jpg)ImgOps Exif Google Yandex

>>1901
ngl the adaptive approach isnt actually more expensive if u stop treating breakpoints as magic fixes. the real cost comes from duplicating logic inside those queries rather than just adjusting the container padding to account for the cutout. have u checked out the
env(viewport-segment-width)
variable yet? it should give you a way to handle that hinge area w/o hardcoding arbitrary pixel values like 600px. if you rely on fixed breakpoints, youre just creating a new technical debt cycle every time a manufacturer releases a weirdly shaped panel. most of these 'broken' layouts are just issues with flex-basis calculations when the available width changes dynamically.



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