@uni-design-system/uni-core 9.0.1 → 10.1.0

package/CHANGELOG.md

@@ -1,5 +1,306 @@
 # @uni-design-system/uni-core
 
+## 10.1.0
+
+### Minor Changes
+
+- [`f28c951`](https://github.com/uni-design-system/uni/commit/f28c95117f2844b58a265b59c2ea8b9715156670) Thanks [@gaenglish](https://github.com/gaenglish)! - `uni-drawer` is a three-row panel, and is no longer its own scroll container.
+
+  **The `<dialog>` used to be the scroller.** `over` mode set `overflowY: 'auto'`
+  on the panel and put the theme's padding there too, which made a pinned header
+  or footer impossible: padding on a scrolling box scrolls away with its content,
+  and any row you pinned against it could not sit flush to the panel edge. It also
+  set only the one axis — and a single explicit overflow axis computes the other
+  to `auto`, which is exactly how a container becomes an accidental scroller.
+  `side` had it right already, setting both.
+
+  The panel is now a flex column of three rows — an optional
+  `[uni-drawer-header]`, the projected body, an optional `[uni-drawer-buttons]`
+  (alias `[drawer-buttons]`) — and **only the body scrolls**. The panel itself is
+  `overflow: clip` on both axes, explicitly, never the shorthand. The body carries
+  `overscroll-behavior: contain`, so scrolling to its end does not start scrolling
+  the page behind it, and `position: relative`, so a stray absolutely positioned
+  descendant is contained rather than re-homed into an ancestor.
+
+  Those two must travel together: a positioned body _without_ a clipped shell is
+  worse than the status quo, because it pulls phantom overflow into the scroller
+  instead of out of the panel.
+
+  **`drawer.behavior.padding` is now the body's padding, not the panel's.** A
+  drawer with no header or footer looks the same as before. One that gains either
+  gets rows flush to the panel edge, which is the point.
+
+  Two new theme entries, `drawerHeader` and `drawerButtons`, mirror the dialog
+  pair knob for knob but default to a panel's posture rather than a dialog's: the
+  header's title is left-aligned rather than centered, and the footer trails its
+  actions rather than centering them.
+
+  Note one deliberate divergence from `[dialog-buttons]`: the drawer footer's
+  **confirm button does not close the drawer**. A panel's save is usually async
+  and can fail, so closing is left to the consumer via `(confirmed)`.
+
+- [`67e17ea`](https://github.com/uni-design-system/uni/commit/67e17ea927e3ca24b7abecdcccf134d53ac3656b) Thanks [@gaenglish](https://github.com/gaenglish)! - `uni-toggle` honours `size`, and the checked colour has a theme home.
+
+  **`size` did nothing.** `uni-toggle` inherits a bindable `size` input from
+  `BaseComponent`, but its geometry came from a single `toggle.behavior.size`
+  number, so `<uni-toggle size="sm">` compiled, read as deliberate, and rendered
+  identically to every other switch. The theme now carries a `sizes` block and the
+  input selects from it.
+
+  **Geometry is stated per size, not derived from ratios.** Each size token is a
+  `width` / `height` / `padding` triple — `padding` being the knob's inset — and
+  the rest falls out: knob is `height - 2 * padding`, travel is `width - height`,
+  radius is `height / 2`. Real switch designs do not hold a constant proportion
+  across sizes (a consumer's 32x18 and 28x16 pair differs in both track and knob
+  ratio), so a single ratio token could match one size or the other but never
+  both.
+
+  `lg` is `BaseComponent`'s default and reproduces the previous geometry exactly —
+  40x20, knob 16 — so **no existing toggle moves**. A theme still setting the
+  legacy `toggle.behavior.size` number keeps the old derived-ratio behaviour; that
+  option is now deprecated in favour of the `sizes` block.
+
+  **Fixed: the knob would have overhung the track at any other proportion.** The
+  checked transform was hardcoded to translate by one track height, which is only
+  correct while the track is `2x` wide and the knob `0.8x`. It is now derived, so
+  the knob lands the same distance from each edge at every size.
+
+  **New `checkedColor`, as an input and a theme option.** The on-state used to be
+  the instance's `variant`, which meant an app wanting one switch colour repeated
+  an attribute on every call site. `toggle.behavior.checkedColor` sets it once;
+  the input overrides per instance; `variant` remains the fallback when neither is
+  set. The focus ring follows the resolved colour rather than staying on `variant`.
+  An input as well as an option is necessary because `variant` defaults to
+  `'primary'` and so cannot be distinguished from unset — without one, a themed
+  `checkedColor` would have silently made `variant` inert with no way back.
+
+  **Toggle transitions are a motion token.** It hardcoded `0.3s ease` while
+  `uni-radio` already read `theme.motion(options.motion ?? 'control')`, so a theme
+  setting a motion scale moved the radio and not the switch.
+
+### Patch Changes
+
+- [`7545ff3`](https://github.com/uni-design-system/uni/commit/7545ff3e6dd85d29157963488f75f9e3681947c7) Thanks [@gaenglish](https://github.com/gaenglish)! - Stepper buttons now leave focus in their field, and `uni-quantity-stepper`
+  follows the theme's field chrome.
+
+  **Clicking `+` or `−` focused nothing.** Taking pointer capture means calling
+  `preventDefault()` on `pointerdown`, which also suppresses the browser's default
+  focus handling — and the buttons carry `tabindex="-1"`, so focus landed on
+  `<body>`. The arrow keys then did nothing, exactly when a user reaching for `+`
+  is most likely to try them. `createPressRepeat` gained a `focus` callback,
+  invoked on press and handed the pressed button; `uni-number-input` and
+  `uni-quantity-stepper` point it at their text field, the way a native spinner
+  does. Where there is no field — a read-only quantity stepper, whose buttons are
+  themselves the tab stops — focus goes to the button instead. **This affected
+  `uni-number-input` as well**, not just the stepper.
+
+  **`uni-quantity-stepper` ignored a theme's field styling.** It carried its own
+  `color` / `border` / `borderRadius` tokens, so a theme that restyles `input` —
+  Wellsourced fills its fields `#F3F2EF` — left the stepper stark white beside
+  them. Those three now default to the shared `input` chrome and are unset in the
+  base theme, so the stepper tracks whatever a theme does to its fields; they
+  remain available as per-component overrides for parting them deliberately. With
+  the focus indicator and the dividers already sourced this way, the container is
+  now consistently the field chrome unless a theme says otherwise.
+
+## 10.0.0
+
+### Major Changes
+
+- [`21b655d`](https://github.com/uni-design-system/uni/commit/21b655df0f93e2e2de6a22ccf38050b474d4e5ab) Thanks [@gaenglish](https://github.com/gaenglish)! - `uni-slider` is rebuilt on custom thumbs instead of `<input type="range">`,
+  gaining range mode, marks, a value readout and an exact decimal step model. This
+  is a breaking change to both the component's value shape and its theme options.
+
+  **Why it could not stay native.** One `<input type="range">` cannot carry two
+  thumbs, so range mode, thumb crossing and per-thumb ARIA bounds were all
+  unreachable; marks and a value tooltip were unstyleable through it. The
+  alternative — a second component for the range case — would have meant two
+  keyboard implementations to keep in step, which is the drift the shared step
+  model exists to prevent. What the platform was giving us (the slider ARIA
+  pattern and the keyboard map) is reimplemented explicitly and covered by 29
+  specs.
+
+  **Breaking: value shape.**
+
+  ```ts
+  // before
+  value = model<number>(0);
+  // after — the shape follows `mode`, and `null` is empty
+  value = model<number | UniNumberRange | null>(null);
+  ```
+
+  A `single` slider still reads and writes a plain number, so
+  `[(value)]="volume"` is unchanged. Code that relied on `value()` being
+  non-nullable, or that read it without narrowing, now needs to handle `null` and
+  the `{ start, end }` range.
+
+  **Breaking: theme options.** `slider.options.color` is **removed**. Fill and
+  thumb colour now come from the `variant` role pair, the rule every other
+  component follows, so `variant="warn"` recolours a slider with no theme edit. A
+  theme that set `color` should delete it and pass `variant` at the call site.
+  `trackColor` now defaults to `primary-container` rather than `surface-variant`.
+
+  New options: `thumbBorderRadius`, `minTouchTarget`, `markSize`, `markColor`,
+  `labelTypeface`, `labelColor`, `tooltipColor`, `tooltipTextColor`,
+  `tooltipShadow`, `tooltipBorderRadius`, `transitionMs`. `trackHeight`,
+  `thumbSize` and `borderRadius` are unchanged.
+
+  **New capability.**
+  - `mode="range"` — two thumbs, a `{ start, end }` value, `minGap` to fence the
+    ends apart. Thumbs may cross and swap, and the dragged one keeps focus.
+  - `marks` and `snapToMarks` — labelled stops, spoken in place of the number.
+  - `valueDisplay` — `none`, `inline`, `tooltip`, or `input`, which seats a
+    compact `uni-number-input` at the trailing edge, two-way bound to the same
+    value: drag for the ballpark, type for the exact figure. Single mode only.
+  - `origin` — anchor the fill somewhere other than `min`, for sliders spanning ±.
+  - `sliding` and `changed` outputs, replacing an implicit per-frame model write.
+    **Bind `changed` in forms**; `sliding` fires every frame of a drag.
+  - `largeStep`, defaulting to a tenth of the range, for `PageUp`/`PageDown` and
+    `Shift+Arrow`.
+  - Right-to-left support: the horizontal arrows and the track mirror; the value
+    does not.
+
+  **Also new: the `cdk/number` primitives** this is built on, shared with the
+  numeric input family still to come — exact scaled-`BigInt` decimal arithmetic
+  (`stepDecimal`, `roundDecimal`, `clampDecimal`), locale-aware
+  `parseNumber`/`formatNumber` over `Intl`, and `createPressRepeat` for
+  hold-to-repeat stepper buttons. Stepping `0.1` twenty times from `0` now lands
+  on exactly `2`, and `1.15` rounds to `1.2` where `(1.15).toFixed(1)` gives
+  `'1.1'`.
+
+### Minor Changes
+
+- [`2a79bb8`](https://github.com/uni-design-system/uni/commit/2a79bb8ebd8fd0b5cd792697972b6f48b444c80f) Thanks [@gaenglish](https://github.com/gaenglish)! - New `uni-number-input`: the field for a quantity, a price, a percentage or a
+  measurement, with locale-aware parsing, `Intl` formatting on commit,
+  prefix/suffix adornments, min/max/step fences and steppers that hold to repeat.
+
+  ```html
+  <uni-number-input label="Quantity" [(value)]="qty" [min]="1" />
+  <uni-number-input label="Unit price" currency="USD" [(value)]="price" />
+  ```
+
+  **Why not `<input type="number">`.** Per the HTML value sanitization algorithm,
+  a number input whose text is not a valid floating-point number reports
+  `value === ''`. Type `12,50` as most of Europe does, or paste `1,234.56` from a
+  spreadsheet, and the app reads an empty field with no way to tell that from a
+  blank one — a data-loss bug, and the reason this is `type="text"` with
+  `role="spinbutton"`. The platform control also cannot group thousands, cannot
+  place an affix outside the editable text, has ~10px unstyleable spinners below
+  the WCAG 2.2 target minimum, changes value on the scroll wheel while focused,
+  and steps in floats.
+
+  **What it does instead.**
+  - **Presets** — `decimal`, `integer`, `currency`, `percent` — supply decimals,
+    grouping, affix and `inputmode` together, so a money field is `label`,
+    `currency="USD"`, `[(value)]`. `numberFormat` is the escape hatch, merged over
+    the preset.
+  - **Parses what people actually type**: canonical ASCII always, locale grouping
+    (`1.234,56` in German), pasted affixes and currency symbols, accounting
+    negatives `(1,234.56)`, localized digit systems, compact `1.5k`, and — behind
+    `allowExpressions` — spreadsheet arithmetic like `12*3`, via a shunting-yard
+    parser that never calls `eval`.
+  - **Unreadable text stays in the field**, flagged with a dashed underline and a
+    `rejected` event, rather than being silently swallowed.
+  - **Exact arithmetic.** Stepping `0.1` twenty times from `0` lands on exactly
+    `2`; `1.15` rounds to `1.2` where `(1.15).toFixed(1)` gives `'1.1'`. A second
+    `valueAsString` model carries digits a `number` cannot, and a dev-mode warning
+    fires when a bound `value` cannot round-trip.
+  - **Percent never divides behind your back**: `preset="percent"` shows `15%` for
+    `15`. Models that really are fractions set `valueIsFraction`.
+  - Clamping on commit rather than per keystroke, visible fences that disable the
+    matching stepper and announce, `wrap` for cyclic fields, `emptyStepValue`,
+    four stepper layouts, and hold-to-repeat that announces once on release.
+
+  `uni-slider` gains `valueDisplay="input"`, which seats one of these as its
+  readout — drag for the ballpark, type for the exact value.
+
+  Adds `numberInput` to `ComponentName` with a theme entry. Field chrome is not
+  duplicated there: colour, border, radius and focus come from the shared `input`
+  options via `uni-input-box`, so a number field restyles with every other field.
+
+  `uni-input-box` gains a `managedInset` input. The themed leading inset normally
+  rides the inner `<input>`, which is right while the text is the field's leading
+  edge and wrong the moment an adornment sits in front — a currency prefix would
+  hug the border while the number it belongs to sat indented past it. A field with
+  adornments sets `managedInset` and places the inset on whichever element is
+  actually first. Existing fields are unaffected: the default is `false`.
+
+- [`e7875ee`](https://github.com/uni-design-system/uni/commit/e7875ee81030a703f4ca1904bb94cb8ddc7f57b9) Thanks [@gaenglish](https://github.com/gaenglish)! - New `uni-number-range-input`: two linked numeric fields in one chrome with a
+  single `{ start, end }` value — price filters, thresholds, tolerances. This
+  completes the numeric family alongside `uni-number-input`,
+  `uni-quantity-stepper` and the rebuilt `uni-slider`.
+
+  ```html
+  <uni-number-range-input label="Price range" currency="USD" [(value)]="price" [minGap]="50" />
+  ```
+
+  `start`/`end` deliberately match `UniDateRange`, so the library has one range
+  vocabulary, and they never collide with the `min`/`max` **inputs**, which mean
+  the fence rather than the value.
+
+  **The rules that make it one field rather than two glued together:**
+  - **Either end alone is a valid value.** `{ start: 50 }` means "50 and up",
+    which is a real filter. This is where it diverges from `uni-date-time-input`,
+    whose two parts are two halves of one answer.
+  - **Stepping is fenced; typing swaps.** A stepper can never walk one end through
+    the other — its wall is the other end, held off by `minGap`, and each end's
+    `aria-valuemin`/`aria-valuemax` report that wall rather than the outer bounds.
+    A _typed_ backwards commit is swapped and announced instead, the rule
+    `uni-calendar` applies to a backwards date range: clamping against the other
+    end would destroy the number just entered.
+  - **`minGap` pushes the end you edited**, not the other one, which is what makes
+    stepping behave as a fence rather than dragging the range along.
+  - A refused draft flags only the end it was typed into; the other stays valid.
+  - `preset`, `currency`, `prefix`, `suffix`, `decimals`, `grouping`, `locale` and
+    `roundingMode` are forwarded to both ends so the halves always read alike.
+
+  It owns its commit path rather than nesting two `uni-number-input`s, because the
+  two behaviours above need _different_ bounds — a stepper must be fenced at the
+  other end while a typed commit must arrive un-clamped — and a child field
+  applies one bound pair to both. The arithmetic, parsing and formatting are still
+  the shared `cdk/number` primitives.
+
+  Adds `numberRangeInput` to `ComponentName` with a theme entry (`partGap`,
+  `dividerText`, `dividerColor`). Field chrome is not duplicated there: colour,
+  border, radius and focus come from the shared `input` options via
+  `uni-input-box`. `dividerText` is literal punctuation rather than an icon token —
+  an en dash between two numbers is not a glyph a theme swaps artwork for.
+
+- [`589cecb`](https://github.com/uni-design-system/uni/commit/589cecb178d9119eea3fbc3f3cd9149eefdaa036) Thanks [@gaenglish](https://github.com/gaenglish)! - New `uni-quantity-stepper`: `− 3 +` for cart lines, table cells and seat counts
+  — the numeric core with no field chrome, no label and no room for either.
+
+  ```html
+  <uni-quantity-stepper label="Quantity, Blue T-shirt (M)" [(value)]="qty" [min]="1" />
+  ```
+
+  A separate component rather than a `chrome="bare"` flag on `uni-number-input`,
+  because this control is defined by what it does _not_ have — presets, affixes,
+  expressions, four stepper layouts — and eight inputs are easier to write
+  correctly than forty plus a list of which ones to leave alone. The arithmetic,
+  parsing and hold-to-repeat come from the same `cdk/number` primitives, so
+  `1,200` and the keyboard map behave identically in both.
+  - **`deleteAtMin`** is the cart pattern in one attribute: at the floor the
+    decrement becomes a remove affordance, renamed `Remove {label}`, and emits
+    `removed` rather than stepping to zero. Without it every shop reimplements the
+    same `value === 1 ? remove() : step(-1)` branch outside the component. (The
+    spec called this output `emptied`; that is a native `HTMLMediaElement` event
+    name, which `@angular-eslint/no-output-native` rightly rejects, and `removed`
+    is already what `uni-tag` calls the same request.)
+  - The middle is a real input by default — typing `12` beats tapping `+` eleven
+    times, and it takes the same grouped and locale-aware entry the field does.
+    `editable=false` renders the number as text for read-mostly tables, and the
+    buttons become the tab stops since there is nothing else to focus.
+  - `size` is `sm` / `md` / `lg` at 24 / 32 / 40px _outer_ height, so an `md`
+    stepper lines up with a 32px field beside it, with the buttons square at that
+    height. `md` and `lg` clear the 24×24 pointer target of WCAG 2.2 SC 2.5.8;
+    `sm` leaves 22px inside its border and is the dense desktop option.
+
+  Adds `quantityStepper` to `ComponentName` with a theme entry. Unlike the other
+  numeric controls it does **not** inherit the shared `input` chrome — it is not a
+  field — so it carries its own container tokens, defaulted to the same values
+  `input` uses so a cart stepper and a form field look related out of the box.
+  Height comes from the entry's `sizes` block rather than an option.
+
 ## 9.0.1
 
 ### Patch Changes

package/dist/cjs/index.cjs

@@ -1099,7 +1099,30 @@ var buildComponents = (c) => ({
 		divider: "light",
 		elevation: "menu",
 		padding: "md",
-		backdrop: { background: "rgba(0, 0, 0, 0.4)" }
+		backdrop: { background: "rgba(0, 0, 0, 0.4)" },
+		scrim: true,
+		background: "solid"
+	} },
+	drawerHeader: { options: {
+		color: void 0,
+		height: 56,
+		padding: "md",
+		textRole: "title-medium",
+		textAlign: "left",
+		divider: "light",
+		closeButtonIcon: "close",
+		closeButtonSize: "md"
+	} },
+	drawerButtons: { options: {
+		gap: "sm",
+		padding: "md",
+		justifyContent: "flex-end",
+		confirmButtonVariant: "primary",
+		cancelButtonVariant: "quaternary",
+		buttonSize: "md",
+		divider: "light",
+		stretch: false,
+		reverseOrder: false
 	} },
 	avatar: {
 		options: {
@@ -1294,6 +1317,44 @@ var buildComponents = (c) => ({
 		rows: 3,
 		resize: "vertical"
 	} },
+	numberInput: { options: {
+		stepperLayout: "stacked",
+		incrementIcon: "plus",
+		decrementIcon: "minus",
+		stepUpIcon: "chevronUp",
+		stepDownIcon: "chevronDown",
+		stepperWidth: 32,
+		minTouchTarget: 24,
+		affixColor: "on-primary-surface-variant",
+		affixGap: "xs",
+		align: "start",
+		tabularNumerals: true,
+		repeatDelayMs: 500,
+		repeatIntervalMs: 100,
+		repeatFastIntervalMs: 25,
+		repeatRampMs: 2e3
+	} },
+	numberRangeInput: { options: {
+		partGap: "sm",
+		dividerText: "–",
+		dividerColor: "outline",
+		affixColor: "on-primary-surface-variant",
+		affixGap: "xs"
+	} },
+	quantityStepper: {
+		options: {
+			incrementIcon: "plus",
+			decrementIcon: "minus",
+			deleteIcon: "delete",
+			tabularNumerals: true,
+			valueWidth: "3ch"
+		},
+		sizes: {
+			sm: { height: 24 },
+			md: { height: 32 },
+			lg: { height: 40 }
+		}
+	},
 	tabs: { options: {
 		typeface: "title-small",
 		textColor: "on-surface-variant",
@@ -1717,11 +1778,21 @@ var buildComponents = (c) => ({
 		gap: "xxs"
 	} },
 	slider: { options: {
-		color: "primary",
-		trackColor: "surface-variant",
-		borderRadius: "max",
 		trackHeight: 4,
-		thumbSize: 16
+		trackColor: "primary-container",
+		borderRadius: "max",
+		thumbSize: 16,
+		thumbBorderRadius: "max",
+		minTouchTarget: 24,
+		markSize: 3,
+		markColor: "on-primary-container",
+		labelTypeface: "label",
+		labelColor: "on-surface-variant",
+		tooltipColor: "inverse-surface",
+		tooltipTextColor: "on-inverse-surface",
+		tooltipShadow: "menu",
+		tooltipBorderRadius: "xs",
+		transitionMs: 120
 	} },
 	skeleton: { options: {
 		color: "surface-variant",
@@ -1744,11 +1815,30 @@ var buildComponents = (c) => ({
 		grade: 0,
 		opticalSize: 24
 	} },
-	toggle: { options: {
-		size: 20,
-		trackColor: "surface-variant",
-		knobColor: "surface"
-	} },
+	toggle: {
+		options: {
+			trackColor: "surface-variant",
+			knobColor: "surface",
+			motion: "control"
+		},
+		sizes: {
+			sm: {
+				width: 28,
+				height: 16,
+				padding: 3
+			},
+			md: {
+				width: 32,
+				height: 18,
+				padding: 3
+			},
+			lg: {
+				width: 40,
+				height: 20,
+				padding: 2
+			}
+		}
+	},
 	tooltip: { options: {
 		border: void 0,
 		borderRadius: "xs",