/**
 * THE TWO DISMISSALS NO OVERLAY LIBRARY PERFORMS, stated once.
 *
 * Both are about a press or a movement the overlay's own outside-press listener
 * cannot observe, and both are the ANCHORED presentation's alone: a modal sheet
 * covers the page, so nothing under it scrolls and nothing under it takes a
 * press.
 */
/**
 * THE ONE PRESS AN OUTSIDE-PRESS LISTENER CANNOT SEE: one that lands inside a
 * cross-origin iframe. Those events are dispatched in the frame's own document
 * and never cross into this one, so an overlay anchored over an embedded app
 * stays open while the reader clicks underneath it. Focus is the signal that
 * survives the boundary — and checking `activeElement` is what keeps this from
 * over-firing, since a window blur alone also means "switched tab".
 */
export declare function useIframeDismiss(active: boolean, dismiss: () => void): void;
/**
 * A SCROLL THAT MOVES THE ANCHOR IS THE READER MOVING ON, so the panel is
 * dismissed rather than chased — as a native `<select>` and most menu systems
 * do. Neither Base UI's positioner nor its dismissal has one of these: the
 * positioner tracks the anchor off-screen instead.
 *
 * "Moves the anchor" is the whole test, and it is why the scroller is asked to
 * CONTAIN it: the panel's own list, a dialog opened from within it and a deeper
 * overlay all scroll boxes that hold no anchor, while the page and any container
 * the trigger sits in hold one. Capture, because a nested scroller's event does
 * not bubble.
 *
 * `anchor` is read at scroll time rather than held, because the element the
 * overlay is measured against is not always mounted when this arms.
 */
export declare function useAnchorScrollDismiss(active: boolean, anchor: () => Element | null, dismiss: () => void): void;