import{type TemplateResult,type PropertyValues}from'lit';import{LyraElement}from'../../../internal/lyra-element.js';import type{LyraSize}from'../../../internal/variants.js';import{type FormOwnerValue}from'../../../internal/form-associated.js';import{type LyraFormValidator}from'../form-validator.js';export interface LyraSwitchEventMap{input:InputEvent;change:Event;'lr-input':CustomEvent<{checked:boolean;}>;'lr-change':CustomEvent<{checked:boolean;}>;focus:FocusEvent;blur:FocusEvent;'lr-invalid':CustomEvent<null>;'lr-switch-toggle-request':CustomEvent<{checked:boolean;}>;}
/**
* `<lr-switch>` — a boolean toggle-switch form control. Structurally the
* same idea as a checkbox (form-associated via `ElementInternals`, click and
* Space toggle) but with switch semantics: `role="switch"` +
* `aria-checked` read to assistive tech as an on/off state rather than a
* checked/unchecked one, and there is no indeterminate state.
*
* `checked` is not a plain string, so this attaches `ElementInternals`
* directly and implements its own `updateValidity()` rather than using the
* `FormAssociated` mixin (that mixin's `value` accessor assumes a string —
* see `<lr-combobox>` for the same direct-`ElementInternals` shape with a
* non-string value).
*
* Ships an opt-in `hint`/`errorText` form-control chrome (props + matching named slots +
* `hint`/`error` CSS parts), mirroring `<lr-select>`'s pattern for those two pieces -- left
* unset, neither renders. Deliberately no separate top-of-field `label` prop/slot/part mirroring
* `<lr-select>`'s `form-control-label`: the default slot already *is* this control's visible,
* clickable label (same as `<lr-checkbox>`), so a second label surface would be redundant.
* Its wrapper follows flattened rendered assignment and updates through forwarding slots. Visual
* elements, including decorative `aria-hidden` icons, retain the wrapper independently of their
* accessibility-tree contribution.
*
* Host `aria-describedby` references resolve onto the internal switch before its local error/hint
* guidance, tracking target changes, reconnect and document adoption. Removing `hint`, `help-text`
* or `error-text` safely omits the content while preserving native null property readback.
*
* @customElement lr-switch
* @slot - Label text, rendered next to the track. Clicking it toggles the
* switch, the same as clicking a checkbox's associated `<label>`. If left
* empty, set `aria-label` on the host so the control still has an accessible name. Host
* `aria-label` is forwarded by presence, including an explicitly empty value.
* @slot hint - Custom hint content.
* @slot help-text - Shoelace alias for `hint`.
* @slot error - Custom error content.
* @event {InputEvent} input - The user toggled the switch; bubbling and composed like a native form event.
* @event lr-input - Prefixed compatibility alias for `input`; `detail: { checked }`.
* @event {Event} change - Fired immediately after `input` for the same user toggle, matching the native
* checkbox/radio contract a form library expects from a boolean control.
* @event lr-change - Compatibility alias fired after `input` and `change` (click, Space, logical
* ArrowLeft/ArrowRight, or
* the programmatic `click()` activation path). `detail: { checked }`. Not fired for a plain
* `.checked` property assignment, `form.reset()`, session-state restoration, or a user toggle a
* listener refused through `lr-switch-toggle-request`.
* @event lr-switch-toggle-request - A user toggle (click, Space, the logical arrow keys, or the
* programmatic `click()` activation path) is about to change `checked`; `detail: { checked }`
* carries the state the control *would* take, and `checked` itself still holds the old value while
* this dispatches. Cancelable: calling `preventDefault()` keeps the current state, so the switch
* never slides at all rather than sliding and snapping back, and none of
* `input`/`lr-input`/`change`/`lr-change` fire. A listener may instead resolve the request by
* assigning `checked` itself during the dispatch, which suppresses the built-in write the same
* way. Not fired for a programmatic `.checked` assignment, while the control is disabled, or for
* an arrow key that names the state the switch already holds.
* @event focus - The internal switch control received focus. Bridges the internal element's
* non-bubbling native `focus`, re-dispatched as bubbling and composed.
* @event blur - The internal switch control lost focus. Bridges the internal element's
* non-bubbling native `blur`, re-dispatched as bubbling and composed.
* @event lr-invalid - The switch failed a validity check. Cancelable: calling
* `preventDefault()` also cancels the native `invalid` event behind it, suppressing the
* browser's own validation bubble so an app can present the failure its own way.
* @cssstate required - Matches while `required` is set. Style with `lr-switch:state(required)`.
* @cssstate optional - Matches while `required` is not set — the complement of `required`.
* @cssstate valid - Matches while the control satisfies its constraints, including any
* `setCustomValidity()` error.
* @cssstate invalid - Matches while it does not — from the very first render, before the user has
* touched anything.
* @cssstate user-valid - `valid`, but only after the user has interacted: a toggle the host
* allowed, a blur, `reportValidity()`, or a submission attempt. Not after a silent
* `checkValidity()` alone. A toggle refused through `lr-switch-toggle-request` is deliberately
* not one of them -- nothing changed, so nothing is revealed until the user interacts again.
* @cssstate user-invalid - `invalid` after that same interaction. Style validation errors with this
* rather than `invalid`: a pristine required switch is genuinely invalid, but colouring it red
* before the user has done anything is hostile.
* @cssstate checked - Matches while the live switch state is on.
* @cssstate disabled - Matches while disabled directly or by an ancestor fieldset.
* @csspart form-control - The outer wrapper around the switch, error and hint.
* @csspart row - The row wrapping the switch owner and the label as siblings. This is the node
*  to size or align when laying out a column of switches; `base`/`switch` is only the track box
*  inside it, so its inline size tracks the track, not the row.
* @csspart wrapper - Compatibility name on the semantic switch owner.
* @csspart base - Compatibility name for the semantic switch owner; use `switch`.
* @csspart switch - The interactive `role="switch"` owner around the track, with the rich default
*   label as a sibling so nested actions remain valid focus stops.
* @csspart track - The pill-shaped background.
* @csspart control - WA/Shoelace name for the same pill-shaped background.
* @csspart thumb - The circular knob that slides across the track.
* @csspart label - The wrapper around the default slot.
* @csspart hint - The hint message.
* @csspart form-control-help-text - Shoelace name for the same hint message.
* @csspart error - The error message.
* @cssprop [--lr-switch-gap=var(--lr-space-s)] - Gap between the track and label.
* @cssprop [--lr-switch-track-inline-size=calc(var(--lr-switch-track-block-size) * 1.8)] - Inline
*   size of the track, and (with the block size) the distance the thumb travels when checked.
*   Derived from the block size, so re-sizing the track keeps its aspect ratio.
* @cssprop [--lr-switch-track-block-size=calc(var(--lr-form-control-height) * 0.5)] - Block size of
*   the track, half the `size` tier's shared control height; the thumb's diameter is derived from
*   it minus twice `--lr-switch-thumb-offset`.
* @cssprop [--lr-switch-thumb-offset=var(--lr-size-2px)] - Inset of the thumb from the track's
*   edges.
* @cssprop [--lr-switch-track-fill=var(--lr-color-border)] - Resting fill of `[part='track']`,
*   used as the source for the hover and press fallbacks.
* @cssprop [--lr-switch-checked-track-fill=var(--lr-color-brand)] - Track fill while checked.
* @cssprop [--lr-switch-track-hover-fill=color-mix(...)] - Track fill while hovered.
* @cssprop [--lr-switch-track-active-fill=color-mix(...)] - Track fill while pressed.
* @cssprop --lr-switch-track-border - Border of `[part='track']`, and the checked-state fallback
*   when `--lr-switch-checked-track-border` is unset. Undeclared by default (no border renders at
*   all), matching today's chrome.
* @cssprop [--lr-switch-checked-track-border=var(--lr-switch-track-border)] - Border of
*   `[part='track']` while checked, independently themeable from the unchecked border, so a
*   bordered track can differ by state without reaching for `::part(track)` plus the `checked`
*   custom state. Takes a whole `border` shorthand value, like `--lr-switch-track-border`; give
*   both states the same border *width* unless a size change between them is what you want, since
*   the track is `box-sizing: content-box` and a border grows its outer footprint.
* @cssprop [--lr-switch-thumb-fill=var(--lr-color-surface)] - Thumb fill while unchecked, and the
*   checked-state fallback when `--lr-switch-checked-thumb-fill` is unset.
* @cssprop [--lr-switch-checked-thumb-fill=var(--lr-switch-thumb-fill)] - Thumb fill while
*   checked, independently themeable from the unchecked fill.
* @cssprop [--width=var(--lr-switch-track-inline-size)] - WA/Shoelace alias for the track's inline
* size.
* @cssprop [--height=var(--lr-switch-track-block-size)] - WA/Shoelace alias for the track's block
* size.
* @cssprop [--thumb-size=calc(var(--height, var(--lr-switch-track-block-size)) - (var(--lr-switch-thumb-offset) * 2))] - WA/Shoelace thumb diameter alias.
* @cssprop [--lr-switch-label-color=var(--lr-color-text)] - Text color of `[part='label']`, and
*   the checked-state fallback when `--lr-switch-checked-label-color` is unset.
* @cssprop [--lr-switch-checked-label-color=var(--lr-switch-label-color)] - Text color of
*   `[part='label']` while checked, independently themeable from the unchecked color.
* @status stable
* @since 4.0.0
*/
export declare class LyraSwitch extends LyraElement<LyraSwitchEventMap>{
/** Public WA-compatible intrinsic validator catalog. */
static get validators():LyraFormValidator<LyraSwitch>[];static styles:import("lit").CSSResultGroup[];static formAssociated:boolean;static properties:{customError:{attribute:string;reflect:boolean;noAccessor:boolean;};checked:{attribute:boolean;noAccessor:boolean;};defaultChecked:{attribute:string;type:BooleanConstructor;reflect:boolean;useDefault:boolean;noAccessor:boolean;};disabled:{type:BooleanConstructor;reflect:boolean;noAccessor:boolean;};name:{reflect:boolean;noAccessor:boolean;converter:import("lit").ComplexAttributeConverter<string,unknown>;};required:{type:BooleanConstructor;reflect:boolean;noAccessor:boolean;};size:{reflect:boolean;};value:{reflect:boolean;noAccessor:boolean;};};
/**
* Control size, on the library's shared ladder. Accepts both spellings of every tier —
* `2xs`/`xs`/`s`/`m`/`l`/`xl` and Web Awesome's `small`/`medium`/`large` — so migrating either way
* is a tag rename. Scales the track and thumb off the same `--lr-form-control-*` values
* `<lr-input>`/`<lr-select>`/`<lr-button>` use, so controls of one `size` line up in a row. The
* slotted label keeps the library's standard control-label type size at every tier; restyle it
* through `::part(label)` if you want it to track the control.
*/
size:LyraSize;
/** Hint text below the switch. Unset: no hint chrome renders. */
hint:string;
/** Shoelace alias for {@link hint}. `hint` wins when both are supplied. */
helpText:string;
/** WA SSR slot-presence hint used before light-DOM assignment can be inspected. */
withHint:boolean;
/** Error text below the switch (overridden by slotted `error` content). Unset: no error chrome
*  renders. */
errorText:string;private hasLabelSlot;private hasHintSlot;private hasHelpTextSlot;private hasErrorSlot;private labelObserver?;private touched;
/** Whether the user has acted on this control yet, which is what gates the `user-valid`/
*  `user-invalid` custom states. Deliberately separate from `touched` (which drives the visible
*  `data-invalid`/`aria-invalid` pair and is set on blur alone): a toggle is an interaction the
*  instant it happens, and so is interactive validation — `reportValidity()` and a submission
*  attempt alike, via `installInteractionOnInvalid()` — exactly as it does for native
*  `:user-invalid`. A silent `checkValidity()` alone never counts. Not `@state`: nothing in
*  `render()` reads it. */
private hasInteracted;private internals;private validityController;
/** Consumer-supplied validation message reflected through `custom-error`. */
customError:string|null;private _defaultChecked;private _checkedDirty;private settingDefaultChecked;private reflectingDefaultChecked;private _fieldsetDisabled;private _name;private _checked;private _disabled;private _required;private _value;private toggleGuard;
/** Whether the control is disabled explicitly or by an ancestor fieldset. */
get effectiveDisabled():boolean;get checked():boolean;set checked(next:boolean);
/** Reflected current reset default; changing it never overwrites dirty live `checked` state. */
get defaultChecked():boolean;set defaultChecked(next:boolean);get disabled():boolean;set disabled(next:boolean);
/** The form submission key, reflected synchronously for native form APIs. */
get name():string;set name(next:string|null);get required():boolean;set required(next:boolean);get value():string;set value(next:string|null);constructor();get form():HTMLFormElement|null;set form(owner:FormOwnerValue);getForm():HTMLFormElement|null;get labels():NodeList;get validity():ValidityState;get validationMessage():string;get willValidate():boolean;
/** Reads both component state and the UA's synchronous fieldset cascade before public actions. */
private get liveDisabled();
/** Activates the internal switch control, toggling it the same as a real click -- mirrors
*  `<lr-checkbox>`'s identical `override click()`. Without this, `HTMLElement.prototype.click()`
*  on the host is a no-op: the real click handler is bound only to the internal
*  `[part~="base"]` control, not the host itself. */
click():void;
/** Moves focus to the internal switch control. */
focus(options?:FocusOptions):void;
/** Removes focus from the internal switch control. */
blur():void;private externalDescriptionLease?;private syncExternalDescription;protected updated(changed:PropertyValues):void;private releaseExternalDescription;connectedCallback():void;adoptedCallback():void;disconnectedCallback():void;protected willUpdate(changed:PropertyValues):void;
/** Shared with every other form control: disabled (own or fieldset-cascaded) bars validation. */
private get barredFromValidation();private updateValidity;
/** Republishes the six validity custom states (`required`/`optional`, `valid`/`invalid`,
*  `user-valid`/`user-invalid`) from whatever `ElementInternals` currently holds. Called from
*  every path that can move either validity or the interaction flag. */
private reflectValidityStates;private syncFormState;formResetCallback():void;formStateRestoreCallback(state:string|File|FormData|null,reason:'autocomplete'|'restore'):void;private restoreCheckedFromDefault;formDisabledCallback(disabled:boolean):void;private markInteracted;checkValidity():boolean;reportValidity():boolean;
/**
* Sets or clears a consumer-supplied validation error — the standard channel for a server-side
* rejection ("notifications are disabled for your plan") that no client-side constraint can
* express. A non-empty `message` raises `customError` and becomes `validationMessage`, so the
* control fails `checkValidity()`, blocks form submission, and matches `:state(invalid)`; `''`
* clears it.
*
* Clearing restores the control's own computed validity rather than forcing it valid: a
* required-and-unchecked switch whose custom error is cleared stays `valueMissing`. The custom
* error also survives every intrinsic recomputation in between (each toggle re-runs
* `updateValidity()`) and a form reset, exactly like a native control — only another
* `setCustomValidity('')` clears it.
*
* The message is caller-supplied content, so it is used verbatim and never localized here.
*/
setCustomValidity(message:string):void;
/** Clears consumer-supplied validity and restores the current required/checked constraint. */
resetValidity():void;private setFromUser;private onClick;private onBlur;private onFocus;private onKeyDown;private isDefaultLabelNode;private labelForwardingSlots;private observeLabelNode;private bindLabelObserverTargets;private recomputeHasLabelSlot;
/**
* Whether a direct light-DOM child carries `slot="name"` -- the same structural check
* {@link recomputeLightDomSlotState} always relied on for the connect/reconnect pass, and now
* also what the hint/help-text/error slotchange handlers use. `HTMLSlotElement.assignedElements()`
* is a live re-derivation of the browser's *current* slot-assignment computation, and WebKit has
* been observed reporting it transiently empty for an unrelated forwarding-slot chain nested
* inside the assigned element (a deeply forwarded node's own `characterData` mutating can fire a
* spurious `slotchange` on this outer named slot, with `assignedElements()` reporting zero for
* that one notification) -- even though the assigned child's own `slot` attribute never changed.
* Reading the light-DOM attribute directly is immune to that: it does not depend on the engine's
* live slot-assignment snapshot at all.
*/
private hasLightDomChildWithSlot;private recomputeLightDomSlotState;private handleLabelSlotChange;private onLabelSlotChange;private onSlotChange;private onHintSlotChange;private onHelpTextSlotChange;private onErrorSlotChange;render():TemplateResult;}declare global{interface HTMLElementTagNameMap{'lr-switch':LyraSwitch;}}