import type { PropsLike } from "../merge-props-n.js";
/**
 * Accessor-or-value input. Consumers may pass a plain boolean/number or a
 * reactive accessor; we always coerce via `read()` at call time.
 */
type MaybeAccessor<T> = T | (() => T);
/**
 * Parameters for {@link useButton}. Each flag may be a plain value or an
 * accessor so consumers can thread reactive state in without us having to
 * re-create the primitive on every change.
 */
export interface UseButtonOptions {
    /**
     * Whether the component should ignore user interaction.
     * @default false
     */
    disabled?: MaybeAccessor<boolean | undefined> | undefined;
    /**
     * Whether the button may receive focus even if it is disabled.
     * @default false
     */
    focusableWhenDisabled?: MaybeAccessor<boolean | undefined> | undefined;
    /**
     * `tabindex` when non-composite. Ignored when `composite` is true.
     * @default 0
     */
    tabIndex?: MaybeAccessor<number | undefined> | undefined;
    /**
     * Whether the component is being rendered as a native `<button>`.
     * @default true
     */
    native?: MaybeAccessor<boolean | undefined> | undefined;
    /**
     * Whether the button is part of a composite widget. When `true`, keyboard
     * activation for Space occurs on keydown rather than keyup.
     * @default false
     *
     * (Base UI React looks this up from a CompositeRoot context by default; the
     * Solid port leaves context discovery to callers until CompositeRoot is
     * ported.)
     */
    composite?: MaybeAccessor<boolean | undefined> | undefined;
}
/**
 * Return value of {@link useButton}.
 */
export interface UseButtonReturn {
    /**
     * A reactive props source to pass into `renderElement`'s `params.props`
     * array. Contains the button-specific handlers plus (when applicable)
     * `role`, `type`, `tabIndex`, `aria-disabled`, and `disabled`.
     *
     * Typed as `PropsLike` so it composes with `mergePropsN` / `renderElement`
     * without per-component casts. Consumers don't read individual fields off
     * of this — they pass it through the merge pipeline.
     */
    props: PropsLike;
    /**
     * Stable ref callback to attach to the rendered element. Compose with
     * other refs via Solid 2's array form (`ref={[a, buttonRef]}`).
     */
    ref: (element: HTMLElement | null) => void;
}
/**
 * Shared primitive powering `<Button>`, `<Toggle>`, and other button-shaped
 * components.
 *
 * Responsibilities mirror Base UI React's `useButton`:
 *
 * 1. Native path: lets the browser handle activation; threads `disabled` and
 *    defaults `type="button"`.
 * 2. Non-native path: adds `role="button"`, synthesizes click events on
 *    Enter/Space via `HTMLElement.click()` so consumer `onClick` handlers
 *    still fire through the normal DOM path, and sets `tabIndex`.
 * 3. Disabled handling: suppresses pointer/keyboard events via Base UI's
 *    `preventBaseUIHandler()` so chained consumer handlers don't run. Focus
 *    and blur events are NOT suppressed — this matches React Base UI, which
 *    deliberately lets focusableWhenDisabled components still observe focus
 *    transitions.
 *
 * Solid-specific decisions:
 *
 * - Inputs accept accessors so consumers can pass `() => props.disabled`
 *   without materializing a memo. All reads happen inside event handlers
 *   (call-time), so top-level reactive reads don't fire.
 * - Clicks are synthesized via `currentTarget.click()` rather than by calling
 *   a captured `externalOnClick` closure — the Solid merge pipeline keeps
 *   consumer handlers separate, so dispatching a real DOM click lets them
 *   fire through the normal right-to-left chain in `mergePropsN`.
 * - The `buttonRef` is a stable callback; Solid's native array-ref form
 *   (RFC 07) is used at the call site to compose with other refs.
 *
 * Reactivity notes:
 *
 * - The element is tracked in an internal signal with `ownedWrite: true` so
 *   the ref callback (unowned) can write to it without tripping the
 *   `SIGNAL_WRITE_IN_OWNED_SCOPE` diagnostic.
 * - The dev-mode native-button mismatch warning is wired up with a split
 *   `createEffect` — the compute half reads the element and the `native`
 *   flag; the apply half does the console.error.
 */
export declare function useButton(options?: UseButtonOptions): UseButtonReturn;
export {};
//# sourceMappingURL=use-button.d.ts.map