Anger Flame Cooling

About Anger Flame Cooling

Anger Flame Cooling is a checkbox built with a keyframe animation, gradient fills, transforms and layered shadows. Its stylesheet runs to 134 lines across 21 rules, declaring 23 distinct properties. It styles checked state explicitly, so the component responds to interaction rather than sitting still. The animation is driven by keyframe sequences named anger-flicker, anger-inner-flicker, anger-core-flicker, calm-gentle-sway, calm-inner-sway, calm-core-sway and calm-float, which you can retime or remove without touching the rest of the styling. Every format shown on this page is the same component, so you can take CSS and Tailwind depending on how your project is set up. Nothing is minified and nothing depends on a framework.

When to use

• Settings panels and forms, where state has to read at a glance, where a emotion and psychology checkbox fits the surrounding design
• A single prominent checkbox rather than a row of them, since the anger-flicker animation runs continuously and several at once compete with each other
• Palettes built around red, orange and yellow, where this checkbox can be dropped in without retheming
• Places where one control is meant to be memorable, since 134 lines of CSS is a real investment for a single element

How it works

The base rule sets the shape with border-radius, display, height and position. The fill is a gradient rather than a flat colour, so it is a single background declaration with no image to load. Movement is done with transforms rather than by changing position or size, which is what keeps it smooth: transforms are composited and do not force the browser to lay the page out again. State changes are eased with a transition, so hovering does not snap. The looping motion comes from anger-flicker, anger-inner-flicker, anger-core-flicker, calm-gentle-sway, calm-inner-sway, calm-core-sway and calm-float. Changing the animation-duration is usually the only edit needed to make it faster or calmer.

Accessibility

No focus style is defined. Add one before shipping, or keyboard users lose track of position. Animates without a prefers-reduced-motion guard. Wrap the animation in that query if motion sensitivity matters to your audience. Those are 2 things to fix before this ships in front of users.

Browser support

Everything this component uses has been supported across browsers for years, so no fallback is needed.

Related components

Frequently asked questions