realized my CSS reset was killing my @property animations

I spent 3 days on a gradient animation that kept snapping back to the start, and it turned out the browser defaults were overriding my registered custom properties. Found a random comment in a Stack Overflow thread from 2022 mentioning that `all: initial` wipes out `initial-value` on custom properties. Has anyone else hit this with their resets, or do you just scope those declarations to a wrapper?

1 comments

1 Comment

milam4216d ago

Spent a whole weekend chasing the same thing with my own reset, turns out `all: initial` on my normalize was nuking `initial-value` on registered properties too. I finally just wrapped those animations in a scoped container and set the properties right there instead of relying on the reset. It feels hacky but honestly, the scoped approach saved me way more time than digging through browser quirks again.