` wrapper element around its children. You can treat this\\ncomponent as a `
`, since extra props will be forwarded down to the DOM element. For example,\\nyou can add an `onClick` handler. You may also customize the tag name of the generated wrapper\\nelement using the `tagName` prop. Note that the generated popover will be rendered as a _sibling_\\nof this wrapper element.\\n\\n### Advanced usage\\n\\nBy default, `
` will render a wrapper element around its children to attach an event handler\\nand get a DOM ref for theme detection. If this wrapper element breaks your HTML and/or CSS layout in\\nsome way and you wish to omit it, you may do so by utilizing ContextMenu\'s advanced rendering API\\nwhich uses a `children` render function. If you use this approach, you must take care to properly use\\nall the render props supplied to the `children()` function:\\n\\n```tsx\\nimport classNames from \\"classnames\\";\\nimport { ContextMenu, ContextMenuChildrenProps, Menu, MenuItem } from \\"@blueprintjs/core\\";\\n\\nexport default function AdvancedContextMenuExample() {\\n return (\\n \\n \\n \\n \\n \\n }\\n >\\n {(ctxMenuProps: ContextMenuChildrenProps) => (\\n \\n {ctxMenuProps.popover}\\n Right click me!\\n \\n )}\\n \\n )\\n}\\n```\\n\\nBoth `content` and `children` props support the [render prop](https://reactjs.org/docs/render-props.html)\\npattern, so you may use information about the context menu\'s state (such as `isOpen: boolean`) in your\\nrender code.\\n\\n@## Props interface\\n\\nTo enable/disable the context menu popover, use the `disabled` prop. Note that it is inadvisable to change\\nthe value of this prop inside the `onContextMenu` callback for this component; doing so can lead to unpredictable\\nbehavior.\\n\\n@interface ContextMenuProps","metadata":{}},"dialog":{"reference":"dialog","route":"core/components/dialog","sourcePath":"packages/core/src/components/dialog/dialog.md","title":"Dialogs","contents":[{"level":1,"route":"core/components/dialog","tag":"heading","value":"Dialogs"},"
Dialog presents content overlaid over other parts of the UI.
\\n
\\n
Terminology note
\\n\\n
The term "modal" is sometimes used to mean "dialog," but this is a misnomer.\\nModal is an adjective that describes parts of a UI. An element is considered to be "modal" if it\\nblocks interaction with the rest of the application.\\nWe use the term "dialog" in Blueprint to avoid confusion with the adjective.
\\n
\\n\\n
Blueprint provides two types of dialogs:
\\n
\\n- Standard dialog: show single view using the
<Dialog> component \\n- Multi-step dialog: show multiple sequential views using the
<MultistepDialog> component. \\n
\\n",{"level":2,"route":"core/components/dialog.dialog","tag":"heading","value":"Dialog"},{"tag":"reactExample","value":"DialogExample"},"
A standard Dialog renders its contents in an Overlay with a\\nClasses.DIALOG element. You can use some simple dialog markup sub-components or CSS classes\\nto structure its contents:
\\n
<Dialog title="Informational dialog" icon="info-sign">\\n <DialogBody>\\n {/* body contents here */}\\n </DialogBody>\\n <DialogFooter actions={<Button intent="primary" text="Close" onClick={/* ... */} />} />\\n</Dialog>",{"level":3,"route":"core/components/dialog.dialog-props","tag":"heading","value":"Dialog props"},"
<Dialog> is a stateless React component controlled by the isOpen prop.
\\n
The children you provide to this component are rendered as contents inside the\\nClasses.DIALOG element.
\\n",{"tag":"interface","value":"DialogProps"},{"level":3,"route":"core/components/dialog.dialog-body-props","tag":"heading","value":"Dialog body props"},"
<DialogBody> renders a Classes.DIALOG_BODY element, optionally with a constrained container\\nheight which allows vertical scrolling of its content.
\\n",{"tag":"interface","value":"DialogBodyProps"},{"level":3,"route":"core/components/dialog.dialog-footer-props","tag":"heading","value":"Dialog footer props"},"
<DialogFooter> renders a Classes.DIALOG_FOOTER element. Footer "actions" are rendered\\ntowards the right side of the footer container element.
\\n",{"tag":"interface","value":"DialogFooterProps"},{"level":3,"route":"core/components/dialog.css-api","tag":"heading","value":"CSS API"},"
\\n
\\n\\n
Deprecated API: use <Dialog>
\\n\\n\\n
CSS APIs for Blueprint components are considered deprecated, as they are verbose, error-prone, and they\\noften fall out of sync as the design system is updated. You should use the React component APIs instead.
\\n
\\n\\n",{"tag":"css","value":"dialog"},{"level":2,"route":"core/components/dialog.multistep-dialog","tag":"heading","value":"Multistep dialog"},{"tag":"reactExample","value":"MultistepDialogExample"},{"level":3,"route":"core/components/dialog.multistep-dialog-props","tag":"heading","value":"Multistep dialog props"},"
MultistepDialog is a wrapper around Dialog that displays a dialog with multiple steps. Each step has a\\ncorresponding panel.
\\n
This component expects <DialogStep> child elements: each "step" is rendered in order and its panel is shown as the\\ndialog body content when the corresponding step is selected in the navigation panel.
\\n",{"tag":"interface","value":"MultistepDialogProps"},{"level":3,"route":"core/components/dialog.dialogstep","tag":"heading","value":"DialogStep"},"
DialogStep is a minimal wrapper with no functionality of its own—it is managed entirely by its parent\\nMultistepDialog container. Typically, you should render a <DialogBody> element as the panel element. A step's\\ntitle text can be set via the title prop.
\\n",{"tag":"interface","value":"DialogStepProps"}],"contentsRaw":"@# Dialogs\\n\\n__Dialog__ presents content overlaid over other parts of the UI.\\n\\n
\\n
Terminology note
\\n\\nThe term \\"modal\\" is sometimes used to mean \\"dialog,\\" but this is a misnomer.\\n_Modal_ is an adjective that describes parts of a UI. An element is considered to be \\"modal\\" if it\\n[blocks interaction with the rest of the application](https://en.wikipedia.org/wiki/Modal_window).\\nWe use the term \\"dialog\\" in Blueprint to avoid confusion with the adjective.\\n\\n\\n\\nBlueprint provides two types of dialogs:\\n\\n1. Standard dialog: show single view using the `