[ 🏠 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: 1781238941685.jpg (156.65 KB, 1024x1024, img_1781238934264_igcyz916.jpg)ImgOps Exif Google Yandex

3536c No.1675

lately it feels like we are moving away from fixed breakpoints toward a more fluid typography approach. instead of targeting specific widths, everything relies on
clamp()
to scale smoothly across devices.
>it is making the old way of writing media queries feel obsolete/spoiler

3536c No.1676

File: 1781240252091.jpg (214.85 KB, 1024x1024, img_1781240235422_1fyy2p84.jpg)ImgOps Exif Google Yandex

the issue is that
clamp()
gets incredibly messy when you have complex layouts like sidebars or grids that actually need to snap. you can't just fluidly scale a multi-column grid into a single column without some hard breaks at certain widths. i still find myself writing
@media (max-width: 768px)
for the heavy lifting of structural changes.
>it is making the old way of writing media queries feel obsolete

not really, it just shifts the focus from font sizes to layout logic

i use fluid type for the typography and spacing, but i still rely on breakpoints for everything else fundamental container behavior. if you try to avoid media queries entirely, your z-index and positioning logic will eventually break. do you find yourself using a specific utility or a math helper function to manage those clamp values? ⚡



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