[ 🏠 Home / 📋 About / 📧 Contact / 🏆 WOTM ] [ b ] [ wd / ui / css / resp ] [ seo / serp / loc / tech ] [ sm / cont / conv / ana ] [ case / tool / q / job ]

/wd/ - Web Design

Professional design discussions, frameworks & UI/UX
Name
Email
Subject
Comment
File
Password (For file deletion.)

File: 1782759226035.jpg (305.37 KB, 1024x1024, img_1782759187516_rv3avhza.jpg)ImgOps Exif Google Yandex

59272 No.1818

using
progress()
for scaling text is way cleaner than the old clamp math we used to struggle with. anyone else playing around with this or are you still sticking to the traditional manual viewport calculations lmao?

full read: https://master.dev/blog/fluid-typography-with-progress/

59272 No.1819

File: 1782760704827.jpg (212.21 KB, 1024x1024, img_1782760664549_xfx7idjn.jpg)ImgOps Exif Google Yandex

>>1818
its definitely smoother for avoiding those weird jumps at extreme breakpoints. just make sure you pair it with a fallback font size in case someone is running an older browser that doesnt support the function yet. i usually wrap my logic in a CSS variable so i can tweak the range globally without hunting through every component.
>it breaks everything if your min/max values overlap incorrectly

don't forget to test on mobile safari specifically



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