material 3.0.2 → 3.0.3

package/README.md

@@ -97,7 +97,7 @@ What a bundler keeps, minified and gzipped (kB is 1,000 bytes), measured from th
 | Everything the root exports (`export * from 'material'`), without code splitting | 127.0 kB |
 | `material/styles/base` | 2.9 kB |
 | `material/styles/base` and `material/styles/button` | 5.2 kB |
-| `material/styles`, the full stylesheet | 62.6 kB |
+| `material/styles`, the full stylesheet | 62.8 kB |
 <!-- /sizes -->
 
 `material` publishes ESM only, so bundlers drop what you do not import. Each component's page on [md3.io/components](https://md3.io/components/) gives its size.

package/dist/components/badge/config.d.ts

@@ -615,7 +615,7 @@ export declare const getApiConfig: (comp: {
  * A badge is a count, and a count of nothing is not news -- so an empty label
  * and a zero are both hidden. The setter has always done this; creation did
  * not, so `createBadge({ label: 0 })` was visible while `setLabel(0)` on the
- * same badge hid it. One rule now, used by both. FLO-108.
+ * same badge hid it. One rule now, used by both.
  */
 export declare const isEmptyBadgeLabel: (formattedLabel: string) => boolean;
 /**
@@ -624,7 +624,7 @@ export declare const isEmptyBadgeLabel: (formattedLabel: string) => boolean;
  * Asked of the same value the formatter reads, rather than of its type. Both
  * callers used to require `typeof label === "number"`, so `"1250"` with a max
  * of 999 rendered "999+" without the overflow class that 1250 received --
- * the formatter has always used `Number(label)`. FLO-108.
+ * the formatter has always used `Number(label)`.
  */
 export declare const isBadgeOverflow: (label: string | number, max?: number) => boolean;
 export declare const formatBadgeLabel: (label: string | number, max?: number) => string;

package/dist/components/button/features/toggle.d.ts

@@ -31,7 +31,7 @@ export interface ToggleComponent {
  * `--selected` classes drive the selected colours and the shape swap.
  *
  * Emits a `change` event with `{ selected, value }` when the user toggles it;
- * `value` is the button's value, as `getValue()` returns it (FLO-380).
+ * `value` is the button's value, as `getValue()` returns it.
  * With `toggleOnClick: false` the click does nothing and a container
  * (button group) drives the state through `setSelected`.
  *

package/dist/components/button/types.d.ts

@@ -187,7 +187,7 @@ export interface ButtonEventPayload<E extends Event = Event> {
     /** The same DOM event as `event`; both names have always been provided. */
     originalEvent: E;
 }
-/** A toggle button's `change` (FLO-380). */
+/** A toggle button's `change`. */
 export interface ButtonChangePayload {
     /** Whether the button is now selected */
     selected: boolean;
@@ -199,7 +199,7 @@ export interface ButtonChangePayload {
  *
  * `on` and `off` are generic over these keys, so a misspelled event name is a
  * compile error rather than a listener that never fires, and a handler's
- * payload is typed rather than `any`. FLO-114.
+ * payload is typed rather than `any`.
  *
  * Native forwarding and toggle selection are reported here. `mount` and `unmount` are *not* here: the lifecycle
  * feature keeps its own emitter and exposes them as `lifecycle.onMount` and
@@ -208,7 +208,7 @@ export interface ButtonChangePayload {
 export interface ButtonEvents {
     /**
      * A toggle button's selected state changed on a click. `value` is the
-     * button's value (`getValue()`), as every model event carries (FLO-380);
+     * button's value (`getValue()`), as every model event carries;
      * `selected` is the toggled state.
      */
     change: (payload: ButtonChangePayload) => void;
@@ -300,7 +300,7 @@ export interface ButtonComponent {
      * @returns The button component for chaining
      */
     disable: () => ButtonComponent;
-    /** Whether the button is disabled (FLO-384) */
+    /** Whether the button is disabled */
     isDisabled: () => boolean;
     /**
      * Sets the button's text content
@@ -445,7 +445,7 @@ export interface ButtonComponent {
 /**
  * Registers ButtonConfig with the global defaults map, so
  * `setComponentDefaults("button", ...)` is typed without core
- * importing anything from this component. FLO-115.
+ * importing anything from this component.
  */
 declare module "../../core/config/global" {
     interface ComponentConfigMap {

package/dist/components/button-group/button-group.d.ts

@@ -5,7 +5,7 @@ import { ButtonGroupConfig, ButtonGroupComponent } from "./types.js";
  * The Button Group component provides a container for grouping related action buttons.
  * A standard group holds related actions, each button acting on its own; a
  * connected group (`kind: "connected"`, with `selection`) is M3's replacement for
- * the segmented button, which material 3.0.0 removed (FLO-382).
+ * the segmented button, which material 3.0.0 removed.
  *
  * Per Material Design 3 specifications:
  * - Standard groups space their buttons (18/12/8/8/8dp by size) and a

package/dist/components/button-group/constants.d.ts

@@ -73,7 +73,7 @@ export declare const BUTTON_GROUP_SIZES: {
 /**
  * Material 3 button group tokens per size (dp): container height, button
  * icon size, standard between-space, connected inner corner and its shape
- * scale step (FLO-331) (m3.material.io button group specs; ButtonGroupSmallTokens.kt and
+ * scale step (m3.material.io button group specs; ButtonGroupSmallTokens.kt and
  * ConnectedButtonGroupSmallTokens.kt for the s size)
  */
 export declare const BUTTON_GROUP_SIZE_TOKENS: {

package/dist/components/button-group/index.d.ts

@@ -4,7 +4,7 @@
  * The Button Group component provides a container for grouping related action buttons.
  * A standard group holds related actions, each button acting on its own; a
  * connected group (`kind: "connected"`, with `selection`) is M3's replacement for
- * the segmented button, which material 3.0.0 removed (FLO-382).
+ * the segmented button, which material 3.0.0 removed.
  *
  * @packageDocumentation
  */

package/dist/components/button-group/types.d.ts

@@ -123,7 +123,7 @@ interface ButtonGroupItemBase extends Omit<ButtonConfig, "variant"> {
  *
  * Expressed as a union rather than a flat required field, because requiring
  * it on text items too is over-broad -- it would make 67 call sites in this
- * component's own tests pass a label that duplicates the text. FLO-110.
+ * component's own tests pass a label that duplicates the text.
  */
 export type ButtonGroupItemConfig = (ButtonGroupItemBase & {
     text: string;
@@ -287,7 +287,7 @@ export interface ButtonGroupComponent {
      * @returns The ButtonGroupComponent for chaining
      */
     disable: () => ButtonGroupComponent;
-    /** Whether the whole group is disabled (FLO-384) */
+    /** Whether the whole group is disabled */
     isDisabled: () => boolean;
     /**
      * Enables a specific button by index

package/dist/components/card/types.d.ts

@@ -63,14 +63,14 @@ export interface CardConfig {
     /**
      * The hover and press states and their elevation, for a card the app
      * makes interactive itself. Not a control: no role of button and no tab
-     * stop; `clickable` is (FLO-109).
+     * stop; `clickable` is.
      */
     interactive?: boolean;
     /** Whether the card should take full width */
     fullWidth?: boolean;
     /**
      * A card that acts on activation: a button (role, tab stop, Enter and
-     * Space click it) with the ripple (FLO-109)
+     * Space click it) with the ripple
      */
     clickable?: boolean;
     /** Whether the card is draggable */
@@ -290,7 +290,7 @@ export interface CardComponentConfig extends CardConfig {
     prefix: string;
 }
 /**
- * The card's events (FLO-323). A clickable card forwards `click`; an
+ * The card's events. A clickable card forwards `click`; an
  * interactive one `mouseenter`, `mouseleave`, `keydown`, `focus` and `blur`;
  * a draggable one emits `dragstart` and `dragend`.
  */
@@ -321,7 +321,7 @@ export interface CardEvents extends TouchEvents {
  * @category Components
  */
 export interface CardComponent extends BaseComponent {
-    /** Subscribes to one of the card's events (FLO-323) */
+    /** Subscribes to one of the card's events */
     on: <K extends keyof CardEvents>(event: K, handler: CardEvents[K]) => CardComponent;
     /** Removes a handler added with `on` */
     off: <K extends keyof CardEvents>(event: K, handler: CardEvents[K]) => CardComponent;
@@ -506,7 +506,7 @@ export interface ApiOptions {
 /**
  * Registers CardConfig with the global defaults map, so
  * `setComponentDefaults("card", ...)` is typed without core
- * importing anything from this component. FLO-115.
+ * importing anything from this component.
  */
 declare module "../../core/config/global" {
     interface ComponentConfigMap {

package/dist/components/carousel/types.d.ts

@@ -1,7 +1,7 @@
 import type { ForwardedEventPayload } from "../../core/dom/index.js";
 /** Current item reported by programmatic navigation or native scrolling. */
 export interface CarouselChangePayload {
-    /** The current item's index, as `getValue()` returns it; every model event carries it (FLO-380) */
+    /** The current item's index, as `getValue()` returns it; every model event carries it */
     value: number;
 }
 /** Events emitted by the scroll feature and forwarded from the root. */

package/dist/components/checkbox/types.d.ts

@@ -62,7 +62,7 @@ export interface CheckboxConfig {
     labelPosition?: CheckboxLabelPosition | string;
     /**
      * Error state: the outline, the selected container and the state layers
-     * take the error role, and the input is marked `aria-invalid`. FLO-265.
+     * take the error role, and the input is marked `aria-invalid`.
      * @default false
      */
     error?: boolean;
@@ -71,7 +71,7 @@ export interface CheckboxConfig {
      */
     ariaLabel?: string;
     /**
-     * Whether Enter toggles as Space does. Off for a checkbox (FLO-265).
+     * Whether Enter toggles as Space does. Off for a checkbox.
      * @internal
      */
     enterToggles?: boolean;
@@ -221,7 +221,7 @@ export interface CheckboxComponent {
      * @returns Checkbox component for method chaining
      */
     disable: () => CheckboxComponent;
-    /** Whether the checkbox is disabled (FLO-384) */
+    /** Whether the checkbox is disabled */
     isDisabled: () => boolean;
     /**
      * Destroys the checkbox component and cleans up resources
@@ -297,7 +297,7 @@ export type ApiComponent = BaseComponent & Required<Pick<BaseComponent, "checkab
 /**
  * Registers CheckboxConfig with the global defaults map, so
  * `setComponentDefaults("checkbox", ...)` is typed without core
- * importing anything from this component. FLO-115.
+ * importing anything from this component.
  */
 declare module "../../core/config/global" {
     interface ComponentConfigMap {

package/dist/components/chips/types.d.ts

@@ -24,7 +24,7 @@ export interface ChipConfig {
      * Delete. Input chips are always removable (m3.material.io chips): on its own the
      * chip then leaves the page; in a set, the set removes it and emits `remove`. It
      * used to be a request the owner had to act on, and without it there was no
-     * remove button. FLO-257. It and every `remove` listener run first, with the chip
+     * remove button. It and every `remove` listener run first, with the chip
      * still in the set and on the page; the removal follows.
      */
     onRemove?: ChipEvents["remove"];
@@ -32,7 +32,7 @@ export interface ChipConfig {
     /**
      * Filter chips: gives the trailing icon its own button, which calls this (the
      * m3.material.io chips' trailing icon that "can be used to open a menu or remove
-     * the chip"). The chip's own action is unaffected. FLO-259.
+     * the chip"). The chip's own action is unaffected.
      */
     onTrailingClick?: ChipEvents["trailing"];
     /** The trailing button's accessible name; "{label} options" for a menu, "Remove {label}" otherwise. */
@@ -70,7 +70,7 @@ export interface ChipConfig {
 }
 /**
  * @internal What the chip set passes a chip on top of its config; not part of
- * ChipConfig, so apps cannot set it (FLO-381).
+ * ChipConfig, so apps cannot set it.
  */
 export interface ChipOptions extends ChipConfig {
     /** Selection belongs to the chips container. */
@@ -80,7 +80,7 @@ export interface ChipOptions extends ChipConfig {
     /** The owning set removes the chip, once its `remove` listeners have run. */
     onRemoved?: (chip: ChipComponent) => void;
     /**
-     * The chip is a cell of a chip set's grid (FLO-261): the root is a
+     * The chip is a cell of a chip set's grid: the root is a
      * `gridcell`, and a one-action chip's cell is its focus target.
      */
     cell?: boolean;
@@ -95,7 +95,7 @@ export type InputChipConfig = Omit<FilterChipConfig, "elevated" | "onTrailingCli
 export interface ChipChangePayload {
     selected: boolean;
     chip: ChipComponent;
-    /** The chip's value, as `getValue()` returns it; every model event carries it (FLO-380) */
+    /** The chip's value, as `getValue()` returns it; every model event carries it */
     value: string | null;
 }
 export interface ChipEvents {
@@ -105,7 +105,7 @@ export interface ChipEvents {
     blur: (payload: ForwardedEventPayload<FocusEvent, HTMLElement>) => void;
     change: (payload: ChipChangePayload) => void;
     remove: (chip: ChipComponent) => void;
-    /** A filter chip's trailing button was activated (FLO-259). */
+    /** A filter chip's trailing button was activated. */
     trailing: (chip: ChipComponent) => void;
 }
 /** Shared API. Selection setters are inert on assist and suggestion chips. */
@@ -115,7 +115,7 @@ export interface ChipComponent {
     action: HTMLButtonElement;
     /**
      * A filter chip's trailing button, when it has one (`onTrailingClick`): anchor a
-     * menu to it and keep its aria-expanded in step. FLO-259.
+     * menu to it and keep its aria-expanded in step.
      */
     trailingAction?: HTMLButtonElement;
     getType: () => ChipType;
@@ -173,7 +173,7 @@ export interface ChipsConfig {
     selector?: string | null;
     /**
      * Whether several chips can be selected at once. Multi-select is the default, as
-     * Material's chip groups are (single-select is opt-in). FLO-257.
+     * Material's chip groups are (single-select is opt-in).
      * @default true
      */
     multiSelect?: boolean;
@@ -181,7 +181,7 @@ export interface ChipsConfig {
      * Whether the set keeps at least one chip selected: deselecting the last selected
      * chip is refused, and a refused click emits no `change`, on the chip or on the set.
      * Off by default, as in Material; single-select sets used to
-     * enforce it without a way to opt out. FLO-257.
+     * enforce it without a way to opt out.
      * @default false
      */
     selectionRequired?: boolean;
@@ -344,7 +344,7 @@ export interface ChipsComponent {
     /**
      * Selects chips by their values
      * @param values - Value or array of values to select
-     * @param triggerEvent - Emits `change` when true; silent by default (FLO-328)
+     * @param triggerEvent - Emits `change` when true; silent by default
      * @returns The chips instance for chaining
      */
     selectByValue: (values: string | string[], triggerEvent?: boolean) => ChipsComponent;
@@ -401,7 +401,7 @@ export interface ChipsComponent {
     enableKeyboardNavigation: () => ChipsComponent;
     /**
      * Turns keyboard navigation between the chips on and off: while disabled,
-     * the arrows, Home and End no longer move focus in the set (FLO-352)
+     * the arrows, Home and End no longer move focus in the set
      */
     keyboard: {
         /** Moves focus with the arrows, Home and End again */
@@ -431,7 +431,7 @@ export interface ChipsComponent {
 /**
  * Registers ChipConfig with the global defaults map, so
  * `setComponentDefaults("chip", ...)` is typed without core
- * importing anything from this component. FLO-115.
+ * importing anything from this component.
  */
 declare module "../../core/config/global" {
     interface ComponentConfigMap {

package/dist/components/datepicker/datepicker.d.ts

@@ -1,7 +1,7 @@
 import type { DatePickerComponent, DatePickerConfig, DatePickerValueOf } from "./types.js";
 /** M3 calendar/input modes share a draft; modal acceptance is the commit boundary. */
 /**
- * The value's type follows a literal selectionMode (FLO-295): `'range'` makes
+ * The value's type follows a literal selectionMode: `'range'` makes
  * it a pair, the default a date.
  */
 declare const createDatePicker: <M extends string = "single">(config?: DatePickerConfig & {

package/dist/components/datepicker/types.d.ts

@@ -3,17 +3,17 @@ import type { NormalizedEvent } from "../../core/utils/mobile.js";
 /** Value returned by the API, including complete ranges and empty selections. */
 export type DatePickerValue = Date | [Date, Date] | null;
 /**
- * The value as the selection mode shapes it (FLO-295): a range is a pair, a
+ * The value as the selection mode shapes it: a range is a pair, a
  * single date a date; an unknown mode, either.
  */
 export type DatePickerValueOf<M> = M extends "range" ? [Date, Date] | null : M extends "single" ? Date | null : DatePickerValue;
-/** What setValue and `value` take: a date, a range as a pair, or as { start, end } (FLO-289). */
+/** What setValue and `value` take: a date, a range as a pair, or as { start, end }. */
 export type DatePickerInput = Date | string | [Date | string, Date | string] | {
     start: Date | string;
     end: Date | string;
 };
 /**
- * One shape whatever committed the value (FLO-295): a range's `value` is the
+ * One shape whatever committed the value: a range's `value` is the
  * pair, and `rangeEndDate` its end, kept for compatibility (null otherwise).
  * The docked calendar sent the start as the value and the end apart.
  */
@@ -23,7 +23,7 @@ export interface DatePickerChangePayload<V = DatePickerValue> {
     formattedValue: string;
     /**
      * The value as ISO 8601 text, the `value` of the `<m-datepicker>` element's
-     * `change`: a date (`2026-09-10`), a `start/end` interval, or "" (FLO-320)
+     * `change`: a date (`2026-09-10`), a `start/end` interval, or ""
      */
     iso: string;
 }
@@ -141,11 +141,11 @@ export interface DatePickerConfig {
      * Accepts a Date object, Date string, or two dates for range selection
      */
     value?: DatePickerInput;
-    /** The value shows and cannot change: no typing, no calendar (FLO-289). */
+    /** The value shows and cannot change: no typing, no calendar. */
     readOnly?: boolean;
-    /** A date is required: on the input for forms, and checkValidity() (FLO-289). */
+    /** A date is required: on the input for forms, and checkValidity(). */
     required?: boolean;
-    /** The supporting text under the field. Default: the date format (FLO-289). */
+    /** The supporting text under the field. Default: the date format. */
     supportingText?: string;
     /**
      * Minimum selectable date
@@ -310,11 +310,11 @@ export interface DatePickerComponent<V = DatePickerValue> {
      * @returns The datepicker component for chaining
      */
     setValue: (value: DatePickerInput) => DatePickerComponent<V>;
-    /** Read-only: the value shows and cannot change (FLO-289) */
+    /** Read-only: the value shows and cannot change */
     setReadOnly: (readOnly: boolean) => DatePickerComponent<V>;
     /** Whether the picker is read-only */
     isReadOnly: () => boolean;
-    /** Whether a date is required (FLO-289) */
+    /** Whether a date is required */
     setRequired: (required: boolean) => DatePickerComponent<V>;
     /**
      * False when a date is required and missing. A dialog variant's input is
@@ -323,7 +323,7 @@ export interface DatePickerComponent<V = DatePickerValue> {
     checkValidity: () => boolean;
     /** As checkValidity(), and shows the error on the field when false */
     reportValidity: () => boolean;
-    /** The supporting text; empty or null shows the date format (FLO-289) */
+    /** The supporting text; empty or null shows the date format */
     setSupportingText: (text: string | null) => DatePickerComponent<V>;
     /**
      * Gets the formatted date string based on the selected date(s)
@@ -395,7 +395,7 @@ export interface DatePickerState {
     label: string;
     specialDates: NonNullable<DatePickerConfig["specialDates"]>;
     isAllowed(date: Date): boolean;
-    /** Full screen: the first month of the rendered list, and how many follow. FLO-276. */
+    /** Full screen: the first month of the rendered list, and how many follow. */
     listStart?: Date;
     listLength?: number;
 }

package/dist/components/datepicker/utils.d.ts

@@ -79,6 +79,6 @@ export declare const addMonths: (date: Date, months: number) => Date;
 export declare const addYears: (date: Date, years: number) => Date;
 /**
  * A value as ISO 8601 text, the `<m-datepicker>` element's value: a date
- * (`2026-09-10`), a `start/end` interval, or "" (FLO-320).
+ * (`2026-09-10`), a `start/end` interval, or "".
  */
 export declare const toIsoValue: (value: Date | [Date, Date] | null, end?: Date | null) => string;

package/dist/components/dialog/types.d.ts

@@ -618,7 +618,7 @@ export interface DialogConfirmOptions {
 /**
  * Registers DialogConfig with the global defaults map, so
  * `setComponentDefaults("dialog", ...)` is typed without core
- * importing anything from this component. FLO-115.
+ * importing anything from this component.
  */
 declare module "../../core/config/global" {
     interface ComponentConfigMap {

package/dist/components/drawer/types.d.ts

@@ -42,7 +42,7 @@ export interface DrawerItemConfig {
 export interface DrawerSelectEvent {
     /** The selected item's id */
     id: string;
-    /** The id again, as the `value` of the `<m-drawer>` element's `change` (FLO-320) */
+    /** The id again, as the `value` of the `<m-drawer>` element's `change` */
     value: string;
     /** The selected item's label */
     label: string;

package/dist/components/extended-fab/types.d.ts

@@ -389,9 +389,9 @@ export interface ExtendedFabEvents extends TouchEvents {
     focus: (payload: ForwardedEventPayload<FocusEvent, HTMLButtonElement>) => void;
     /** The button lost focus. */
     blur: (payload: ForwardedEventPayload<FocusEvent, HTMLButtonElement>) => void;
-    /** `collapse()` ran, by call or on scroll (FLO-319) */
+    /** `collapse()` ran, by call or on scroll */
     collapse: () => void;
-    /** `expand()` ran, by call or on scroll (FLO-319) */
+    /** `expand()` ran, by call or on scroll */
     expand: () => void;
 }
 /**
@@ -524,7 +524,7 @@ export interface ExtendedFabComponent {
      * ```
      */
     disable: () => ExtendedFabComponent;
-    /** Whether the extended FAB is disabled (FLO-384) */
+    /** Whether the extended FAB is disabled */
     isDisabled: () => boolean;
     /**
      * Sets the Extended FAB's icon

package/dist/components/fab/types.d.ts

@@ -231,7 +231,6 @@ export interface FabConfig {
     /**
      * Accessible name. Required: an icon-only control has no text for a screen
      * reader to announce, so without this it is just "button" (WCAG 4.1.2).
-     * FLO-110.
      */
     ariaLabel: string;
     /**
@@ -336,7 +335,7 @@ export interface FabConfig {
  *
  * `on` and `off` are generic over these keys, so a misspelled event name is a
  * compile error rather than a listener that never fires, and the handler's
- * payload is typed rather than `Function`'s implicit `any`. FLO-114.
+ * payload is typed rather than `Function`'s implicit `any`.
  */
 export interface FabEvents extends TouchEvents {
     /** The FAB was clicked. Not forwarded while the FAB is disabled. */
@@ -459,7 +458,7 @@ export interface FabComponent {
      * ```
      */
     disable: () => FabComponent;
-    /** Whether the FAB is disabled (FLO-384) */
+    /** Whether the FAB is disabled */
     isDisabled: () => boolean;
     /**
      * Sets the FAB's icon

package/dist/components/fab-menu/types.d.ts

@@ -81,7 +81,7 @@ export interface FabMenuEvents {
     close: () => void;
     /**
      * An item was chosen; the menu closes. `value` is the item's id again, as
-     * the `value` of `<m-fab-menu>`'s `select` (the FLO-320 payload rule)
+     * the `value` of `<m-fab-menu>`'s `select` (the payload rule)
      */
     select: (event: {
         id: string;

package/dist/components/icon-button/types.d.ts

@@ -137,7 +137,6 @@ export interface IconButtonConfig extends BaseComponentConfig {
     /**
      * Accessible name. Required: an icon-only control has no text for a screen
      * reader to announce, so without this it is just "button" (WCAG 4.1.2).
-     * FLO-110.
      */
     ariaLabel: string;
     /**
@@ -196,7 +195,7 @@ export interface ToggleManager {
      */
     isSelected: () => boolean;
 }
-/** A toggle icon button's `change` (FLO-380). */
+/** A toggle icon button's `change`. */
 export interface IconButtonChangePayload {
     /** Whether the button is now selected */
     selected: boolean;
@@ -209,10 +208,10 @@ export interface IconButtonChangePayload {
  */
 export interface IconButtonEvents extends TouchEvents {
     /**
-     * A toggle button's selected state changed on a click (FLO-295). The DOM
+     * A toggle button's selected state changed on a click. The DOM
      * `toggle` event on `element` is deprecated and goes in the next release.
      * `value` is the button's value (`getValue()`), as every model event
-     * carries (FLO-380); `selected` is the toggled state.
+     * carries; `selected` is the toggled state.
      */
     change: (payload: IconButtonChangePayload) => void;
     /** Clicks are not forwarded while the button is disabled. */
@@ -316,7 +315,7 @@ export interface IconButtonComponent {
      * @returns The IconButton component for chaining
      */
     disable: () => IconButtonComponent;
-    /** Whether the icon button is disabled (FLO-384) */
+    /** Whether the icon button is disabled */
     isDisabled: () => boolean;
     /**
      * Sets the IconButton's icon

package/dist/components/list/types.d.ts

@@ -232,7 +232,7 @@ export interface SelectEvent<T = unknown> {
     item: T;
     /**
      * The item's id as a string, the `value` of the `<m-list>` element's
-     * `activate` (FLO-320)
+     * `activate`
      */
     value: string;
     /**

package/dist/components/menu/features/loader.d.ts

@@ -13,7 +13,7 @@ export interface SubmenuLoader {
 /** True when an item opens a submenu: the only case that needs the feature. */
 export declare const hasNestedItems: (items: MenuContent[] | undefined) => boolean;
 /**
- * Loads the submenu feature on demand (FLO-310).
+ * Loads the submenu feature on demand.
  *
  * The feature is most of what a menu with nested items adds, and a menu
  * without them never uses it, so it is a chunk of its own rather than part of

package/dist/components/menu/types.d.ts

@@ -152,7 +152,7 @@ export interface MenuConfig {
     /**
      * The element the menu is placed against, when it is not the opener's: a
      * select's field, so its supporting text row never pushes the menu down
-     * (FLO-300). The opener still opens, closes and gets focus back.
+     * The opener still opens, closes and gets focus back.
      */
     positionTarget?: HTMLElement;
     /**
@@ -321,7 +321,7 @@ export interface MenuSelectEvent<TData = unknown> extends MenuEvent {
     item: MenuItem<TData>;
     /** ID of the selected menu item */
     itemId: string;
-    /** The item's id again, as the `value` of the `<m-menu>` element's `select` (FLO-320) */
+    /** The item's id again, as the `value` of the `<m-menu>` element's `select` */
     value: string;
     /** Data associated with the menu item (if any) */
     itemData?: TData;
@@ -500,7 +500,7 @@ export interface MenuEvents {
  *
  * Declared here rather than in features/keyboard.ts so the host below can
  * name it: a host that types its manager methods needs their parameter types
- * in scope. FLO-114.
+ * in scope.
  */
 export interface KeyboardMenuState {
     items: MenuContent[];

package/dist/components/navigation-bar/types.d.ts

@@ -55,7 +55,7 @@ export interface NavigationBarComponent {
         destroy: () => void;
     };
     getActive: () => string | null;
-    /** The active destination's id, as getActive(): the value getter every component has (FLO-380) */
+    /** The active destination's id, as getActive(): the value getter every component has */
     getValue: () => string | null;
     /** Marks a destination active, silently (no `select`); `null` clears it */
     setActive: (id: string | null) => NavigationBarComponent;

package/dist/components/navigation-rail/types.d.ts

@@ -16,7 +16,7 @@ export interface NavigationRailItemConfig {
 }
 export interface NavigationRailSelectEvent {
     id: string;
-    /** The id again, as the `value` of the `<m-navigation-rail>` element's `change` (FLO-320) */
+    /** The id again, as the `value` of the `<m-navigation-rail>` element's `change` */
     value: string;
     index: number;
     originalEvent: MouseEvent;
@@ -82,7 +82,7 @@ export interface NavigationRailComponent {
 /**
  * Registers NavigationRailConfig with the global defaults map, so
  * `setComponentDefaults("navigation-rail", ...)` is typed without core
- * importing anything from this component. FLO-115.
+ * importing anything from this component.
  */
 declare module "../../core/config/global" {
     interface ComponentConfigMap {

package/dist/components/progress/types.d.ts

@@ -291,7 +291,7 @@ export interface ProgressComponent {
     painted: () => Promise<void>;
     /**
      * Adds an event listener: `change` when the value is set, `complete` when it
-     * reaches the maximum. Handlers get `{ value, max }` (FLO-295: they got a DOM
+     * reaches the maximum. Handlers get `{ value, max }` (they got a DOM
      * CustomEvent, the payload in `event.detail`).
      */
     on: <K extends keyof ProgressEvents>(event: K, handler: ProgressEvents[K]) => ProgressComponent;

package/dist/components/radios/types.d.ts

@@ -160,7 +160,7 @@ export interface RadiosComponent {
      * @returns The radios component for chaining
      */
     disable: () => RadiosComponent;
-    /** Whether the whole group is disabled (FLO-384) */
+    /** Whether the whole group is disabled */
     isDisabled: () => boolean;
     /**
      * Enables a specific radio option