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

/q/ - Q&A Central

Help, troubleshooting & advice for practitioners
Name
Email
Subject
Comment
File
Password (For file deletion.)

File: 1792242116594.jpg (41.03 KB, 1080x771, img_1792242105945_w0vjl94w.jpg)ImgOps Exif Google Yandex

ce41b No.2396

finally found a way to skip that annoying js trickery for animating elements as they hit the dom. using -style instead of setting opacity 0 and then toggling classes manually is such a massive win. chromium devtools was lagging behind on debugging this stuff until version 143 but polypane already had it covered back in june 2024. honestly kinda wild how much easier it makes things when you don't have to manage two different states just for a simple fade in. still not sure if i can trust it for complex stuff though. looks way cleaner than:
.element {  opacity: 0;}.element.visible {  opacity: 1;}

lmao imagine going back to that mess.

more here: https://polypane.app/blog/how-to-debug-the-starting-style-at-rule-in-polypane/


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