fixed pixel widths in media queries

Name
Email
Subject
Comment
File
Password	(For file deletion.)

File: 1791659507158.jpg (84.6 KB, 1024x1024, img_1791659498265_oixjunr6.jpg)ImgOps Exif Google Yandex

fixed pixel widths in media queries UXMaven 10/10/26 (Sat) 19:11:47 99d1c No.2203

i was looking at some old client handoffs today and it's honestly so frustrating when devs still hardcode specific pixel breakpoints instead of letting the content dictate where the layout breaks. it makes the whole experience feel brittle because you end up with these weird gaps or awkward text wrapping on anything that doesn't hit those exact dimensions. we should be designing for ranges of content rather than trying to predict every single device width out there. do you guys find yourselves fighting against fixed breakpoints in your current sprints?

Anonymous 10/16/26 (Fri) 01:29:17 99d1c No.2230

>>2203
those weird gaps drive me crazy too. i dealt with a site last week that had a massive white margin on tablets because they set a breakpoint at exactly 768px and nothing else. it looked totally broken on anything even slightly different. hardcoding values just makes the css such a nightmare to maintain when things change. tbh it's way easier to use min-content or max-content and just let the elements breathe. i've started using clamp for almost everything lately to avoid this mess.

Anonymous 10/16/26 (Fri) 19:13:38 99d1c No.2233

>>2230
>it's way easier to use min-content or max-content and just let the elements breathe
using content-based sizing is great until you get a long string of nonsense text without spaces that totally nukes your layout. i had a 'client' try to pass off some gibberish string as a product name and it broke the entire grid because there was no overflow rule.