ngwr 14.9.1 → 14.11.0

package/types/ngwr-popover.d.ts

@@ -1,26 +1,20 @@
-import * as _angular_core from '@angular/core';
-import { Signal, TemplateRef } from '@angular/core';
-import { BooleanInput } from '@angular/cdk/coercion';
-
-/**
- * @license
- *
- * Use of this source code is governed by an MIT-style license that can be
- * found in the LICENSE file at https://github.com/thekhegay/ngwr/blob/main/LICENSE
- */
-
+import * as i0 from "@angular/core";
+import { Signal, TemplateRef } from "@angular/core";
+import { ConnectedPosition } from "@angular/cdk/overlay";
+import { BooleanInput } from "@angular/cdk/coercion";
+import { WrClassInput } from "ngwr/utils";
 /**
  * What a chart's hover tooltip says about one section.
  *
  * @internal
  */
 interface WrChartTooltipDatum {
-    /** The series or category name. Omitted where `value` is already a whole sentence. */
-    readonly label?: string;
-    /** The value, formatted the way the chart already prints it. */
-    readonly value: string;
-    /** The section's own paint, drawn as a swatch. Omitted where colour says nothing. */
-    readonly color?: string;
+  /** The series or category name. Omitted where `value` is already a whole sentence. */
+  readonly label?: string;
+  /** The value, formatted the way the chart already prints it. */
+  readonly value: string;
+  /** The section's own paint, drawn as a swatch. Omitted where colour says nothing. */
+  readonly color?: string;
 }
 /**
  * Where the tooltip for one section points, and what it says.
@@ -28,29 +22,29 @@ interface WrChartTooltipDatum {
  * @internal
  */
 interface WrChartTooltipTarget {
-    readonly datum: WrChartTooltipDatum;
-    /**
-     * What the chip points at: an element, or a box in viewport pixels for a section
-     * that is not one — a zero-size point on a donut's arc. The chip sits on `side` of
-     * it with its arrow on the middle of that edge, and flips for room. Point at the
-     * section itself, not at something near it: the arrow is what tells a reader which
-     * of forty squares the chip is about. `null` while the element is not rendered —
-     * the tooltip stays closed rather than pointing at nothing.
-     */
-    readonly anchor: Element | {
-        readonly x: number;
-        readonly y: number;
-        readonly width?: number;
-        readonly height?: number;
-    } | null;
-    /**
-     * Which PHYSICAL side of the anchor the chip goes, before a flip for room — the
-     * side the section faces. A chart's geometry does not mirror with `direction`, so
-     * neither does this: `right` is the right in RTL too. `top` and `bottom` flip to
-     * each other; `left` and `right` try above and below rather than the far side,
-     * which is the chart itself. @default 'top'
-     */
-    readonly side?: 'top' | 'bottom' | 'left' | 'right';
+  readonly datum: WrChartTooltipDatum;
+  /**
+   * What the chip points at: an element, or a box in viewport pixels for a section
+   * that is not one — a zero-size point on a donut's arc. The chip sits on `side` of
+   * it with its arrow on the middle of that edge, and flips for room. Point at the
+   * section itself, not at something near it: the arrow is what tells a reader which
+   * of forty squares the chip is about. `null` while the element is not rendered —
+   * the tooltip stays closed rather than pointing at nothing.
+   */
+  readonly anchor: Element | {
+    readonly x: number;
+    readonly y: number;
+    readonly width?: number;
+    readonly height?: number;
+  } | null;
+  /**
+   * Which PHYSICAL side of the anchor the chip goes, before a flip for room — the
+   * side the section faces. A chart's geometry does not mirror with `direction`, so
+   * neither does this: `right` is the right in RTL too. `top` and `bottom` flip to
+   * each other; `left` and `right` try above and below rather than the far side,
+   * which is the chart itself. @default 'top'
+   */
+  readonly side?: 'top' | 'bottom' | 'left' | 'right';
 }
 /**
  * The handle {@link useChartTooltip} returns to a chart.
@@ -58,38 +52,73 @@ interface WrChartTooltipTarget {
  * @internal
  */
 interface WrChartTooltip {
-    /** The section the tooltip is showing, or `null`. Always `null` while the chart opted out. */
-    readonly active: Signal<number | null>;
-    /**
-     * The pointer is over section `index`. Switches straight to it when another is up —
-     * unless the pointer is between that one's anchor and its chip, on its way onto the
-     * chip, where the switch waits out the same grace as `leave`.
-     */
-    enter(index: number): void;
-    /**
-     * The pointer left the sections. Hides after a short grace period, so a pointer
-     * can cross the gap onto the tooltip — WCAG 1.4.13 (Hoverable) — and so moving
-     * between two sections through a gap does not blink it.
-     */
-    leave(event?: MouseEvent): void;
+  /** The section the tooltip is showing, or `null`. Always `null` while the chart opted out. */
+  readonly active: Signal<number | null>;
+  /**
+   * The pointer is over section `index`. Switches straight to it when another is up —
+   * unless the pointer is between that one's anchor and its chip, on its way onto the
+   * chip, where the switch waits out the same grace as `leave`.
+   */
+  enter(index: number): void;
+  /**
+   * The pointer left the sections. Hides after a short grace period, so a pointer
+   * can cross the gap onto the tooltip — WCAG 1.4.13 (Hoverable) — and so moving
+   * between two sections through a gap does not blink it.
+   */
+  leave(event?: MouseEvent): void;
 }
-
+type WrPopoverPosition = 'top' | 'top-start' | 'top-end' | 'bottom' | 'bottom-start' | 'bottom-end' | 'left' | 'left-start' | 'left-end' | 'right' | 'right-start' | 'right-end';
 /**
- * @license
+ * The CDK geometry for each placement — one position, no fallbacks.
  *
- * Use of this source code is governed by an MIT-style license that can be
- * found in the LICENSE file at https://github.com/thekhegay/ngwr/blob/main/LICENSE
+ * The 8px offset is the gap between the trigger and the panel, and it is the
+ * reason a flip list matters rather than being a nicety: the flexible strategy
+ * emits `offsetX` as a `transform` on the pane, AFTER `withPush` has already
+ * decided the coordinate. Push therefore parks a right-anchored panel flush
+ * against the viewport edge and the offset then shoves it 8px back out, so a
+ * side placement that does not fit loses its border and corner off-screen no
+ * matter how hard push works. Flipping to a placement that fits is the only
+ * recovery, which is what `WR_POPOVER_FALLBACKS` is for.
+ *
+ * @internal
  */
-
-type WrPopoverPosition = 'top' | 'top-start' | 'top-end' | 'bottom' | 'bottom-start' | 'bottom-end' | 'left' | 'left-start' | 'left-end' | 'right' | 'right-start' | 'right-end';
-
+declare const WR_POPOVER_POSITIONS: Record<WrPopoverPosition, ConnectedPosition>;
+/**
+ * What each placement is allowed to flip to when it does not fit, best first.
+ * The requested placement always leads, so a panel that fits never moves.
+ *
+ * Alignment is preserved down the whole chain — a `-start` popover stays
+ * `-start` — because the alignment is the author's answer to "which end of the
+ * trigger does this belong to", and a flip is about the side, not about that.
+ *
+ * The two axes are deliberately NOT symmetric. A block-axis placement (`top*` /
+ * `bottom*`) flips only to its opposite, the classic behaviour, so a dropdown-ish
+ * panel can never surprise anyone by appearing beside its trigger. An inline-axis
+ * one (`left*` / `right*`) also gets the two block-axis sides, because on a phone
+ * NEITHER side fits: at 375px a 233px panel beside a mid-page trigger overflows
+ * by 109px to the right and 97px to the left, and only below/above has room.
+ *
+ * @internal
+ */
+declare const WR_POPOVER_FALLBACKS: Record<WrPopoverPosition, readonly WrPopoverPosition[]>;
 /**
- * @license
+ * The list `withPositions()` wants, with every link tagged so the pane names the
+ * placement it ACTUALLY took rather than the one that was asked for.
+ *
+ * The tag is what keeps the arrow honest. It is drawn by
+ * `.wr-popover-overlay--<placement> > *::after`, so a panel that flipped while
+ * the class stayed put would point at a side it no longer sits on. CDK applies a
+ * position's own `panelClass` in `_applyPosition` and clears it again on the next
+ * one, which is exactly the bookkeeping this needs — hence the class rather than
+ * a `positionChanges` subscription.
  *
- * Use of this source code is governed by an MIT-style license that can be
- * found in the LICENSE file at https://github.com/thekhegay/ngwr/blob/main/LICENSE
+ * @param paneClass The pane's base class: `wr-popover-overlay` or
+ *   `wr-tooltip-overlay`. The two modes key their arrows off different
+ *   selectors, so the prefix cannot live in the table.
+ *
+ * @internal
  */
-
+declare function wrPopoverPositions(position: WrPopoverPosition, paneClass: string): ConnectedPosition[];
 /**
  * A hover tooltip for a chart's sections, with ONE overlay per chart.
  *
@@ -160,146 +189,201 @@ type WrPopoverPosition = 'top' | 'top-start' | 'top-end' | 'bottom' | 'bottom-st
  *
  * @internal
  */
-declare function useChartTooltip(enabled: Signal<boolean>, resolve: (index: number) => WrChartTooltipTarget | null, sectionAt?: (x: number, y: number) => number | null): WrChartTooltip;
-
-declare class WrPopover {
-    /**
-     * Content to render inside the panel.
-     * - In **popover** mode (default): pass a `TemplateRef`.
-     * - In **tooltip** mode: pass a plain string.
-     */
-    readonly content: _angular_core.InputSignal<string | TemplateRef<unknown>>;
-    /**
-     * Shape preset.
-     *
-     * - `'popover'` (default) — template content, click trigger, dialog
-     *   semantics.
-     * - `'tooltip'` — text content, hover / keyboard-focus trigger,
-     *   `role="tooltip"`, `aria-describedby` on the host.
-     */
-    readonly mode: _angular_core.InputSignal<"popover" | "tooltip">;
-    /**
-     * How the popover opens. Ignored in tooltip mode — a tooltip is always hover
-     * plus keyboard focus. @default 'click'
-     */
-    readonly trigger: _angular_core.InputSignal<"click" | "hover">;
-    /** Anchor side. @default 'bottom' for popover, 'top' for tooltip */
-    readonly position: _angular_core.InputSignal<WrPopoverPosition | null>;
-    /** Tooltip only — delay before showing, in ms. @default 120 */
-    readonly showDelay: _angular_core.InputSignalWithTransform<number, unknown>;
-    /** Tooltip only — delay before hiding, in ms. @default 60 */
-    readonly hideDelay: _angular_core.InputSignalWithTransform<number, unknown>;
-    /**
-     * Popover mode only — present the panel as a full-width bottom-sheet on
-     * small viewports instead of an anchored panel. `undefined` follows the
-     * app-wide `provideWrResponsiveOverlays()` setting; `true`/`false`
-     * overrides it. Tooltips never become sheets. @default undefined
-     */
-    readonly responsive: _angular_core.InputSignalWithTransform<boolean | undefined, BooleanInput>;
-    /**
-     * Popover mode only — accessible name of the panel. `role="dialog"` with no
-     * name announces as a bare "dialog", so the catalog's `popover.label` is used
-     * when nothing is given. A popover has no universal name; whenever the panel
-     * has a heading or a purpose, pass it.
-     */
-    readonly ariaLabel: _angular_core.InputSignal<string | null>;
-    /** Fires after the panel opens. */
-    readonly opened: _angular_core.OutputEmitterRef<void>;
-    /** Fires after the panel closes. */
-    readonly closed: _angular_core.OutputEmitterRef<void>;
-    private readonly host;
-    private readonly focusMonitor;
-    private readonly keystroke;
-    private readonly overlay;
-    private readonly dir;
-    private readonly outsideClick;
-    private readonly responsiveConfig;
-    private readonly vcr;
-    private readonly scrollStrategies;
-    private readonly destroyRef;
-    private readonly injector;
-    /** @internal */
-    readonly isOpen: _angular_core.WritableSignal<boolean>;
-    /** @internal */
-    protected readonly isTooltip: _angular_core.Signal<boolean>;
-    /** Auto-generated id for `aria-controls` / `aria-describedby`. */
-    protected readonly panelId: string;
-    private readonly resolvedAriaLabel;
-    private readonly resolvedPosition;
-    private overlayRef;
-    private textPanelRef;
-    /** Whether the HOST itself holds focus — not a descendant of it. */
-    private hostFocused;
-    private hoverCloseTimer;
-    private showTimer;
-    private hideTimer;
-    constructor();
-    open(): void;
-    close(): void;
-    toggle(): void;
-    /** @internal */
-    protected onClick(event: MouseEvent): void;
-    /** @internal */
-    protected onMouseEnter(): void;
-    /** @internal */
-    protected onMouseLeave(event: MouseEvent): void;
-    /** @internal */
-    protected onEscape(): void;
-    /**
-     * Whether the keystroke in flight is one the user moves focus with.
-     *
-     * Asked only of a `keyboard` origin, which the CDK grants to any focus landing
-     * within a millisecond of a keydown — including the hand-back a drawer
-     * performs while Escape is still being handled. That is the reported bug's
-     * keyboard half, and the origin cannot see it.
-     *
-     * NO key on record answers `true`, and that polarity is chosen rather than
-     * inherited: a keyboard modality with no keystroke behind it is a screen
-     * reader's virtual cursor (the CDK reads its synthetic mousedown as
-     * `keyboard`) or a deliberate `focusVia(el, 'keyboard')`, and both are the
-     * user. Refusing wants positive evidence of a key that does something other
-     * than navigate — silence must not cost an AT user the hint. The two windows
-     * are aligned so that "keyboard origin, no key" cannot mean "the key just
-     * expired"; what it does still admit is a `FocusMonitorDetectionMode.EVENTUAL`
-     * app, where the CDK never expires an origin at all.
-     */
-    private fromNavigationKey;
-    private scheduleShow;
-    private scheduleHide;
-    private clearTimers;
-    private openOverlay;
-    /**
-     * Tear the overlay down, and tell the host — unless the host is going away
-     * with it.
-     *
-     * `notify: false` is the DESTROY path, and it is not a nicety. An `output()`
-     * belongs to the view that declares it, so emitting from `onDestroy` is
-     * refused: Angular logs `NG0953: Unexpected emit for destroyed OutputRef` and
-     * the listener never runs. Measured — a `(closed)` handler on a dropdown whose
-     * host view is removed while the menu is open fired zero times and left a
-     * console error behind. There is nobody to notify at that point, because the
-     * consumer's own view is being torn down in the same pass; `wr-popconfirm`
-     * already disposes without emitting, and this brings the other two into line.
-     *
-     * The focus hand-back is skipped for the same reason — the host element is on
-     * its way out of the document.
-     */
-    private closeOverlay;
-    private readonly onOverlayLeave;
-    private readonly onOverlayEnter;
-    private scheduleHoverClose;
-    private clearHoverClose;
-    /**
-     * Whether the app reads right-to-left.
-     *
-     * Optional inject: `Directionality` is root-provided, so this is never null in
-     * an app — but a bare `TestBed` that provides nothing should still get a
-     * component that works, and defaulting to LTR is the honest fallback.
-     */
-    private isRtl;
-    static ɵfac: _angular_core.ɵɵFactoryDeclaration<WrPopover, never>;
-    static ɵdir: _angular_core.ɵɵDirectiveDeclaration<WrPopover, "[wrPopover]", ["wrPopover"], { "content": { "alias": "wrPopover"; "required": true; "isSignal": true; }; "mode": { "alias": "mode"; "required": false; "isSignal": true; }; "trigger": { "alias": "trigger"; "required": false; "isSignal": true; }; "position": { "alias": "position"; "required": false; "isSignal": true; }; "showDelay": { "alias": "showDelay"; "required": false; "isSignal": true; }; "hideDelay": { "alias": "hideDelay"; "required": false; "isSignal": true; }; "responsive": { "alias": "responsive"; "required": false; "isSignal": true; }; "ariaLabel": { "alias": "ariaLabel"; "required": false; "isSignal": true; }; }, { "opened": "opened"; "closed": "closed"; }, never, never, true, never>;
+export declare function useChartTooltip(enabled: Signal<boolean>, resolve: (index: number) => WrChartTooltipTarget | null, sectionAt?: (x: number, y: number) => number | null): WrChartTooltip;
+export declare class WrPopover {
+  /**
+   * Content to render inside the panel.
+   * - In **popover** mode (default): pass a `TemplateRef`.
+   * - In **tooltip** mode: pass a plain string.
+   */
+  readonly content: import("@angular/core").InputSignal<string | TemplateRef<unknown>>;
+  /**
+   * Shape preset.
+   *
+   * - `'popover'` (default) — template content, click trigger, dialog
+   *   semantics.
+   * - `'tooltip'` — text content, hover / keyboard-focus trigger,
+   *   `role="tooltip"`, `aria-describedby` on the host.
+   */
+  readonly mode: import("@angular/core").InputSignal<"popover" | "tooltip">;
+  /**
+   * How the popover opens. Ignored in tooltip mode — a tooltip is always hover
+   * plus keyboard focus. @default 'click'
+   */
+  readonly trigger: import("@angular/core").InputSignal<"click" | "hover">;
+  /** Anchor side. @default 'bottom' for popover, 'top' for tooltip */
+  readonly position: import("@angular/core").InputSignal<WrPopoverPosition | null>;
+  /** Tooltip only — delay before showing, in ms. @default 120 */
+  readonly showDelay: import("@angular/core").InputSignalWithTransform<number, unknown>;
+  /** Tooltip only — delay before hiding, in ms. @default 60 */
+  readonly hideDelay: import("@angular/core").InputSignalWithTransform<number, unknown>;
+  /**
+   * Popover mode only — present the panel as a full-width bottom-sheet on
+   * small viewports instead of an anchored panel. `undefined` follows the
+   * app-wide `provideWrResponsiveOverlays()` setting; `true`/`false`
+   * overrides it. Tooltips never become sheets. @default undefined
+   */
+  readonly responsive: import("@angular/core").InputSignalWithTransform<boolean | undefined, BooleanInput>;
+  /**
+   * Popover mode only — accessible name of the panel. `role="dialog"` with no
+   * name announces as a bare "dialog", so the catalog's `popover.label` is used
+   * when nothing is given. A popover has no universal name; whenever the panel
+   * has a heading or a purpose, pass it.
+   */
+  readonly ariaLabel: import("@angular/core").InputSignal<string | null>;
+  /**
+   * Extra CSS classes for the popover's (or tooltip's) overlay pane.
+   *
+   * The pane is appended to the overlay container, not to this component, so
+   * nothing in the consumer's own template encloses it and no descendant rule
+   * written around the trigger can reach it. This input is the only per-instance
+   * handle on it. A space-separated string works as well as an array.
+   */
+  readonly panelClass: import("@angular/core").InputSignal<WrClassInput>;
+  /** Fires after the panel opens. */
+  readonly opened: import("@angular/core").OutputEmitterRef<void>;
+  /** Fires after the panel closes. */
+  readonly closed: import("@angular/core").OutputEmitterRef<void>;
+  private readonly host;
+  private readonly focusMonitor;
+  private readonly keystroke;
+  private readonly overlay;
+  private readonly dir;
+  private readonly outsideClick;
+  private readonly responsiveConfig;
+  private readonly vcr;
+  private readonly scrollStrategies;
+  private readonly destroyRef;
+  private readonly injector;
+  /** @internal */
+  readonly isOpen: import("@angular/core").WritableSignal<boolean>;
+  /** @internal */
+  protected readonly isTooltip: import("@angular/core").Signal<boolean>;
+  /** Auto-generated id for `aria-controls` / `aria-describedby`. */
+  protected readonly panelId: string;
+  private readonly resolvedAriaLabel;
+  private readonly resolvedPosition;
+  private overlayRef;
+  private textPanelRef;
+  /** Whether the HOST itself holds focus — not a descendant of it. */
+  private hostFocused;
+  private hoverCloseTimer;
+  private showTimer;
+  private hideTimer;
+  constructor();
+  open(): void;
+  close(): void;
+  toggle(): void;
+  /** @internal */
+  protected onClick(event: MouseEvent): void;
+  /** @internal */
+  protected onMouseEnter(): void;
+  /** @internal */
+  protected onMouseLeave(event: MouseEvent): void;
+  /** @internal */
+  protected onEscape(): void;
+  /**
+   * Whether the keystroke in flight is one the user moves focus with.
+   *
+   * Asked only of a `keyboard` origin, which the CDK grants to any focus landing
+   * within a millisecond of a keydown — including the hand-back a drawer
+   * performs while Escape is still being handled. That is the reported bug's
+   * keyboard half, and the origin cannot see it.
+   *
+   * NO key on record answers `true`, and that polarity is chosen rather than
+   * inherited: a keyboard modality with no keystroke behind it is a screen
+   * reader's virtual cursor (the CDK reads its synthetic mousedown as
+   * `keyboard`) or a deliberate `focusVia(el, 'keyboard')`, and both are the
+   * user. Refusing wants positive evidence of a key that does something other
+   * than navigate — silence must not cost an AT user the hint. The two windows
+   * are aligned so that "keyboard origin, no key" cannot mean "the key just
+   * expired"; what it does still admit is a `FocusMonitorDetectionMode.EVENTUAL`
+   * app, where the CDK never expires an origin at all.
+   */
+  private fromNavigationKey;
+  private scheduleShow;
+  private scheduleHide;
+  private clearTimers;
+  private openOverlay;
+  /**
+   * Tear the overlay down, and tell the host — unless the host is going away
+   * with it.
+   *
+   * `notify: false` is the DESTROY path, and it is not a nicety. An `output()`
+   * belongs to the view that declares it, so emitting from `onDestroy` is
+   * refused: Angular logs `NG0953: Unexpected emit for destroyed OutputRef` and
+   * the listener never runs. Measured — a `(closed)` handler on a dropdown whose
+   * host view is removed while the menu is open fired zero times and left a
+   * console error behind. There is nobody to notify at that point, because the
+   * consumer's own view is being torn down in the same pass; `wr-popconfirm`
+   * already disposes without emitting, and this brings the other two into line.
+   *
+   * The focus hand-back is skipped for the same reason — the host element is on
+   * its way out of the document.
+   */
+  private closeOverlay;
+  private readonly onOverlayLeave;
+  private readonly onOverlayEnter;
+  private scheduleHoverClose;
+  private clearHoverClose;
+  /**
+   * Whether the app reads right-to-left.
+   *
+   * Optional inject: `Directionality` is root-provided, so this is never null in
+   * an app — but a bare `TestBed` that provides nothing should still get a
+   * component that works, and defaulting to LTR is the honest fallback.
+   */
+  private isRtl;
+  static ɵfac: i0.ɵɵFactoryDeclaration<WrPopover, never>;
+  static ɵdir: i0.ɵɵDirectiveDeclaration<WrPopover, "[wrPopover]", ["wrPopover"], {
+    "content": {
+      "alias": "wrPopover";
+      "required": true;
+      "isSignal": true;
+    };
+    "mode": {
+      "alias": "mode";
+      "required": false;
+      "isSignal": true;
+    };
+    "trigger": {
+      "alias": "trigger";
+      "required": false;
+      "isSignal": true;
+    };
+    "position": {
+      "alias": "position";
+      "required": false;
+      "isSignal": true;
+    };
+    "showDelay": {
+      "alias": "showDelay";
+      "required": false;
+      "isSignal": true;
+    };
+    "hideDelay": {
+      "alias": "hideDelay";
+      "required": false;
+      "isSignal": true;
+    };
+    "responsive": {
+      "alias": "responsive";
+      "required": false;
+      "isSignal": true;
+    };
+    "ariaLabel": {
+      "alias": "ariaLabel";
+      "required": false;
+      "isSignal": true;
+    };
+    "panelClass": {
+      "alias": "panelClass";
+      "required": false;
+      "isSignal": true;
+    };
+  }, {
+    "opened": "opened";
+    "closed": "closed";
+  }, never, never, true, never>;
 }
-
-export { WrPopover, useChartTooltip };
-export type { WrChartTooltip, WrChartTooltipDatum, WrChartTooltipTarget, WrPopoverPosition };
+export type { WrChartTooltip, WrChartTooltipDatum, WrChartTooltipTarget, WrPopoverPosition };

package/types/ngwr-progress.d.ts

@@ -1,5 +1,4 @@
-import * as _angular_core from '@angular/core';
-
+import * as i0 from "@angular/core";
 /**
  * Horizontal progress bar.
  *
@@ -11,26 +10,40 @@ import * as _angular_core from '@angular/core';
  *
  * @see https://ngwr.dev/reference/components/progress
  */
-declare class WrProgress {
-    /** Accessible name — `role="progressbar"` needs one. Falls back to `progress.label`. */
-    readonly ariaLabel: _angular_core.InputSignal<string | null>;
-    protected readonly resolvedAriaLabel: _angular_core.Signal<string>;
-    /**
-     * Bar color.
-     *
-     * @default 'primary'
-     */
-    readonly color: _angular_core.InputSignal<"primary" | "secondary" | "success" | "warning" | "danger" | "info" | "light" | "medium" | "dark">;
-    /**
-     * Progress value, clamped to `[0, 100]`.
-     *
-     * @default 0
-     */
-    readonly value: _angular_core.InputSignalWithTransform<number, unknown>;
-    protected readonly clamped: _angular_core.Signal<number>;
-    protected readonly classes: _angular_core.Signal<string>;
-    static ɵfac: _angular_core.ɵɵFactoryDeclaration<WrProgress, never>;
-    static ɵcmp: _angular_core.ɵɵComponentDeclaration<WrProgress, "wr-progress", never, { "ariaLabel": { "alias": "ariaLabel"; "required": false; "isSignal": true; }; "color": { "alias": "color"; "required": false; "isSignal": true; }; "value": { "alias": "value"; "required": false; "isSignal": true; }; }, {}, never, never, true, never>;
-}
-
-export { WrProgress };
+export declare class WrProgress {
+  /** Accessible name — `role="progressbar"` needs one. Falls back to `progress.label`. */
+  readonly ariaLabel: import("@angular/core").InputSignal<string | null>;
+  protected readonly resolvedAriaLabel: import("@angular/core").Signal<string>;
+  /**
+   * Bar color.
+   *
+   * @default 'primary'
+   */
+  readonly color: import("@angular/core").InputSignal<"primary" | "secondary" | "success" | "warning" | "danger" | "info" | "light" | "medium" | "dark">;
+  /**
+   * Progress value, clamped to `[0, 100]`.
+   *
+   * @default 0
+   */
+  readonly value: import("@angular/core").InputSignalWithTransform<number, unknown>;
+  protected readonly clamped: import("@angular/core").Signal<number>;
+  protected readonly classes: import("@angular/core").Signal<string>;
+  static ɵfac: i0.ɵɵFactoryDeclaration<WrProgress, never>;
+  static ɵcmp: i0.ɵɵComponentDeclaration<WrProgress, "wr-progress", never, {
+    "ariaLabel": {
+      "alias": "ariaLabel";
+      "required": false;
+      "isSignal": true;
+    };
+    "color": {
+      "alias": "color";
+      "required": false;
+      "isSignal": true;
+    };
+    "value": {
+      "alias": "value";
+      "required": false;
+      "isSignal": true;
+    };
+  }, {}, never, never, true, never>;
+}