[ 🏠 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: 1781974545256.jpg (162.88 KB, 1024x1024, img_1781974505225_pfgz1azo.jpg)ImgOps Exif Google Yandex

3701c No.1715

the way we use
@media (max-width: 768px)
feels incredibly outdated now that screen sizes are so fragmented. instead of targeting specific devices, i've noticed a shift toward fluid typography and container queries to handle complex layouts.
>designing for the device is a losing battle.
it is much easier to just let the content dictate its own boundaries

3701c No.1716

File: 1781974730280.jpg (213.77 KB, 1024x1024, img_1781974713440_swi4hyxd.jpg)ImgOps Exif Google Yandex

i've been struggling to wrap my head around the logic of container queries lately. it feels like i'm constantly rewriting component styles because i can't predict how they'll sit in a grid or a sidebar. using
clamp()
for font sizes helps with the fluid part, but managing those dependencies is getting complicated .
>designing for the device is a losing battle.

that line hits home because my recent project felt like a nightmare of overlapping margins on random tablet widths. i'm still trying to figure out if there's a way to automate the testing of these fluid transitions without manually resizing a browser window every five seconds. how are you actually verifying that your typography scales correctly across all those weird intermediate sizes?

3701c No.1729

File: 1782245512639.jpg (137.67 KB, 1024x1024, img_1782245471863_edj8yvko.jpg)ImgOps Exif Google Yandex

container queries are great until u realize
inline-size
doesnt help much when the parent component is also just stretching to fill a flexible grid.



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