/**
 * @oxpulse/chat-widget — ReactionTrigger (reactions quick-bar redesign,
 * heart-first amendment 2026-07-14, reuse-update pass).
 *
 * Wired to a single heart button per bubble:
 *   - Tap/click (no preceding hold) → onToggle() — instant add/remove/
 *     replace-to-heart, handled by the caller.
 *   - Touch/pen: press-and-hold ≥400ms → onOpenBar() — reveals the full
 *     ReactionQuickBar. Movement >10px cancels (scroll wins) and suppresses
 *     the trailing click too (a drag gesture is not a tap). Long-press
 *     timing/gating ported from oxpulse-chat web's
 *     `web/src/lib/chat/list/usePopover.svelte.ts` (LONG_PRESS_MS=400,
 *     POINTER_CANCEL_PX=10, mouse excluded from this path).
 *   - Mouse: no long-press — instead a hover-intent ≥400ms scoped to THIS
 *     button (not the bubble) reveals the bar (TG-desktop pattern). Leaving
 *     before 400ms cancels; once opened there is no auto-hide-on-leave —
 *     ReactionQuickBar owns its own dismissal (Escape/outside-click/select).
 *   - ArrowUp → onOpenBar() (keyboard/SR path to the full bar).
 *   - Enter/Space → native <button> activation behavior fires a 'click'
 *     event; this class only needs a click listener, not a reimplementation
 *     of keyboard activation.
 *
 * Browsers fire a native 'click' on pointerup at the same target regardless
 * of how long the pointer was held — a completed touch/pen hold (onOpenBar
 * already fired) or a cancelled-by-movement hold must suppress that
 * trailing click so the heart doesn't ALSO toggle. Mouse never sets this
 * suppression — its hover-intent and click paths are independent (hover
 * never consumes a click the way a touch/pen long-press does).
 */
/** Which affordance opened the bar — the caller (MessageList) uses this to
 *  decide whether to move focus into the bar (review fix CRITICAL#2,
 *  2026-07-14): 'hover' must NOT steal focus (the user's pointer merely
 *  rested on the button — they could be typing elsewhere), while 'hold'
 *  and 'keyboard' are deliberate actions that should still focus the bar. */
export type ReactionTriggerOpenSource = 'hold' | 'hover' | 'keyboard';
export interface ReactionTriggerOptions {
    /** The heart button — hold/hover/click/ArrowUp target, contextmenu suppression scope. */
    element: HTMLElement;
    /** Called on a plain tap/click (not preceded by a completed or cancelled touch/pen hold). */
    onToggle: () => void;
    /** Called when a ≥400ms touch/pen hold, a ≥400ms mouse hover, or ArrowUp fires. */
    onOpenBar: (source: ReactionTriggerOpenSource) => void;
    /** Optional abort signal — destroys the trigger when it fires. */
    signal?: AbortSignal;
    longPressDelayMs?: number;
    longPressMoveCancelPx?: number;
    hoverDelayMs?: number;
    suppressClickGuardMs?: number;
}
/** Ported from usePopover.svelte.ts's LONG_PRESS_MS. */
export declare const DEFAULT_LONG_PRESS_DELAY_MS = 400;
/** Ported from usePopover.svelte.ts's POINTER_CANCEL_PX. */
export declare const DEFAULT_LONG_PRESS_MOVE_CANCEL_PX = 10;
/** Mouse hover-intent delay — same budget as the touch/pen hold (reuse-update). */
export declare const DEFAULT_HOVER_DELAY_MS = 400;
/** Review fix LOW#9: #suppressNextClick expects a trailing native click to
 *  consume it. If pointerup lands off-element (no click ever fires) the
 *  flag would otherwise dangle true and wrongly swallow a later, unrelated
 *  genuine tap — this bounds how long the suppression can outlive the
 *  gesture that armed it. Generously short relative to the 400ms
 *  interaction delays; a real click fires within the same event tick as
 *  pointerup, so this only ever fires for the "click never came" case. */
export declare const DEFAULT_SUPPRESS_CLICK_GUARD_MS = 300;
export declare class ReactionTrigger {
    #private;
    constructor(opts: ReactionTriggerOptions);
    /** Tear down all listeners and clear any pending timer. Idempotent. */
    destroy(): void;
}
//# sourceMappingURL=reaction-trigger.d.ts.map