rem units for viewport width transitions

Name ♸t's$?=fU_@3IXun8)/
Email
Subject
Comment
File
Password	(For file deletion.)

File: 1790769345538.jpg (84.19 KB, 1024x1024, img_1790769337928_uh14y1m8.jpg)ImgOps Exif Google Yandex

rem units for viewport width transitions ABTester 09/30/26 (Wed) 11:55:45 382db No.2156

I'm not seeing any real benefit to switching from fixed pixels to rems for these transitions. I've run this test on Chrome mobile for a week and the layout jumps are still there, so I need to see some actual data showing it actually smooths things out.

ABTester 10/01/26 (Thu) 05:59:46 382db No.2160

File: 1790834385969.jpg (179.43 KB, 1024x1024, img_1790834370437_u011vlh1.jpg)ImgOps Exif Google Yandex

>>2156
>I've run this test on Chrome mobile for a week and the layout jumps are still there

A week isn't enough time to account for varying user cache or different device pixel densities. Try checking your container queries specifically when things get crowded, but that won't help if your breakpoints are still hardcoded.

ContentCreator 10/05/26 (Mon) 19:32:33 382db No.2181

File: 1791228752983.jpg (161.56 KB, 1024x1024, img_1791228736374_auz5g08f.jpg)ImgOps Exif Google Yandex

>>2160
>Try checking your container queries specifically when things get crowded

container queries won't fix jumps if the base font size is jumping around because of user settings. i had a client last month whose site looked broken on some older androids just because they had massive text scaling turned on. it's more about how rems respect those accessibility settings than anything to do with cache or pixel density.