Files
zeekayandHanzo Dev 751ef5c778 rename the framework to @hanzo/gui and the loader to @hanzogui/loader
Both old names are owned by a different npm account (artemis-prime), so
publishing them returns 403 — which is how this surfaced: the 8.0.0 run
shipped @hanzogui/logo and @hanzogui/demos depending on [email protected], a
version that cannot be published and therefore does not exist. Those two
were uninstallable.

@hanzo/gui and @hanzogui/* are ours, so the framework now carries the name
it is imported by everywhere downstream, and the loader moves under the
scope we control.

The rewrite is limited to package references. `DEBUG?.startsWith('hanzogui')`
is a log-namespace filter and join(dir, 'hanzogui') is a path — rewriting
either would change behaviour, so both are untouched.

Co-authored-by: Hanzo Dev <[email protected]>
2026-07-30 20:23:18 -07:00

393 lines
10 KiB
Plaintext

---
title: Dialog
description: Show a modal with configurable layout and accessible actions
name: dialog
component: Dialog
package: dialog
demoName: Dialog
---
<HeroContainer showAnimationDriverControl>
<DialogDemo />
</HeroContainer>
```tsx hero template=Dialog
```
<Highlights
features={[
`Comes with styling, yet completely customizable and themeable.`,
`Accepts animations, themes, size props and more.`,
`Accessible with dev-time checks to ensure ARIA props.`,
]}
/>
Dialog is a great way to show content inside a new floating window above
content. Dialogs [automatically stack](/ui/z-index) above other overlays. Be sure to open the code example above for a copy-paste implementation.
## Installation
Dialog is already installed in `hanzogui`, or you can install it independently:
```bash
npm install @hanzogui/dialog
```
<Notice theme="blue">
For native apps, we recommend [setting up native
portals](/docs/components/portal#native-portal-setup-recommended) to preserve React
context inside Dialog content.
</Notice>
## Anatomy
```tsx
import { Dialog } from '@hanzo/gui' // or '@hanzogui/dialog'
export default () => (
<Dialog>
<Dialog.Trigger />
<Dialog.Portal>
<Dialog.Overlay />
<Dialog.Content>
<Dialog.Title />
<Dialog.Description />
<Dialog.Close />
{/* ... */}
</Dialog.Content>
</Dialog.Portal>
{/* Optional: Control focus behavior */}
<Dialog.FocusScope loop trapped focusOnIdle={true}>
<Dialog.FocusScope.Scope>
{/* Focus scope will be applied to children */}
</Dialog.FocusScope.Scope>
</Dialog.FocusScope>
</Dialog>
)
```
## Scoping
Dialog supports scoping which lets you mount one or more Dialog instances at the
root of your app, while having a deeply nested child Trigger or Content attach
to the proper parent Dialog instance.
In performance sensitive areas you may want to take advantage of this, it allows
you to only need to render the Dialog.Trigger inside the sensitive area as
Dialogs aren't the cheapest component - they have a lot of functionality.
Here's the basic anatomy of using `scope` and placing your Dialog higher up for
performance:
```tsx fileName=_layout.tsx
import { Dialog } from '@hanzo/gui'
// in your root layout:
export default ({ children }) => (
<Dialog scope="user-profile">
<Dialog.Portal>
<Dialog.Overlay />
<Dialog.Content>
<Dialog.Title />
<Dialog.Description />
<Dialog.Close />
{/* ... */}
</Dialog.Content>
</Dialog.Portal>
{/* the rest of your app, note that it's inside of Dialog */}
{children}
</Dialog>
)
```
```tsx fileName=UserProfile.tsx
export default () => (
<Dialog.Trigger scope="user-profile">
<Button>Open Profile</Button>
</Dialog.Trigger>
)
```
Note that the `Trigger` scope ties to the `Dialog` scope.
## Dismissal Behavior
By default, dialogs can be dismissed by:
- Clicking outside the dialog content (on the overlay)
- Pressing the Escape key
- Clicking a Dialog.Close element
### Modal vs Non-Modal Dialogs
- **Modal dialogs** (`modal={true}`, which is the default):
- In v1, have `disableOutsidePointerEvents` set to `true` by default
- Still dismiss on outside click, but prevent interaction with elements behind the dialog
- Prevent right-click dismissal (right-clicks on the overlay are ignored)
- **Non-modal dialogs** (`modal={false}`):
- Allow interaction with elements behind the dialog
- Dismiss on any outside click
- Do not trap focus
### Preventing Outside Dismissal
To prevent a dialog from closing when clicking outside:
```tsx
<Dialog.Content
onPointerDownOutside={(event) => {
event.preventDefault()
}}
>
{/* Dialog contents */}
</Dialog.Content>
```
## API Reference
### Dialog
Contains every component for the dialog. Beyond
[Gui Props](/docs/intro/props), adds:
<PropsTable
data={[
{
name: 'children',
type: 'React.ReactNode',
required: true,
description: `Must contain Dialog.Content`,
},
{
name: 'size',
type: 'SizeTokens',
description: `Passes size down to all sub-components when set for padding, arrow, borderRadius.`,
},
{
name: 'open',
type: 'boolean',
description: `Controlled open state of the dialog.`,
},
{
name: 'defaultOpen',
type: 'boolean',
description: `Initial open state when uncontrolled.`,
},
{
name: 'onOpenChange',
type: '(open: boolean) => void',
description: `Called when the dialog opens or closes.`,
},
{
name: 'modal',
type: 'boolean',
default: 'true',
description: `Renders into root of app instead of inline.`,
},
{
name: 'keepChildrenMounted',
type: 'boolean',
default: 'false',
description: `When true, dialog content stays mounted in the DOM even when closed. Useful for preserving state across open/close cycles or when you need faster re-opening.`,
},
{
name: 'disableRemoveScroll',
type: 'boolean',
required: false,
description: `Used to disable the automatic removal of scrolling from the page when open.`,
},
]}
/>
### Dialog.Trigger
Just [Gui Props](/docs/intro/props).
### Dialog.Portal
Renders Dialog into appropriate container. Beyond
[Gui Props](/docs/intro/props), adds:
<PropsTable
data={[
{
name: 'forceMount',
type: 'boolean',
required: false,
description: `Used to force mounting when more control is needed. Useful when controlling animation with React animation libraries.`,
},
{
name: 'unstyled',
required: false,
type: `boolean`,
description: `Removes all default Gui styles.`,
},
]}
/>
### Dialog.Content
Main container for Dialog content, this is where you should apply animations.
Beyond [Gui Props](/docs/intro/props), adds:
<PropsTable
data={[
{
name: 'forceMount',
type: 'boolean',
required: false,
description: `Used to force mounting when more control is needed. Useful when controlling animation with React animation libraries.`,
},
{
name: 'unstyled',
required: false,
type: `boolean`,
description: `Removes all default Gui styles.`,
},
{
name: 'disableOutsidePointerEvents',
type: 'boolean',
required: false,
description: `When true, hover/focus/click interactions will be disabled on elements outside the Dialog. Users will need to click twice on outside elements to interact with them: once to close the Dialog, and again to trigger the element. Note: In v1, modal dialogs have this set to true by default.`,
},
]}
/>
### Dialog.Overlay
Displays behind Content. Beyond [Gui Props](/docs/intro/props), adds:
<PropsTable
data={[
{
name: 'forceMount',
type: 'boolean',
required: false,
description: `Used to force mounting when more control is needed. Useful when controlling animation with React animation libraries.`,
},
]}
/>
### Dialog.Title
Required. Can wrap in VisuallyHidden to hide.
Defaults to H2, see [Headings](/docs/components/headings).
### Dialog.Description
Required. Can wrap in VisuallyHidden to hide.
Defaults to Paragraph, see [Paragraph](/docs/components/text).
### Dialog.Close
Closes the Dialog, accepts the same props as YStack. Recommended to use with
your own component and `asChild`.
<PropsTable
data={[
{
name: 'displayWhenAdapted',
type: 'boolean',
description: `By default Close elements hide when Adapt is active. If set to true, they will show when adapted.`,
},
]}
/>
Just [Gui Props](/docs/intro/props).
### Dialog.FocusScope
Provides access to the underlying FocusScope component used by Dialog for focus
management. Can be used to control focus behavior from a parent component.
<PropsTable
data={[
{
name: 'enabled',
type: 'boolean',
default: 'true',
description: `Whether focus management is enabled`,
},
{
name: 'loop',
type: 'boolean',
default: 'false',
description: `When true, tabbing from last item will focus first tabbable and shift+tab from first item will focus last tabbable`,
},
{
name: 'trapped',
type: 'boolean',
default: 'false',
description: `When true, focus cannot escape the focus scope via keyboard, pointer, or programmatic focus`,
},
{
name: 'focusOnIdle',
type: 'boolean | number',
default: 'false',
description: `When true, waits for idle before focusing. When a number, waits that many ms. This prevents reflows during animations`,
},
{
name: 'onMountAutoFocus',
type: '(event: Event) => void',
description: `Event handler called when auto-focusing on mount. Can be prevented`,
},
{
name: 'onUnmountAutoFocus',
type: '(event: Event) => void',
description: `Event handler called when auto-focusing on unmount. Can be prevented`,
},
]}
/>
### Dialog.Sheet
When used with `Adapt`, Dialog will render as a sheet when that breakpoint is
active.
See [Sheet](/docs/components/sheet) for more props.
Must use `Adapt.Contents` inside the `Dialog.Sheet.Frame` to insert the contents
given to `Dialog.Content`
```tsx
import { Dialog } from '@hanzo/gui' // or '@hanzogui/dialog'
export default () => (
<Dialog>
<Dialog.Trigger />
<Dialog.Portal>
<Dialog.Overlay />
<Dialog.Content>
<Dialog.Title />
<Dialog.Description />
<Dialog.Close />
{/* ... */}
</Dialog.Content>
</Dialog.Portal>
{/* optionally change to sheet when small screen */}
<Dialog.Adapt when="max-md">
<Dialog.Sheet>
<Dialog.Sheet.Frame>
<Dialog.Adapt.Contents />
</Dialog.Sheet.Frame>
<Dialog.Sheet.Overlay />
</Dialog.Sheet>
</Dialog.Adapt>
</Dialog>
)
```
<Notice>
Note that Dialog.Sheet currently doesn't preserve state of the contents when it
transitions between Sheet and Portal. In the future, we can do this on the web using
react-reparenting.
</Notice>