import * as _angular_core from '@angular/core'; /** * Headless implementation of the [WAI-ARIA Button pattern](https://www.w3.org/WAI/ARIA/apg/patterns/button/). * * Works on a native ` * * *
Click me
* * * * ``` */ declare class ForButton { #private; /** * When `true`, activation (click, Enter, Space) is suppressed and the element * reflects `aria-disabled="true"` + `data-disabled=""`. The element remains * focusable so assistive technology can announce it. Read * {@link effectiveDisabled} for the value that actually gates behavior — it * also folds in a surrounding disabled `[forFieldset]`. */ readonly disabled: _angular_core.InputSignalWithTransform; /** * The button's own {@link disabled} OR'd with a surrounding disabled * `[forFieldset]`. This is what gates activation and drives `aria-disabled` / * `data-disabled`: a native `
` never reaches a non-native * host (`
`), so the group's disabled state has to compose in * here. Mirrors `FormUiControlBase.effectiveDisabled`, so a `[forButton]` and * a `[forSwitch]` inside the same disabled group behave identically. */ readonly effectiveDisabled: _angular_core.Signal; /** * Emitted once per user activation: a pointer click on any host, or Enter / Space * on a non-native-button host (native buttons synthesize click from keyboard). */ readonly activate: _angular_core.OutputEmitterRef; protected readonly hovered: _angular_core.Signal; protected readonly pressed: _angular_core.Signal; protected readonly focusVisible: _angular_core.Signal; protected readonly resolvedType: _angular_core.Signal; protected readonly resolvedRole: _angular_core.Signal<"button" | null>; protected readonly resolvedTabindex: _angular_core.Signal; protected onClick(event: MouseEvent): void; protected onKeydown(event: KeyboardEvent): void; protected onKeyup(event: KeyboardEvent): void; protected onFocusIn(): void; protected onFocusOut(): void; static ɵfac: _angular_core.ɵɵFactoryDeclaration; static ɵdir: _angular_core.ɵɵDirectiveDeclaration; } export { ForButton };