No libraryTransitions
Plain [hidden]
A div and one attribute. No framework, no JavaScript animation, no wrapper component.
Every value the manifest allows on this host, single presets and the pairs that compose. The first is what this component ships with. Both stages are the same component, so anything that changes between them is the attribute.
A div and one attribute
No framework, no JavaScript animation, no wrapper component. Toggling hidden is the entire integration.
A div and one attribute
No framework, no JavaScript animation, no wrapper component. Toggling hidden is the entire integration.
[hidden]
[data-motion~="scale-fade"][hidden]
transition: opacity, scale, display
<div hidden data-motion="scale-fade">
Where the attribute goes
The parts this demo composes, and the value each one carries. Everything inside an animated part is that part's content, so the tree stops there.
buttondivdata-motion="scale-fade"
Source
"use client"
import { useState } from "react"
import type { DemoProps } from "@/components/demos/props"
export function PlainHidden({ motion }: DemoProps) {
const [open, setOpen] = useState(false)
return (
<>
<button type="button" className="btn" onClick={() => setOpen((v) => !v)}>
{open ? "Hide panel" : "Show panel"}
</button>
<div className="panel" data-motion={motion} hidden={!open} style={{ marginTop: 12 }}>
<p className="panel__title">A div and one attribute</p>
<p className="panel__body">
No framework, no JavaScript animation, no wrapper component. Toggling hidden is the
entire integration.
</p>
</div>
</>
)
}motion prop is the only difference between them.