--- url: /reference/items/ClickOutside/examples.md --- # Examples ## Expandable card The simplest pairing: `ClickOutside` and `Action` share the same element and each effect toggles a single class. Clicking the card opens it, clicking anywhere outside collapses it. Because the trigger is the element itself, the opening click is always *inside* and never fights the close. :::code-group ```js import { registerComponent } from '@studiometa/js-toolkit'; import { Action, ClickOutside } from '@studiometa/ui'; registerComponent(Action); registerComponent(ClickOutside); ``` ::: ## Inline edit A label turns into an input on click and commits back to a static label when a click lands outside. Keeping the input *inside* the `ClickOutside` element is what makes this reliable — clicking the field never triggers the outside-click that would close the editor. :::code-group ```js import { registerComponent } from '@studiometa/js-toolkit'; import { Action, ClickOutside } from '@studiometa/ui'; registerComponent(Action); registerComponent(ClickOutside); ``` ::: ::: tip Keep the trigger inside `ClickOutside` reports every click that lands outside its root element. If the control that *opens* a panel sits outside that element, the very click that opens it will also be seen as an outside click and immediately close it again. Nest the trigger inside the `ClickOutside` element — as in both examples above and the [dropdown on the overview page](./index.md) — to avoid this. :::