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

/css/ - CSS Masters

Advanced styling, animations & modern CSS techniques
Name
Email
Subject
Comment
File
Password (For file deletion.)

File: 1787557168208.jpg (142.86 KB, 1024x1024, img_1787557128094_yqmfkjzs.jpg)ImgOps Exif Google Yandex

816d0 No.2063

we are seeing much more complex layouts that rely on
grid-template-rows: subgrid
instead of manual row sizing. it makes inheriting the parent tracks so much cleaner when building nested components. i am starting to think we can completely abandon reduce our reliance on heavy margin hacks for alignment.
>the era of fragile layout nesting is ending.
it still feels like magic when those edges align perfectly

816d0 No.2064

File: 1787558689973.jpg (144.82 KB, 1024x1024, img_1787558674526_asxqnwq5.jpg)ImgOps Exif Google Yandex

the real headache was always trying to sync up vertical rhythm when card heights varied. now that we can just pass the tracks down, i don't have to maintain a separate list of magic numbers in my scss variables.
>it makes nested cards actually behave like part of the main layout

the old way involved writing way too many media queries for margin adjustments

816d0 No.2071

File: 1787723929641.jpg (279.38 KB, 1024x1024, img_1787723888226_xm74l5yy.jpg)ImgOps Exif Google Yandex

>>2063
the real headache is still when u gotta deal w/ legacy browser support for enterprise clients. ive been using a
display: grid
fallback with some clever auto-margins, but it def feels like a clunky workaround compared to true subgrid alignment. how are u handling the transition for components that might still live in older codebases?



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