import { TemplateResult } from 'lit';
import { BahtElement } from '../base.js';
import { IconName } from './icons.js';
export type ButtonVariant = 'primary' | 'secondary' | 'ghost' | 'danger';
export type ButtonSize = 'sm' | 'md' | 'lg';
/**
 * Design-system button (20baht: no scale, no shadow change — color does the work).
 * Standalone primitive: children become the label, listen for the native `click`.
 * (Light DOM has no <slot>, so the initial children are moved into the button.)
 *
 *   <baht-button variant="danger" size="sm">Delete</baht-button>
 *   <baht-button label="Save workflow"></baht-button>
 *   <baht-button icon="copy" variant="ghost" size="sm">Copy</baht-button>
 *   <baht-button icon="close" icon-only label="Close"></baht-button>  <!-- label = a11y name -->
 *   <baht-button aria-label="Previous month">‹</baht-button>  <!-- glyph child, host aria-label wins -->
 *   <baht-button variant="secondary" shortcut="alt+q">Close</baht-button>  <!-- ⌥Q / Alt+Q -->
 *
 * `shortcut` binds a document-wide key combo that clicks the button (NOTES 2026-10-31):
 * hover/focus shows a tooltip with the label and the keys (`⌥Q` on Mac, `Alt+Q`
 * elsewhere) and the inner button gets `aria-keyshortcuts`. Disabled buttons, buttons
 * outside the topmost open `<baht-modal>`, and modifier-less combos while typing in a
 * field never fire.
 */
export declare class BahtButton extends BahtElement {
    variant: ButtonVariant;
    size: ButtonSize;
    disabled: boolean;
    /** Forwarded to the native button — 'button' (default) or 'submit'. */
    type: 'button' | 'submit';
    /** Alternative to children for setting the label programmatically. */
    label: string;
    /** Optional leading icon from the curated set (copy/check/download/…). */
    icon: IconName | '';
    /** Square icon-only button. Requires `label` for the accessible name. */
    iconOnly: boolean;
    /**
     * A host `aria-label` never reaches assistive tech on its own — light DOM has no
     * implicit ARIA relationship between a custom element and its rendered children, so an
     * `aria-label` written on `<baht-button>` stays on the host and the inner native
     * `<button>` keeps whatever text (or none) is inside it. Mirroring the attribute into
     * this property forwards it to the inner button's `aria-label`, taking priority over
     * `label`/icon-only fallback — this is how a glyph-only child (e.g. `‹`) gets a real
     * accessible name without `icon-only`. Mapped to the plain `aria-label` attribute so
     * hosts write it the way they naturally would; kept off the `ariaLabel` IDL accessor to
     * avoid shadowing the platform's own ARIAMixin.
     */
    hostAriaLabel: string;
    /**
     * Keyboard shortcut that clicks this button from anywhere on the page, e.g. `alt+q`,
     * `shift+alt+s`, `mod+enter` (`mod` = ⌘ on Mac, Ctrl elsewhere). Also shown in a
     * hover/focus tooltip and announced through `aria-keyshortcuts`.
     */
    shortcut: string;
    /** Where the shortcut tooltip sits. */
    tooltipPosition: 'top' | 'bottom';
    private buttonEl;
    private mac;
    private childText;
    private tipDismissed;
    private unbind;
    connectedCallback(): void;
    disconnectedCallback(): void;
    private rebind;
    protected firstUpdated(): void;
    protected updated(changed: Map<PropertyKey, unknown>): void;
    private renderTip;
    private readonly dismissTip;
    private readonly rearmTip;
    protected render(): TemplateResult;
}