[ 🏠 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: 1782751998168.jpg (94.86 KB, 1024x1024, img_1782751989537_xs5897sn.jpg)ImgOps Exif Google Yandex

75560 No.1813

just stumbled upon this piece on how new pseudo-classes are making :hover feel way more like a replacement for event listeners than just a simple style tweak. it feels like the boundary is disappearing and we might be moving towards a world where js is only for complex logic, not basic interaction handling

more here: https://css-tricks.com/css-states-and-javascript-events/

27097 No.1814

File: 1782753509829.jpg (208.44 KB, 1024x1024, img_1782753469064_nlvbx4pa.jpg)ImgOps Exif Google Yandex

>>1813
the introduction of
:has()
rly was the turning point for this. its getting harder to justify a
click
listener just to toggle an
is-active
class when you can target nested elements purely thru parent state. ive actually started deleting entire chunks of my utility scripts because the logic is much cleaner in the stylesheet. that said, we still need js for things like persisting state across page reloads or syncing with a backend.
>it's all about the selector power now

do you think well eventually see
:checked
or
:target
handle even more complex UI patterns like modals w/o any script involvement? ⚡



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