media query breakpoints vs client viewport widths

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

File: 1790358763486.jpg (296.33 KB, 1024x1024, img_1790358756235_obc28n48.jpg)ImgOps Exif Google Yandex

media query breakpoints vs client viewport widths DataNinja 09/25/26 (Fri) 17:52:43 19f80 No.2139

I am tired of seeing developers set breakpoints based on arbitrary device sizes like iPhone or iPad. It is much harder to debug when your layout breaks on a random tablet width that does not match any specific breakpoint in your stylesheet. Just use the actual content boundaries to decide where things need to shift.

Anonymous 09/26/26 (Sat) 22:21:04 19f80 No.2143

File: 1790461264762.jpg (271.32 KB, 1024x1024, img_1790461249397_3cm5q0lj.jpg)ImgOps Exif Google Yandex

>>2139
>Just use the actual content boundaries to decide where things need to shift.

Had a client scream at me last month because their custom dashboard looked like garbage on some weird mid-sized window, and I'd only built for standard mobile/desktop widths.

SEOGuru 09/28/26 (Mon) 02:13:28 19f80 No.2146

>>2143
clients never care about 'proper' implementation, they just want it to work on their specific crappy android. i've seen way too many sites die because some dev tried to be clever with content-based queries and forgot that googlebot crawls with a very specific, narrow viewport. it's usually a desktop emulator

Anonymous 09/30/26 (Wed) 02:17:03 19f80 No.2152

File: 1790734623227.jpg (149.21 KB, 1024x1024, img_1790734608145_acyq1uvf.jpg)ImgOps Exif Google Yandex

>>2146
That part about googlebot is what always trips me up. I've been trying to learn how to do the content-based thing but I'm terrified of messing up my SEO rankings if the crawler sees something different. It's like a balancing act between making it look good and not breaking the site for search engines. I tried using emulated viewport testing once on a project but I couldn't even figure out how to sync it with my local dev server. Does anyone know if there's a way to test that without just manually resizing the browser window like a ~~maniac~~ idiot? It feels like there should be an easier way to see what the bot is actually seeing.