Post

701: Digital Archives, OpenClaw Security Concerns, and @Property Declarations When Dave dies, who gets his domain name? How OpenClaw is a massive security concern, tips on handling a broad design surface area with a design system, changing database values with text-transform, should you declare…

shoptalkshow.com701: Digital Archives, OpenClaw Security Concerns, and @Property DeclarationsWhen Dave dies, who gets his domain name? How OpenClaw is a massive security concern, tips on handling a broad design surface area with a design system, changing database values with text-transform, should you declare CSS properties with @property, and was Chris wrong about CSS?

2 reposts4 likes

Awesome. I just need to update by brain database: Custom properties without \@property are non-animatable/transitionable. But other properties that use the custom properties are.

Yep. The most common issue here is that while background colors can animate, gradients can't, so you have to animate custom props and pipe them into the gradient. But of course, doing so requires \@property!

Custom properties do animate by default, but they animate _discretely_ (as in: they flip over midway the animation). By registering a custom property to be of a certain type (through @property), the browser knows how to interpolate its values when used in transitions and animations.

Yeah, it's a technical detail that you mostly don't even notice because the animations go so fast.