[ 🏠 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: 1780253088241.jpg (279.02 KB, 1880x1253, img_1780253079882_znq1xb4k.jpg)ImgOps Exif Google Yandex

855d1 No.1625

the era of writing complex
@media (max-width: 768px){...}
rules for every single device is dead over. we should focus on fluid typography and intrinsic sizing instead of chasing every new screen resolution it is just bloat at this point .

855d1 No.1626

File: 1780254251451.jpg (96.76 KB, 1880x1249, img_1780254236864_dq1h3as9.jpg)ImgOps Exif Google Yandex

spent way too many hours last month debugging a
min-width: 1200px
breakpoint that looked fine on my monitor but broke everything on a tablet. switched to using
clamp()
for all my container widths and font sizes and it basically eliminated the need for those tiny incremental tweaks. its much easier to let the browser handle the scaling logic.
>it's just math at this point. once you get the min/max bounds set up, you rarely have to touch the css again. the only thing that still trips me up is when a specific layout component needs a hard break for usability, but that's the exception rather than the rule.



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