@uni-design-system/uni-core 10.0.0 → 10.2.0

package/CHANGELOG.md

@@ -1,5 +1,195 @@
 # @uni-design-system/uni-core
 
+## 10.2.0
+
+### Minor Changes
+
+- [`1cd0140`](https://github.com/uni-design-system/uni/commit/1cd0140d2e6a4c753f48fb46418ba08769979263) Thanks [@gaenglish](https://github.com/gaenglish)! - Checkbox, radio and toggle take their accent from the theme, not from the
+  variant's name.
+
+  **Twelve sites across the three controls resolved a variant name as a colour
+  token.** That held together only because every name in the closed union happened
+  to also be a colour. Under an open registry the coincidence ends by design:
+  `<uni-checkbox variant="destructive">` would look up `colors['destructive']`,
+  miss, and **silently render primary** — a wrong-coloured control with no error,
+  no warning, and nothing to grep for.
+
+  Checkbox was worse than it looked. Alongside five `getThemeColor` calls it had
+  two more through a second resolver that built `on-${variant}`, so an
+  unregistered intent also missed its paired content colour and fell back to
+  `on-primary` — the tick would have stayed light on a dark fill even after the
+  box was fixed.
+
+  The theme now says which colour draws each intent, through a new
+  `variantOptions` map on `ComponentTheme`:
+
+  ```ts
+  checkbox: {
+    variantOptions: {
+      primary: { accent: 'primary' },
+      warn: { accent: 'warn' },
+    },
+  }
+  ```
+
+  `variantOptions` is per-variant data a component **reads**, as against `variants`,
+  which is CSS that gets **applied**. The distinction earns its place here: a
+  checkbox's accent lands on the box outline, the checked and indeterminate fills,
+  the tick and the focus ring at once, and expressing that as CSS would have meant
+  the theme naming `.checkbox-check` and `.radio-inner` — promoting private DOM to
+  public theme contract.
+
+  All three controls gain a `checkedColor` input as the per-instance override,
+  matching the one `uni-toggle` already had; its resolution order is now input →
+  the variant's themed accent → theme option. The base theme defines the same
+  seven intents `button` and `iconButton` do, so the library is consistent about
+  which exist by default, and `getThemeColor` — triplicated byte-for-byte across
+  the three components, with a silent fallback to primary — is gone.
+
+  Rendering is unchanged for anything that does not set `variant`: the default
+  still resolves to the primary accent and its paired on-colour.
+
+- [`1cd0140`](https://github.com/uni-design-system/uni/commit/1cd0140d2e6a4c753f48fb46418ba08769979263) Thanks [@gaenglish](https://github.com/gaenglish)! - `Variant` is an open registry: a design system can define its own intents.
+
+  A variant names _what an action means_, and it is the theme's job to describe
+  how that intent is drawn. So the set of names was never Uni's to fix — an app
+  whose actions are `destructive`, `subtle` and `info` had to translate them onto
+  twelve names chosen elsewhere. `Variant` is now `keyof UniVariantRegistry`,
+  extended by declaration merging:
+
+  ```ts
+  declare module '@uni-design-system/uni-core' {
+    interface UniVariantRegistry {
+      destructive: true;
+    }
+  }
+  ```
+
+  `variant="destructive"` then compiles wherever a variant is accepted, and
+  `variant="destructve"` still does not — which the library's other open-token
+  idiom, `Named | (string & {})`, cannot give you, and which would also have
+  collapsed the theme's `variants` map keys to `string`.
+
+  Only the type was ever closed: theme validation checks the _shape_ of a
+  `variants` block and never its key names, so a custom variant already reached
+  `componentStyle` untouched at runtime.
+
+  **The registry extends; it cannot replace.** Declaration merging has no way to
+  remove a member, so Uni's twelve names stay legal in a consuming app; enforcing
+  a house set is a lint concern rather than a type. Two names are reserved and
+  documented as always present: `primary`, which every component inherits as its
+  default, and `disabled`, which the disabled state resolves to.
+
+  **An unthemed variant now says so.** With a closed union this was nearly
+  impossible; with an open set it is the ordinary state of a work in progress —
+  a variant registered and used before its theme block exists. The theme service
+  warns once per component and variant in dev, naming what the theme does define,
+  mirroring what it already did for an unknown spacing token. Components that
+  theme no variants at all stay silent, since a missing key there is not a gap.
+
+## 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

package/dist/cjs/index.cjs

@@ -1057,6 +1057,30 @@ var buildBorders = (c) => ({
 * surface and draws the edge — so every role stays consistent and a theme can
 * still override any single cell.
 */
+/**
+* Accent roles for the selection controls (checkbox, radio, toggle).
+*
+* A variant names the intent; this says which colour token draws it, and the
+* component decides where it lands — the box fill, the ring, the dot, the
+* track, the focus ring. Keeping it as a role rather than a `variants`
+* StyleExpression is what stops interior class names like `.checkbox-check`
+* becoming public theme contract.
+*
+* The same seven names `button` and `iconButton` theme, so the library is
+* consistent about which intents exist by default.
+*/
+var SELECTION_ACCENTS = {
+	primary: { accent: "primary" },
+	secondary: { accent: "secondary" },
+	tertiary: { accent: "tertiary" },
+	warn: { accent: "warn" },
+	success: { accent: "success" },
+	disabled: { accent: "disabled" },
+	ghost: {
+		accent: "ghost",
+		onAccent: "on-primary"
+	}
+};
 var tagVariant = (c, role) => ({ [role]: {
 	backgroundColor: c[`${role}-container`],
 	color: c[`on-${role}-container`],
@@ -1099,7 +1123,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: {
@@ -1170,18 +1217,24 @@ var buildComponents = (c) => ({
 		activeColor: "primary-container",
 		maxSuggestions: 8
 	} },
-	checkbox: { options: {
-		size: 20,
-		boxColor: "surface",
-		borderRadius: 2,
-		focusRingGap: 2
-	} },
-	radio: { options: {
-		size: 20,
-		ringColor: "outline",
-		fillColor: "surface",
-		motion: "control"
-	} },
+	checkbox: {
+		options: {
+			size: 20,
+			boxColor: "surface",
+			borderRadius: 2,
+			focusRingGap: 2
+		},
+		variantOptions: SELECTION_ACCENTS
+	},
+	radio: {
+		options: {
+			size: 20,
+			ringColor: "outline",
+			fillColor: "surface",
+			motion: "control"
+		},
+		variantOptions: SELECTION_ACCENTS
+	},
 	dialog: { options: {
 		borderRadius: "lg",
 		color: "primary-surface",
@@ -1243,13 +1296,16 @@ var buildComponents = (c) => ({
 			activeSymbol: "check",
 			motion: "control"
 		},
-		variants: { warn: {
-			color: c.warn,
-			[HOVER_OR_KEYBOARD_FOCUS]: {
-				backgroundColor: c["warn-container"],
-				color: c["on-warn-container"]
+		variants: {
+			primary: {},
+			warn: {
+				color: c.warn,
+				[HOVER_OR_KEYBOARD_FOCUS]: {
+					backgroundColor: c["warn-container"],
+					color: c["on-warn-container"]
+				}
 			}
-		} }
+		}
 	},
 	popover: { options: {
 		color: "primary-surface",
@@ -1320,9 +1376,6 @@ var buildComponents = (c) => ({
 	} },
 	quantityStepper: {
 		options: {
-			color: "primary-surface",
-			border: "light",
-			borderRadius: "xs",
 			incrementIcon: "plus",
 			decrementIcon: "minus",
 			deleteIcon: "delete",
@@ -1795,11 +1848,31 @@ 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"
+		},
+		variantOptions: SELECTION_ACCENTS,
+		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",
@@ -2604,6 +2677,17 @@ var checkComponents = (value, issues) => {
 			}
 			for (const [key, style] of Object.entries(styles)) if (style !== void 0) checkStyleExpression(style, `components.${name}.${section}.${key}`, issues);
 		}
+		const variantOptions = entry["variantOptions"];
+		if (variantOptions !== void 0) {
+			if (!isRecord(variantOptions)) issues.push({
+				path: `components.${name}.variantOptions`,
+				message: "must be an object"
+			});
+			else for (const [key, roles] of Object.entries(variantOptions)) if (roles !== void 0 && !isRecord(roles)) issues.push({
+				path: `components.${name}.variantOptions.${key}`,
+				message: "must be an object"
+			});
+		}
 		if (entry["options"] !== void 0 && !isRecord(entry["options"])) issues.push({
 			path: `components.${name}.options`,
 			message: "must be an object"