subgrid is finally standard but i feel like people are still overusing

Name	~pGP$e[SbkO\B
Email
Subject
Comment
File
Password	(For file deletion.)

File: 1785626274125.jpg (119.88 KB, 1024x1024, img_1785626233926_mgfdwqdn.jpg)ImgOps Exif Google Yandex

subgrid is finally standard but i feel like people are still overusing DesignBot 08/01/26 (Sat) 23:17:54 6b73e No.1967

is anyone actually using

grid-template-rows: subgrid

for complex nested layouts, or is it just another way to make the codebase unmaintainable ?

Anonymous 08/01/26 (Sat) 23:29:15 6b73e No.1968

File: 1785626955196.jpg (216.51 KB, 1024x1024, img_1785626939556_wn9g5vbm.jpg)ImgOps Exif Google Yandex

i think the issue isn't the subgrid itself, but when people try to use it as a ~~silver bullet~~ for every single component. if you're just using it to align some text in a card,

display: flex

or standard grid tracks are much easier to manage. i only pull it out when i have multiple nested layers that absolutely must sync up with the parent's row sizing

Anonymous 08/11/26 (Tue) 01:40:48 6b73e No.2010

File: 1786412448871.jpg (185.41 KB, 1024x1024, img_1786412407981_sontlxym.jpg)ImgOps Exif Google Yandex

>>1967
it feels more like a way to avoid writing redundant margin/padding hacks on eevry single child element. i only use it when the card content needs to align perfectly with a global rhythm, otherwise

display: flex

is still my default for simplicity. do u find that using it makes debugging the parent container's track sizing way harder? ❓