import { type Placement } from '@floating-ui/dom';
import type { Snippet } from 'svelte';
type Props = {
    /** Floating UI placement. @default 'bottom-start' */
    position?: Placement;
    disabled?: boolean;
    /** Use `position: fixed` strategy (helpful inside overflow-clipped containers). */
    fixedPosition?: boolean;
    /** Distance in px between the trigger and the popover content. @default 4 */
    offset?: number;
    /** Padding in px from the viewport boundary before content shifts/flips. @default 8 */
    boundaryMargin?: number;
    /** Render a semi-transparent backdrop behind the content. */
    backdrop?: boolean;
    /** Make the content match the trigger element width, overriding `--sc-kit--popover--content--min-width` (never growing past the available space). */
    matchWidth?: boolean;
    /** Apply built-in panel styling (background, shadow, border-radius). @default true */
    panel?: boolean;
    /** Keep the popover open on any click inside the content (useful when the content is interactive). Per-item `keepOpen` and `use:popoverIgnore` still work for fine-grained control. */
    keepOpen?: boolean;
    /** Make the trigger fill its parent's box: `width:100%; height:100%`, centered, `border-radius: inherit`. Use when Popover sits inside a wrapper that owns the visible click surface (icon squares, list rows, etc.). */
    fillContainer?: boolean;
    /** Keep the trigger in the tab order. Turn off only when the same state is reachable by keyboard elsewhere — the popover becomes mouse-only. @default true */
    tabbable?: boolean;
    on?: {
        opened?: () => void;
        closed?: () => void;
    };
    children: Snippet;
    /**
     * Custom trigger content; defaults to a chevron-down icon. Renders inside the trigger `<button>`,
     * so content MUST be non-interactive — for a button-looking trigger use `Button` with
     * `type="presentational"`. Nesting an interactive element triggers a dev-only warning.
     */
    trigger?: Snippet;
    /** Accessible name for the trigger button — required when the trigger content carries no text (an icon-only trigger). */
    'aria-label'?: string;
};
/**
 * Popover — floating content anchored to a trigger element. Click trigger to open;
 * click outside, Escape, or click inside content (default) to close. Use `popoverIgnore`
 * action on a sub-tree to keep the popover open when clicks land inside that sub-tree.
 *
 * The trigger renders inside a `<button>`, so trigger content must be non-interactive (an icon,
 * text). For a button-looking trigger, pass `Button` with `type="presentational"` (a styled `<span>`)
 * — never an interactive element, which would nest inside the trigger `<button>`. A dev-only guard
 * warns and outlines the trigger in red if interactive content is detected.
 *
 * `tabbable={false}` drops the trigger out of the tab order, leaving it mouse-only — legitimate only when
 * the same state can be reached by keyboard through another control (as in `UrlInput`, where typing a
 * protocol into the field does what the picker does). Never reach for it just to shorten a tab sequence.
 *
 * Imperative control via `bind:this` — the component exports `open()`, `close()`, `toggle()`
 * methods; type the ref with the exported `PopoverInstance` type.
 *
 * With `panel` on, content sizes to `max-content` and, above the `min-width` floor, never exceeds the room Floating UI measures around the trigger: the `size()` middleware feeds the space left after
 * `flip` / `shift` into the max-width / max-height defaults. So the panel always has a definite width — which is what makes a consumer's own
 * `text-overflow: ellipsis` (on a `min-inline-size: 0` flex child) resolve inside the panel — and a long list scrolls instead of running off-screen. Set
 * `--sc-kit--popover--content--max-width` for a tighter cap than the available space.
 *
 * Because the panel fits itself to the available height, it is a scroll container by default. With `panel={false}` none of the three bounds apply — no width
 * cap, no height fit, no clipping — since that consumer owns the box entirely. Floating content nested inside it — a submenu, a `Tooltip` on
 * an item — is not clipped **once the panel has appeared**: those bubbles resolve their position against the popover's own positioned box, which sits outside
 * the scrolling area, so `fixedPosition` on a nested Popover stays optional. During the appear animation the panel does carry a transform and therefore does
 * clip, so a bubble opening within that window (a `Tooltip` with a near-zero `delay`) is cut off for its duration.
 *
 * Two consequences of the panel being a scroll container. `--sc-kit--popover--content--overflow: visible` removes the clipping but not the height fit — the
 * panel is still shrunk and its content would paint outside the chrome, so pair it with `--sc-kit--popover--content--max-height: none` to opt out of both. And
 * the clip is tight to the panel's box, whose inline padding is `0` by default: content that paints a focus ring outside its own border box (kit's pattern is
 * `outline: 2px` + `outline-offset: 2px`, so 4px) needs inline padding of its own — either via `--sc-kit--popover--content--padding` or a wrapper. `PopoverItem`
 * already carries the margin that keeps it clear.
 *
 * ### CSS Custom Properties
 * | Property | Description | Default |
 * |---|---|---|
 * | `--sc-kit--popover--width` | Trigger width (the trigger fills it). `max-content` ⇒ shrink to content; set `100%` for a full-width trigger | `max-content` |
 * | `--sc-kit--popover--content--background` | Content background | `var(--sc-kit--color--bg--panel)` |
 * | `--sc-kit--popover--content--border-color` | Content border color | `var(--sc-kit--color--border)` |
 * | `--sc-kit--popover--content--border-radius` | Content corner radius | `var(--sc-kit--radius--md)` |
 * | `--sc-kit--popover--content--box-shadow` | Content shadow | `var(--sc-kit--shadow--lg)` |
 * | `--sc-kit--popover--content--max-height` | Content max height. Applies only with `panel` on — a `panel={false}` consumer owns its own bounds | available height around the trigger |
 * | `--sc-kit--popover--content--max-width` | Content max width — the upper bound content shrinks against. Applies only with `panel` on | available width around the trigger |
 * | `--sc-kit--popover--content--min-width` | Content min width. Wins over max-width when the two conflict; ignored under `matchWidth` | `12.5rem` |
 * | `--sc-kit--popover--content--overflow` | Panel overflow, both axes. Applies only with `panel` on. `visible` opts out of clipping | `hidden auto` |
 * | `--sc-kit--popover--content--padding` | Content padding | `var(--sc-kit--space--1) 0` |
 * | `--sc-kit--popover--content--z-index` | Content z-index | `var(--sc-kit--z-index--popover)` |
 *
 * Props for keeping the popover open during interaction:
 * - `keepOpen` (Popover-level): block any inner click from closing — for interactive content (color pickers, emoji panels, etc.).
 * - `keepOpen` (PopoverItem-level): block close only for clicks on that specific item.
 * - `use:popoverIgnore={true}` action: block close for clicks anywhere in the marked sub-tree.
 */
declare const Cmp: import("svelte").Component<Props, {
    /** Imperative API — bind:this on the component to access. */ open: () => void;
    close: () => void;
    toggle: () => void;
}, "">;
type Cmp = ReturnType<typeof Cmp>;
export default Cmp;