@ids-group-ltd/ids-design-system 0.9.0 → 0.10.0

This diff represents the content of publicly available package versions that have been released to one of the supported registries. The information contained in this diff is provided for informational purposes only and reflects changes between package versions as they appear in their respective public registries.
package/CHANGELOG.md CHANGED
@@ -8,10 +8,797 @@ While the package is on `0.x`, minor releases may contain breaking changes.
8
8
 
9
9
  ## Unreleased
10
10
 
11
+ ## 0.10.0 — 2026-08-18
12
+
13
+ ### Added
14
+
15
+ - **A capped chip trigger no longer grows a second line on a narrow screen.** Found by Stas testing the
16
+ docs on a phone: `[maxVisibleChips]="2"` honoured the count, ran out of width, and wrapped the text
17
+ input onto its own line — the exact growth the cap exists to prevent. **A number is now a CEILING**
18
+ ("at most N"), measured like `"fit"`, so a 412px trigger shows one chip and `+3 more` on one line
19
+ instead of two chips over two lines. `null` is unchanged and still the only mode that skips measuring.
20
+ Three faults sat behind it, all fixed: the trigger kept `flex-wrap: wrap` while capped, so the row
21
+ could never shrink — it just moved the input down; a squeezed chip wrapped its own label and stood
22
+ 46px tall beside 29px neighbours; and the measurement's width cache only filled on a render holding
23
+ EVERY chip, which a numeric cap never produces — so the fit silently fell back to "show them all".
24
+ The `+N more` marker also keeps its room whenever the cap hides anything, instead of being clipped to
25
+ `+2 mor`.
26
+
27
+ - **A `TableColumn` can say `width: 'content'`.** The column sizes to its widest cell and stops
28
+ wrapping, so the slack goes to the columns that should absorb it. An auto-layout table spreads
29
+ leftover width evenly, which is why a status or a figure ends up as wide as its own header while the
30
+ name column that should take the space does not — and a pixel `width` cannot express that, since
31
+ pinning one column leaves the rest spreading. Measured in the docs demo: two `'content'` columns come
32
+ out at 89px and 94px while the two ordinary ones take 438px and 530px of the same 1152px table.
33
+ **You can now delete** the `::ng-deep ds-table { .table th, .table td { width: 1%; white-space: nowrap } }`
34
+ block — the last reach into the table's markup a consumer had left, still marked in their tree as
35
+ `TODO(ds-shrink-to-content)`. Dragging a column's edge still wins, because that is a deliberate
36
+ pixel width — but note it wins for the WHOLE table at once: on a `resizableColumns` table the first
37
+ drag OR resize keystroke anywhere locks a measured pixel width onto every column that has not got
38
+ one, `'content'` columns included. `Home` on a column's own handle hands that one back; the column
39
+ panel's "Reset to default" button and clearing the public two-way `columnWidths` hand back all of
40
+ them. A `'content'`
41
+ column also has no clip width, so `truncate` on it is a no-op rather than an ellipsis against 240px.
42
+ The `title` attribute and the click-to-popover handler are still emitted on such a cell, but the
43
+ popover cannot open: it opens only when the cell measures as clipped, and this one never does.
44
+
45
+ - **`ds-table` takes `[loading]="true"` and picks the treatment itself** — skeleton rows while it has
46
+ nothing on screen, overlay once there are rows. `'skeleton'` and `'overlay'` still pin either one
47
+ deliberately, and `false` is unchanged. Which of the two is right is a function of the row count,
48
+ which the table already holds and every consumer was restating: **you can now delete** the
49
+ `items().length > 0 ? 'overlay' : 'skeleton'` computed beside each list — one consumer feature had
50
+ three copies. The rule is not a taste call, which is why it belongs here: replacing visible rows with
51
+ placeholders throws away what the reader is looking at, and dimming an empty card announces nothing
52
+ about what is coming, so a hardcoded `'overlay'` makes a first load read as an empty table that
53
+ flickers.
54
+
55
+ - **`ds-table` has a toolbar row you can put things in — one `[toolbar]` slot.** The component had two
56
+ projection slots in total (`[empty]`, `[bulk-actions]`) and its toolbar existed only while
57
+ `exportButton` was on, so a control that acts on THIS table — a search box, a status filter, a refresh
58
+ — had nowhere to sit next to Export. A consumer forked the table for exactly this; retiring the fork
59
+ pushed two screens' filter rows out of the table and onto the page, where a search + status pair reads
60
+ as page furniture one card away from the rows it narrows. **Project a handful of controls and the row
61
+ lays them out** (flex, wrap, 8px gap), so the ordinary case needs no CSS of yours; **project one
62
+ element of your own** and it stretches to fill the slot, so your layout is the only one in play — the
63
+ slot is the row minus the Export button, and the whole row when `exportButton` is off. The row
64
+ **collapses to nothing** when nothing filled it and `exportButton` is off, so a table that uses
65
+ neither is pixel-identical — the `div` is still in the DOM, hidden in CSS, so a
66
+ `ds-table > :first-child` selector or a DOM snapshot still sees it. Filters that belong to the PAGE
67
+ still belong in a `ds-filter-bar` above it.
68
+
69
+ - **`runExport()`, `exporting()` and `exportStatus()` are public**, so the Export button can live in a
70
+ page header, a filter bar or the new toolbar slot and still run the library's path — the
71
+ `exportFetcher` call, the download, the in-flight state and the live-region announcement. Until now the
72
+ only public export method was `exportCsv()`, which serialises the rows the table HOLDS: on a
73
+ server-paged grid that is one page, so a consumer's own button silently exported a fraction of the
74
+ data. Leave `exportButton` off and drive it yourself:
75
+ `<ds-button [loading]="table.exporting()" (pressed)="table.runExport()">`. That pairing wants an
76
+ `exportFetcher`: without one, `runExport()` falls through to `exportCsv()` synchronously and never
77
+ touches `exporting`/`exportStatus`, so an external button bound to them shows no progress at all.
78
+ The two signals are read-only — a subclass that used to `.set()` them (they were protected writables)
79
+ drives them through `runExport()` now.
80
+
81
+ - **`provideDsConfig` answers seven more inputs in this entry alone, so an app stops restating
82
+ itself.** Five of the release's eight new sections — `avatar`, `brand` and `modal` have their own
83
+ entries:
84
+ `control.size` (honoured by button, icon-button, input, textarea, select, autocomplete, search,
85
+ date/time picker, number stepper, checkbox, radio, switch and field-group), `card.elevation` and
86
+ `card.padding`, `table.stickyScrollbar` and `table.bordered`, `icon.size`, and `badge.withDot`.
87
+ Precedence is **input → config → built-in**, so a screen that differs still binds the attribute and
88
+ wins. **No default moved** — an app that provides nothing renders exactly as before, with one edge
89
+ worth knowing: the booleans that swapped `booleanAttribute` for a nullable transform
90
+ (`table.bordered`, `table.stickyScrollbar`, `badge.withDot`, and `dividers` on both modal components)
91
+ used to read a binding evaluating to `null`/`undefined` as `false`, and now read it as *unset* — so it
92
+ falls through to the config and then the built-in, which for `dividers` is `true`. A literal
93
+ `[bordered]="false"` is unaffected. **You can now
94
+ delete** the attribute an app repeats on every element: one consumer binds `[stickyScrollbar]="true"`
95
+ on all 35 of its tables and `size="sm"` on 146 buttons, which is a house default written 146 times,
96
+ and each new element is one forgotten binding away from looking wrong. `control.size` is a different
97
+ axis from `[data-density]`: the tier rewrites hit targets and padding in CSS for a route, this picks
98
+ which of the three declared sizes a control renders at, and an app can use both. Documented as one
99
+ page under Foundations → Theming rather than in scraps across eight component pages.
100
+
101
+ - **Option icons on every picker, and one shape behind all three.** `ds-multi-select` and
102
+ `ds-autocomplete` now render an option's `icon` before its label at 16px, which only `ds-select`
103
+ did. The three option types share a new exported `DsOption<T>` — they were three near-identical
104
+ interfaces, which is exactly why `icon` existed on one picker for a release. Each keeps its own
105
+ name (`SelectOption`, `MultiSelectOption`, `AutocompleteOption`), so nothing you import changes.
106
+ From the same shared shape `AutocompleteOption` gains `disabled?` and `icon?`, `MultiSelectOption`
107
+ gains `icon?`, and `SelectOption` — which already carried both — gains nothing.
108
+ **`ds-autocomplete` now acts on a `disabled` option**, where it used to ignore the flag entirely: the
109
+ row carries `.is-disabled` and `aria-disabled`, refuses the click, and **the arrow keys step OVER it** —
110
+ including when the panel opens or the filter re-runs, so the active row is never one that Enter would
111
+ ignore. Behaviourally this matches `ds-select` and `ds-multi-select`, which have honoured it all along.
112
+ The row greys out too: measured in the open panel it comes out `rgb(155,163,180)` against
113
+ `rgb(22,26,40)` for an enabled one, so the state is not subtle.
114
+
115
+ - **`maxVisibleChips="fit"` on `ds-autocomplete` and `ds-multi-select`** caps the chips by measured
116
+ width instead of a count: one line holds as many as the trigger is wide, the rest collapse into
117
+ "+N more", and the split is redone whenever the trigger resizes. **It is also the new default** — see
118
+ the Changed entry below for what that moves and how to opt out. Choose between the three by what has
119
+ to stay predictable: `"fit"` lets the count follow the width, a NUMBER adds an upper bound on top of
120
+ the same measuring, and `null` is the only mode that shows every chip and the only one that never
121
+ measures. **You can now delete** a `ResizeObserver`, container query or per-breakpoint
122
+ `maxVisibleChips` number written to keep a chip trigger on one line — and a `max-height` +
123
+ `overflow: hidden` cap, which clips a chip mid-glyph and hides the count instead of dropping whole
124
+ chips. The measurement is not free but it is bounded: it runs only where a chip row is rendered —
125
+ which on `ds-multi-select` means a non-empty selection, but on `ds-autocomplete` means any `multiple`
126
+ trigger, empty or not — widths are cached per selection, and a geometry guard skips the re-measure
127
+ when neither width nor count moved.
128
+
129
+ - **`--ds-dropdown-panel-radius` — the lever 0.9.0's notes promised and never shipped.** That release
130
+ said an 8px select panel could be restored with `--ds-select-panel-radius`; no such token existed,
131
+ so the advice did nothing (the note has been corrected). This is the honest version, and it is
132
+ panel-level rather than per-component on purpose: retuning one picker's corner is not a thing to
133
+ encourage, while `--ds-radius-panel` moves modal, popover and date picker too. Defaults to that
134
+ role, so an untouched theme is unchanged, and it is forwarded onto the portaled pane — scope it with
135
+ a selector (`ds-select { --ds-dropdown-panel-radius: 8px }`) and only that panel moves. Verified
136
+ in a browser: one select at 3px, the other 34 on the 12px role. **Two panels read it, not three:**
137
+ `ds-select` and `ds-autocomplete`. `ds-multi-select`'s panel hardcodes `--radius-md` and is reached by
138
+ neither this token nor `--ds-radius-panel` — so only `--radius-md` itself moves it, and that moves
139
+ buttons, fields and tooltips with it.
140
+
141
+ - **Two migration manifests were corrected and three more were written**, so re-read them if you
142
+ subclass a DS component or upgrade across a version you skipped. `0.9.0`'s named no member collisions
143
+ at all — the note that now fills the gap lists **fifteen** classes whose member surface had grown, plus
144
+ four newly exported symbols that can shadow a local name — and `0.8.0`'s missed the private
145
+ `saveLayout` that actually stopped a build (`restoreLayout` went in beside it). **`0.6.1`, `0.6.2` and
146
+ `0.9.1` had no manifest at all**, and now every released version carries one: the auto-update planner
147
+ prefers a manifest and otherwise re-derives the plan from changelog prose on every run, which is what
148
+ an upgrade crossing those three used to do. `0.6.2`'s turned out to hold something actionable that no
149
+ machine-readable file had ever stated — a `ds-bottom-sheet` with nothing focusable inside it stopped
150
+ closing on Escape — which is exactly the kind a "just fixes" patch is assumed not to have.
151
+
152
+ - **`ds-avatar` takes a `name`, and the rule that reads it is replaceable.** One binding now does both
153
+ jobs a caller used to wire by hand: it derives the initials and seeds the tint. **The tint hashes the
154
+ NAME, not the initials** — two letters collide wholesale, so Alice Brown and Adam Bell used to share a
155
+ colour whenever a caller seeded from the letters. Swap the rule with `[initialsRule]` on one table or
156
+ `provideDsConfig({ avatar: { initials } })` for the app; an explicit `initials` still wins over both,
157
+ and `seed` still overrides the hash input when identity is an id or an email. The built-in rule is
158
+ `initialsFrom` — first two words — and the docs now say plainly that it is a Latin-script guess: how a
159
+ name is read is a cultural convention, not a UI decision, so the library takes yours rather than
160
+ shipping modes it cannot get right. **You can now delete** the `[seed]`/`[initials]` pair you compute
161
+ beside every avatar. `name` feeds the initials and the tint and nothing else: the avatar stays
162
+ `aria-hidden` unless you bind `ariaLabel`, so a `[name]` on its own leaves it silent to a screen
163
+ reader.
164
+
165
+ - **`DS_CONFIG.brand` — set the brand once instead of on every screen.**
166
+ `provideDsConfig({ brand: { name, logoLetter, tagline } })` answers `ds-sidenav` and `ds-auth-layout`
167
+ together — `name` and `logoLetter` on both, `tagline` on the auth layout, which is the only one of the
168
+ two with a strapline row. They ask the same questions and an app answers them identically, so six auth
169
+ screens were binding the same values six times. Each field resolves on its own, so a screen can
170
+ override the name without restating the letter — and `brand=""` drops the wordmark while a
171
+ `logoLetter` in the config
172
+ still paints its tile, so clear both to give a screen no brand row. **The two-tone wordmark stays
173
+ projected:** there is deliberately no accent in the config, because a string would have to be split
174
+ back apart to find one and that is the guessing `[dsBrandName]` exists to avoid. The projection wins
175
+ over both. **You can now delete** an adapter component that existed to inject a brand object and fan
176
+ it out into four bindings.
177
+
178
+ - **`rememberLastTab` on `ds-tabs` — reopen the tab a screen was last left on.** Off by default, and
179
+ inert without `urlParam` (and outside a routed context), because the parameter supplies the names: a
180
+ remembered INDEX would repoint the moment a tab is inserted. Stored under
181
+ `ds-tabs:{path}:{param}` in `sessionStorage`, so two strips on one path stay apart and tomorrow is a
182
+ fresh visit. **A link always wins** — the query parameter is read first, and memory answers whenever
183
+ it is absent, which is any arrival at the bare path, the deliberately-empty first tab included.
184
+ Tab one is remembered too, or going back to it would be forgotten. Only a user's own click or
185
+ keypress writes the memory; a host driving `selectedIndex` writes neither it nor the URL, as before.
186
+ **You can now delete** a helper that kept the last tab per path.
187
+
188
+ - **`DS_CONFIG.modal.dividers` — turn modal rules off for a whole app in one declaration.**
189
+ `provideDsConfig({ modal: { dividers: false } })` instead of a binding on every `<ds-modal>`, with an
190
+ explicit `[dividers]` on an element still winning. It also reaches where an attribute cannot: a
191
+ `ModalService` confirm renders a `ds-modal-card` with no `ds-modal` ancestor to bind, and the injected
192
+ default gets there (verified — the confirm's card comes out `no-dividers`). One limit on that: the
193
+ service is `providedIn: 'root'` and builds the confirm's injector from the root, so only a ROOT-level
194
+ `provideDsConfig` reaches it — a route- or component-scoped one does not. **You can now delete** a
195
+ `dividers` binding repeated per modal, and any `!important` reach into `.modal > .header|.body|.actions`
196
+ written because the token swap left the padding stacked. Note `[dividers]` now reads
197
+ `boolean | null` internally so "unset" is distinguishable from `false`. A literal `[dividers]="false"`
198
+ is unaffected; a binding that can evaluate to `null`/`undefined` is not, since that used to mean
199
+ "off" and now means "unset", which resolves to `true`.
200
+
201
+ - **`triggerSize` on `ds-filter-bar`, to match its "+N" trigger to the filters beside it.** Default
202
+ `md`, so nothing moves. The bar cannot work this out for itself — `dsFilterItem` carries a width and
203
+ the filters are arbitrary projected controls whose own `size` it never sees — so a row of `sm`
204
+ filters got an `md` trigger standing 8px taller under `align-items: flex-end`. **You can now delete**
205
+ `--ds-button-height` / `-font-size` / `-pad-x` pinned under `ds-filter-bar` to force this.
206
+
207
+ - **`[debounce]` on `ds-search`, so a list screen stops wrapping it.** `[debounce]="200"` holds each
208
+ keystroke back before `value` updates; the default `0` writes on every keystroke exactly as before,
209
+ and what the input SHOWS is never delayed at any setting. **Three things skip the timer on purpose**,
210
+ which is what a wrapped `debounceTime` usually gets wrong: emptying the field, the Clear button, and
211
+ Enter — the last flushing a keystroke still in flight so `submitted` carries what the reader can see.
212
+ Emptying also cancels a pending keystroke, so type-then-clear cannot land the stale query a moment
213
+ later. A host writing `value` mid-typing wins and cancels the timer. The Clear button follows what is
214
+ ON SCREEN rather than the debounced `value`, so at a non-zero delay it appears on the first keystroke
215
+ instead of after the wait. **You can now delete** a debounce wrapper around this control.
216
+
217
+ - **`--ds-stat-value-white-space` and `--ds-stat-value-font-size`, for a tile whose value is a phrase.**
218
+ The value line is `nowrap`, which is right for the number `ds-stat` was built around and wrong for a
219
+ date range or a status — so a text value spilled straight out past the tile's edge, and the way out
220
+ was the projected
221
+ `[dsStatValue]` slot plus two declarations undoing the component. Both default to today's values, so
222
+ nothing moves until you set them. **The size hook works at every `size`**, not just the default: the
223
+ `sm`/`lg` variants now move the same token instead of restating `font-size`, which used to out-rank
224
+ any override. **You can now delete** a `[dsStatValue]` span that exists only to set `white-space`
225
+ or a smaller size.
226
+
227
+ - **The global `.link` class now works on a `<button>`, which it has been documented as doing all
228
+ along.** `ds-button` warns `variant="text"` off in favour of `.link`, and an action that is not
229
+ navigation has to be a button — but the class was written for anchors and reset none of the browser's
230
+ button chrome, so everyone who took that advice wrote the same rule by hand. Measured against an
231
+ `<a class="link">` in the same paragraph, a button came out at 13.3px inside 14px text, with
232
+ `line-height: normal`, `1px 6px` of padding and an outset border; all of that is gone. **You can now
233
+ delete** a local `.link-button`, or the padding/border/background/font reset in your overrides.
234
+ `font-weight` is untouched so `.quiet` and `.standalone` still decide it, and `display` stays
235
+ `inline-block` so a standalone button lays out predictably. The reset is scoped with `:where()`, so
236
+ it sits at `.link`'s own specificity and your rule still wins on source order.
237
+
238
+ ### Fixed
239
+
240
+ - **A card no longer eats the Enter and Space of everything inside it.** `ds-card` bound
241
+ `(keydown.enter)` and `(keydown.space)` on its `<article>` with an unconditional `preventDefault()`,
242
+ and keydown bubbles — so a card cancelled the DEFAULT ACTION of both keys for its whole subtree, on
243
+ every card, not only the `elevation="interactive"` ones that are supposed to answer a key at all.
244
+ Measured on a sign-in screen made of `ds-card` + `ds-input` + `ds-checkbox`, driven with real key
245
+ events: Enter in the password field sent **no request at all** — the form could only be submitted by
246
+ clicking the button — Space did not toggle the "Remember me" box, Enter on a link inside the card did
247
+ not follow it, and a space could not be typed into a text field, so `John` + Space + `Smith` came out
248
+ as `JohnSmith`. Both handlers now run only on an interactive card, and only when the key landed on
249
+ the card itself rather than on something projected into it.
250
+
251
+ - **A table row's own controls answer the keyboard again.** `onRowKey` consumed Enter and Space for
252
+ every target inside an interactive `<tr>`, so the row's select checkbox could not be toggled with
253
+ Space and a cell's button could not be activated with Enter — the row-actions button carries a
254
+ `stopPropagation` workaround for exactly this. The row now opens only on a key pressed on the row
255
+ itself.
256
+
257
+ - **`ds-menu`'s type-ahead no longer swallows a projected field's typing.** Every printable character
258
+ reaching the menu jumped focus to an item and was consumed, which left a search or filter input
259
+ placed inside a menu impossible to type into. Keys from a text-entry control now pass through.
260
+
261
+ - **`ds-radio-group` no longer swallows Enter, so a form still submits from inside it.** The group
262
+ handled Enter as "select the focused radio" and prevented its default, which is neither native radio
263
+ behaviour nor what APG asks for — and inside a form it silently removed the keyboard's way to submit.
264
+ Enter is no longer handled; Space still selects. A text field sitting among the radios (the
265
+ `Other: ___` row) also keeps its own keys now.
266
+
267
+ - **A field in error no longer tints itself inside a `ds-field-group`, and an invalid group draws a red
268
+ border rather than a near-black one.** Two faults the field-state work left behind, both found by an
269
+ adversarial re-read of this changelog. The state rules are included at the end of each stylesheet and
270
+ score the same `(0,3,0)` as the `.in-group` block that strips a segment's chrome, so source order
271
+ alone decided: measured, the border stayed 0 (`border: 0` zeroes the width, so a later `border-color`
272
+ paints nothing) but the FILL came back, tinting one segment pink mid-row — the exact thing a group
273
+ exists to prevent. All three states now carry `:not(.in-group)`. Separately `ds-field-group` itself
274
+ read `var(--border-error)`, **a token declared nowhere**, so `[invalid]` fell through to
275
+ `currentColor`; it now resolves through a new `--ds-field-group-border-color-error`, defaulting to
276
+ `--error`, matching every other colour the component publishes.
277
+
278
+ - **`ds-timeline-item`'s marker sits level with its heading.** The node is 28px and the heading's line
279
+ box is 19.6px, and both started at the row's top edge — so the circle's centre sat **4.2px** below the
280
+ heading's and read as floating between the heading and the time beneath it. The node column is now
281
+ pulled up by half the difference, computed from the same `--font-size-s` / `--line-height-base` pair
282
+ the heading uses, so retuning the heading moves the marker with it. Measured across all ten items on
283
+ the docs page: every one now aligns to 0.
284
+
285
+ - **The collapsed `ds-sidenav` stopped squashing its items into a lozenge.** Every item in the rail
286
+ measured **20×40** where the rail gives it 40×40, so the active item's blue tile rendered as a
287
+ vertical bean with the orange rail bar down one side of it — and the alert dot, positioned from the
288
+ item's corner, landed above the glyph's middle instead of beside it. One cause for both:
289
+ `:host(.collapsed)` set `align-items: center`, which stops a flex child stretching, so each projected
290
+ `ds-sidenav-item` and `ds-sidenav-group` shrank to its 20px icon and the `width: 100%` on `.item`
291
+ resolved against *that*. The rail no longer centres its children — `.brand` already centres its own
292
+ contents, which is all that line was there for. Items now measure 39×40 (the rail's 64px less its
293
+ padding and border). The dot is anchored to the GLYPH's top-right corner rather than the tile's, via a
294
+ new `--sidenav-collapsed-glyph`, so it stays put if the rail width ever changes.
295
+ **ACTION** only if you relied on a projected child of a collapsed `ds-sidenav` sizing to its own
296
+ content — a custom element in the rail now stretches to the full 40px column.
297
+
298
+ - **`ds-time-picker`: the time you just picked stopped looking selected.** Hovering a chosen hour or
299
+ minute painted it with the neutral hover fill while it kept the selected white text — white on pale
300
+ grey, unreadable. Pure specificity: `.opt:hover:not(:disabled)` scores (0,3,0) and out-ranked
301
+ `.opt.is-selected` at (0,2,0). It read as a *touch* bug because a touch screen leaves `:hover` on the
302
+ last-tapped cell until something else is tapped, so the minute you had just chosen sat greyed out
303
+ until you looked away. Hover now skips a selected option; an unselected one is unchanged.
304
+
305
+ - **`ds-time-picker` in single mode closes itself, and `Done` is gone from it.** Choosing an hour and a
306
+ minute *is* the completion, so a confirm button underneath it was a second way to say the same thing.
307
+ The panel now closes once both columns have been used **in that opening** — re-opening a field that
308
+ already holds a value asks for both again rather than closing on the first tap, and changing only the
309
+ hour leaves the panel up. `Now` takes the full width of the footer beneath the columns, so it reads as
310
+ one action across the panel rather than a button hugging the right edge. **`mode="range"` is
311
+ untouched**: it keeps `Done`, and picking both halves there does not close anything, because the end
312
+ time still has to be chosen. Internally `ds-time-columns` gained a `partPicked` output — `timeChange`
313
+ carries a whole time and cannot distinguish "chose the same hour again" from "never touched hours".
314
+
315
+ - **`ds-password-rules`: a pending rule is an empty circle, and a rule fades as it passes.** The
316
+ pending glyph was `minus`, which at 14px beside 12px text read as a stray em-dash rather than an
317
+ unticked box; it is now `circle` — the empty counterpart of the check it turns into. A `circle` icon
318
+ joins the set (86 now), available to anything else that wants one. The row also transitions its
319
+ colour over `--duration-base` instead of snapping, because the reader is looking at the field they
320
+ are typing in, so an instant change says a rule flipped but not which one. No reduced-motion guard
321
+ is needed: the duration tokens are already zeroed globally. Row spacing is unchanged at
322
+ `--space-1` — deliberately, after comparing both.
323
+
324
+ - **`ds-password-rules` printed its screen-reader text on screen.** Every row rendered a visible
325
+ "— not met" / "— not yet met" beside the label, because the component used `.visually-hidden` and
326
+ **nothing anywhere defined it**: three other components (`ds-table`, `ds-date-picker`, `ds-stepper`)
327
+ each declared their own byte-identical copy, so the class only ever worked by accident of being in
328
+ the right component. The leaked text is also what made the two-column layout look broken on a phone —
329
+ it ate the column width and wrapped every label onto two lines, which read as a spacing failure and
330
+ was not one. One `visually-hidden` mixin now backs all four. **No API change**; a checklist just
331
+ stops saying "not met" four times in a row. The host also takes `position: relative`, to contain those
332
+ now-hidden rows — so if you absolutely position anything inside `ds-password-rules`, it anchors to the
333
+ component rather than to whatever ancestor used to hold it.
334
+
335
+ - **`ds-otp-input` no longer shows two digits in one cell.** Typing a second character into a cell that
336
+ already held one left `12` sitting in that box while the model had already split it correctly across
337
+ two cells — so what the user read and what the form held disagreed. The distribution was never the
338
+ bug: `[value]` was. Angular diffs a binding against the value *it* last wrote, and the typed-in cell's
339
+ signal is unchanged by the split (`'1'` before and after), so the DOM write was skipped and the
340
+ browser's own `"12"` survived. That branch now writes the element itself, like the other two already
341
+ did. Pasting a full code is unaffected — it cancels the native input, so nothing ever reaches the box.
342
+
343
+ - **A `warning` now shows on the control, and one rule drives all nine bordered fields.** `warning="…"`
344
+ coloured the message and left the box untouched — which is what a phone screenshot caught. On 0.9.1
345
+ six stylesheets styled `.warning` and not one belonged to a bordered field: `ds-field-message`, the
346
+ message this describes, plus `ds-alert`, `ds-banner`, `ds-progress`, `ds-sidenav-footer` and
347
+ `ds-toast`. It now takes a `--warning-text` border. Not `--warning`:
348
+ that is `--yellow-400`, **1.47:1** against a white field where WCAG 1.4.11 asks 3:1 for a component
349
+ boundary, so the obvious mirror of the error recipe would have drawn a border nobody can see;
350
+ `--warning-text` is the first rung of the ramp that clears it, at 4.59:1. Border only, deliberately —
351
+ an error blocks submission and keeps border + tinted fill, so it still reads as the loudest thing in
352
+ a form holding all three.
353
+
354
+ The nine had drifted badly and are now one shared `field-state` mixin keyed off a `data-field-state`
355
+ attribute: five painted the error box as border + fill and four as a border alone;
356
+ **`ds-autocomplete` reached for a `--border-error` token that does not exist**, so an invalid
357
+ autocomplete drew a *near-black* border (`rgb(22,26,40)` — `border-color` falling back to
358
+ `currentColor`) instead of a red one; and the same state was spelled four ways — `.error` on the
359
+ wrapper in `ds-input` and `ds-textarea`, `.error` on the box itself in `ds-select`, `ds-date-picker`,
360
+ `ds-time-picker` and `ds-autocomplete`, `.invalid` on the box in `ds-multi-select`, and
361
+ `:host(.invalid)` in `ds-color-picker` and `ds-otp-input`. **What changes visually:**
362
+ `ds-autocomplete` finally shows red, and `ds-multi-select`, `ds-color-picker` and `ds-otp-input` gain
363
+ the tinted fill their five siblings already had. A sixth thing moves that is easy to miss:
364
+ `ds-autocomplete`, `ds-multi-select`, `ds-date-picker`, `ds-time-picker` and `ds-color-picker` had no
365
+ error FOCUS ring at all and kept their ordinary accent one while invalid — the shared mixin gives all
366
+ nine `--ds-field-focus-shadow-error`. Only `ds-input`, `ds-select`, `ds-textarea` and `ds-otp-input`
367
+ carry a per-component override for it, so retuning the other five means moving the family token,
368
+ which moves those four with it. One precedence moved with the shared rule: the ladder
369
+ is now error → warning → success, so a `ds-input` carrying both `[success]="true"` and a `warning`
370
+ string paints the warning, where it used to paint the success and ignore the warning entirely. Every
371
+ per-component override token that shipped in 0.7.x (`--ds-input-bg-color-error`,
372
+ `--ds-select-focus-shadow-error`, …) still wins — the mixin takes them as arguments rather than
373
+ replacing them with the family token. The `.error` class is **still emitted** — on the wrapper by
374
+ `ds-input` and `ds-textarea`, on the box by `ds-select`, `ds-date-picker`, `ds-time-picker` and
375
+ `ds-autocomplete` — and `.success` by `ds-input`, the only control with a success state. A selector of
376
+ yours still matches, but the library no longer paints through them, so a rule written to stack on top
377
+ of the DS one now stands alone.
378
+
379
+ **DELETE-LIST:** the dead `.invalid` host class on `ds-color-picker` and `ds-otp-input` is gone, since
380
+ nothing styled it any more; if you selected it from outside, use `[data-field-state="error"]`.
381
+ `ds-multi-select` loses the same class from its internal `.field-trigger` — it was never on the host,
382
+ so `ds-multi-select.invalid` never matched from outside anyway. **The attribute is on those nine and
383
+ only those nine.** `ds-checkbox`, `ds-radio`, `ds-radio-group` and `ds-switch` do not carry it: they
384
+ have no bordered box, they signal through `aria-invalid` and `ds-field-message`, and their paint is
385
+ untouched. Nor does `ds-slider`, which keeps its own `:host(.invalid)` binding and still colours its
386
+ fill and thumb `--error` — so a selector written against `[data-field-state]` will not reach any of
387
+ the five.
388
+
389
+ - **Binding `error` now tints the control, not just the message.** Every field that takes an `error`
390
+ string — all 14, via the shared `resolveFieldMessage` — put a red message under a box that stayed
391
+ neutral grey, because the invalid state was computed from `[invalid]` and from validator `errors` but
392
+ not from an explicit `error`. That contradicted the input's own contract ("binding it says the
393
+ consumer has already decided this field is in error") and it is what a phone screenshot caught: a red
394
+ line under an untouched field. `error="…"` now drives the red border, the tinted fill, the error focus
395
+ ring and `aria-invalid`, exactly as `[invalid]="true"` always did — the border and fill on the nine
396
+ bordered fields, and `aria-invalid` plus the message state on the other five, which have no box to
397
+ paint. **If you were binding both**
398
+ (`[invalid]="hasError" error="…"`) nothing changes. **If you were binding `error` alone and relying on
399
+ the box staying neutral**, that is now the error box — drop to `warning` for an advisory message, or
400
+ bind `hint` and leave `error` empty.
401
+
402
+ - **A field inside `ds-field-group` no longer pins its value to the top of the row.** Found by Stas
403
+ testing the docs on a phone, and it affected **every segment except `ds-button`**: the value sat
404
+ against the top edge instead of the vertical centre — **5px out at `sm`, 9px at `md`, 13px at `lg`**,
405
+ measured in one sitting against the 21.6px content height the box fell back to on the 32/40/48 row
406
+ scale. The group stretches its segments to one row height, but a segment's host is a block, so the
407
+ `height: 100%` each one set on its bordered box resolved against `auto` — the box kept that content
408
+ height, and the value with it. `ds-button`
409
+ escaped the defect only because its host already declared `display: inline-flex`; its block was
410
+ rewritten with the rest all the same, to `flex: 1; height: auto`. Every segment now centres at all
411
+ three sizes. The six `.in-group` blocks — identical declaration for declaration apart from the box's
412
+ class name, which is
413
+ why the defect sat in five of them at once — are now one `field-group-segment` mixin, so the next
414
+ change to segment chrome cannot land in some of them and miss the rest.
415
+
416
+ - **`components.md` had drifted, and it ships inside the package.** The file `tools/build-schematics.mjs`
417
+ copies into `dist/ds/` for a consumer's own agents to read was still documenting the API and token names
418
+ of two renames ago: **46 of the 92 `--ds-*` tokens it named no longer exist** (`--ds-button-fg`,
419
+ `--ds-sidenav-item-bg-hover`, the whole `--ds-pagehdr-*` family, …), `ds-button` was described with its
420
+ pre-2026-06 single `variant` axis (`'primary' | 'secondary' | 'tertiary' | …`) instead of
421
+ `color` × `variant`, and the topbar section documented a `--ds-topbar-margin-b` that **has never
422
+ existed** — telling readers the topbar owns the gap below it and that pages must not add their own.
423
+ Every name in the body is now the shipped one, verified against `src/lib` rather than assumed, and the
424
+ two paragraphs are rewritten from the components' actual API. The preamble of its `## Components`
425
+ section still carries the older warning that the `ds-button` section below is out of date — which now
426
+ contradicts the corrected section, and is itself wrong twice over: it calls `--ds-button-bg-color` a
427
+ dead pre-rename name when that is the shipped token this very release tells you to set. Being cleared
428
+ separately.
429
+
430
+ - **An outlined button no longer paints its own white background.** `ds-button variant="outline"`,
431
+ `ds-icon-button variant="outlined"` and the outlined half of `ds-split-button` defaulted their fill to
432
+ `--surface-default`, which is invisible on a white page and wrong everywhere else: on a tinted card, a
433
+ table toolbar or an alert the button read as a white sticker laid over the surface instead of a control
434
+ drawn on it. The fill is now `transparent`, which is what Material 3 and Bootstrap both specify for this
435
+ variant. Hover still tints — `--c-subtitle` on `ds-button`, `--surface-secondary` on the other two, all
436
+ opaque. On `ds-button` and `ds-icon-button` the disabled state stays transparent as well, because mixing
437
+ a transparent fill toward the disabled surface would have produced a 72%-alpha box, so the border and
438
+ label carry it, as they do on ghost; a disabled `ds-split-button` is the exception and still paints
439
+ `--surface-muted`, which this change did not reach. **If a button of yours sits on a photo, a gradient
440
+ or any busy ground and relied on that white fill**, set it back per instance:
441
+ `--ds-button-bg-color: var(--surface-default)`, or `--ds-icon-button-bg-color` /
442
+ `--ds-split-button-outline-bg-color` for the other two.
443
+
444
+ - **Everything focusable now gets the DS focus ring, not the browser's black outline.** The library
445
+ styled focus on the elements that remembered to — 42 of 81 component stylesheets, and only 35 of those
446
+ with `:focus-visible` — and everything else
447
+ fell through to `outline: auto`, which Chrome paints black: the close button inside `ds-alert`,
448
+ `ds-banner` and `ds-drawer`, a link in projected content, and any plain `<button>` an app writes itself.
449
+ One base rule now covers them: `:where(:focus-visible)` sets `outline: none` and resolves
450
+ `--ds-control-focus-shadow`, written at **zero specificity** so every component rule and every app rule
451
+ still out-ranks it. The `data-focus` switch is unaffected — all five modes (default, `ring`, `field`,
452
+ `edge`, `outline`) behave as before, the last replacing the shadow with a real outline at a higher
453
+ specificity. **If you deliberately suppressed a focus ring** by leaving an element unstyled, it will now
454
+ show one; give that element `box-shadow: none` explicitly. Note the rule also drops the outline such an
455
+ element used to get from the browser, so if an `outline` was what you wanted there, declare it yourself.
456
+
457
+ - **A disabled `ds-button` / `ds-icon-button` now reads as disabled on a COLOURED accent.** One label recipe
458
+ for every variant — `oklch(from accent 70% 0.035 h)` — replacing the 58% default, and on `ds-button` the
459
+ 52% overrides that tonal and outline carried (`ds-icon-button` only ever had the base). Those sat right
460
+ where a saturated accent already is, so the disabled label
461
+ differed from the live one by **1.16–1.60:1** on four of the five variants; only `color="neutral"` was
462
+ safe, because its enabled label is nearly black. Now **2.40–2.71:1** on the coloured variants that
463
+ were failing, and higher still on `neutral`, which reaches 6.46:1.
464
+ Measured, not guessed: the matrix is in `presentations/disabled-recipe.html` — 5 variants x 3 colours
465
+ x rest/hover/active/disabled in light, and a narrower primary-only sweep in dark. **The trade,
466
+ stated:** the disabled label is fainter
467
+ against its own background than it was — 2.1–2.7:1 where the old recipe gave 3.4–5.2 — which is the point,
468
+ and disabled text is exempt from the WCAG contrast floor. **Override per component if you disagree:**
469
+ `--ds-button-label-color-disabled` / `--ds-icon-button-icon-color-disabled` still win. **And delete this
470
+ if you have it:** an override retuning `--opacity-muted` on `ds-button` or `ds-icon-button` never did
471
+ anything — neither component reads that token.
472
+
473
+ - **A disabled control was dimmed twice, and had nearly disappeared.** Five places each set
474
+ `--text-disabled` AND `opacity: 0.6` on top of it: the closed triggers of `ds-select`,
475
+ `ds-date-picker` and `ds-time-picker`, plus two genuine rows — `ds-menu-item` and the shared dropdown
476
+ option. Measured in the light theme: that lands at **1.68:1** against the
477
+ surface, where the colour alone gives **2.53:1** and an enabled control sits at 17.32:1 — so the
478
+ state was
479
+ never in danger of being missed, the text was. The opacity is gone from those five; the colour carries
480
+ the state, which is what it was chosen for. Where opacity IS the only signal — a disabled calendar day,
481
+ `ds-toggle-button` — it now reads `--opacity-disabled` (0.5) instead of `--opacity-muted` (0.6), the
482
+ token named for the job. **If you retuned `--opacity-muted` to compensate**, drop it: it is a
483
+ de-emphasis level for hints and secondary text, and it no longer carries any disabled state.
484
+
485
+ - **`ds-table` lost the sort indicator when a host answered a cleared sort with its own default.** Third
486
+ click clears a column, the host replies with its default sort, the rows come back ordered by it — and
487
+ every header said `aria-sort="none"`. Not the table's arithmetic: Angular writes an input only when the
488
+ bound EXPRESSION changed, diffing against the last value it wrote, which an internal `.set()` never
489
+ updates. So the half of the default that equalled what was last bound was skipped — a host defaulting
490
+ to `owner`/`desc` had its `desc` dropped and stayed at `null`, while a host defaulting to `asc` was
491
+ restored. That is exactly why the same three clicks worked on one screen and not another. The marked
492
+ state is now a `linkedSignal` over BOTH inputs, so a change in either re-seeds the pair and the
493
+ direction arrives with the key. **Verified against both reported screens** by replaying them through
494
+ Angular's real signal graph with the binding diff modelled: the old shape fails the first and passes
495
+ the second, the new one passes both. A table that binds neither input is unaffected.
496
+
497
+ - **`ds-table` painted its empty state while the first read was still in flight.** Only
498
+ `loading="skeleton"` suppressed the empty row, and `overlay` is the mode a list uses on every read
499
+ after the first — so a zero-row reload showed "No records match your filters" or a whole
500
+ `ds-empty-state` CTA underneath the spinner. The empty row is a claim about the data ("there are
501
+ none"), so it is now withheld whenever `loading` is anything but `false`. **You can delete the guard
502
+ you wrote for this** — and check the ones you did not write: of one consumer's 14 overlay-loading
503
+ tables, 9 were shipping the sentence during a load, because branching failure-vs-empty looks complete
504
+ while saying nothing about loading. Note this closes the door on the `[empty]` slot during a load
505
+ rather than opening another one: there is no `loading` value that renders it, so copy you want a
506
+ reader to see WHILE a load runs has to come from your own page, above or around the table.
507
+
508
+ - **Releasing the mouse on the backdrop closed `ds-modal` and `ds-bottom-sheet`, even when the press
509
+ started inside the dialog.** Select a sentence in the body and let go past the edge, or overshoot with
510
+ a slider, and the dialog vanished — reported by a consumer as "not a click, the mouse-UP". The cause is
511
+ in the DOM shape: those backdrops WRAP their dialog, and a browser fires `click` at the nearest common
512
+ ancestor of the press and the release, which for that gesture IS the backdrop — so the
513
+ `target === currentTarget` guard let it through. Dismissal now tracks the press and fires only when
514
+ both the press and the release land on the backdrop itself, which is how the CDK has always guarded
515
+ its own outside-click. `ds-drawer` and the `ModalService` confirm were never affected (their scrim is
516
+ a SIBLING of the panel, so the common ancestor is a third element) and are unchanged — all four were
517
+ re-checked. **If a test of yours dismisses a dialog with `backdropEl.click()`**, it now needs
518
+ `pointerdown` + `pointerup` on the backdrop, both with the primary button; a real mouse or touch has
519
+ always sent both. One side effect on `ds-bottom-sheet`: the sheet no longer stops click propagation
520
+ (the guard it needed for the old `click` listener is gone with it), so a click inside the sheet now
521
+ reaches an ancestor handler of yours, the sheet being rendered inline rather than portaled.
522
+
523
+ - **`ds-filter-bar` clipped the focus ring of its first and last inline filter.** The measured row was
524
+ `overflow: hidden` and each slot is sized to exactly the width `dsFilterItem` declared, so the row's
525
+ box starts flush with the first control — and the focus ring is an OUTSET shadow (3px on fields, 4px
526
+ on controls). Interior filters were fine, living in the 12px gap; the outer two had their ring cut off
527
+ as you tabbed onto them. Now `overflow: clip` with a 4px clip margin: the shadow bleeds, `clip` still
528
+ forbids scrolling, and the width the collapse arithmetic reads is unchanged. Not fixable from an app —
529
+ the row is internal, and padding it from outside would change that measured width.
530
+
531
+ - **A single-select `ds-autocomplete` kept the text you typed to filter, and since 0.9.0 kept it
532
+ INVISIBLY.** The filter input collapses to zero width once a chosen label is on show, so leftover
533
+ query text disappeared from view while it went on narrowing the list: reopening a settled picker
534
+ offered one option out of four, with nothing on screen to say why and no way to clear it. Before
535
+ 0.9.0 the same text simply sat beside the label instead. It is now cleared whenever the panel closes
536
+ over a displayed label — which covers both picking an option and dismissing after typing over a
537
+ settled value. Multi-select is deliberately unchanged: its input never collapses, so the text stays
538
+ visible and useful for the next pick. Nothing to do on your side; `query` was component-private, so
539
+ this was not fixable from an app.
540
+
541
+ - **Four defects in `ds-sidenav`'s brand row.** A `logoLetter` set without a `brand` string rendered
542
+ **nothing at all** — if you worked around that by passing a dummy `brand`, you can drop it now. A
543
+ brand starting with an emoji or a rarer CJK glyph painted as tofu in the letter-mark. The mark had
544
+ no `aria-hidden`, so a screen reader announced the glyph and then the wordmark ("A MyAdmin"). And a
545
+ logo projected into `[brand]` had no size constraint, so an oversized one set the rail's height —
546
+ `--ds-sidenav-brand-max-height` now caps it, defaulting to `none` so nothing moves until you set it.
547
+
548
+ - **`env(safe-area-inset-*)` needs one line from YOUR app, and nothing here said so.** The insets read
549
+ 0 until the host document sets `viewport-fit=cover` in its viewport meta — a notched device alone is
550
+ not enough, and a library cannot set it for you. So `ds-auth-layout`'s notch padding and
551
+ `ds-bottom-sheet`'s home-indicator padding have been inert in every app that never added it. Both
552
+ component pages now say so and show the tag, and the docs site sets it, so the behaviour can be seen
553
+ rather than described. **One real fix rode along:** `ds-bottom-sheet` was calling
554
+ `env(safe-area-inset-bottom)` with no fallback inside a `padding` shorthand, and an engine that does
555
+ not know the variable throws out the whole declaration — taking the sheet's horizontal padding with
556
+ it. It now reads `env(safe-area-inset-bottom, 0px)`, which is what `ds-auth-layout` — the only other
557
+ component using these insets — already did on all four of its.
558
+
559
+ ### Changed
560
+
561
+ - **`avatarTint` switches from OKLCH to `hsl(H 50% 62%)` with white initials, always.** The seeded
562
+ tints read as dull, and every set of initials came out black. The auto-contrast was not the fault:
563
+ measured across the hue circle, the old `oklch(62% 0.14 h)` put every hue's luminance between 0.218
564
+ and 0.271 against a 0.179 black/white crossover, so black was genuinely the better pick every time
565
+ (5.4–6.5:1) — the switch was right, the lightness never let it switch. The new recipe is pinkmoon's
566
+ own, adopted deliberately: HSL lightness is not perceptually even, so yellows land far lighter than
567
+ blues, and that unevenness is exactly what makes the row read as bright.
568
+ **It is a knowing trade against contrast.** White on the lighter hues measures as little as
569
+ **1.65:1**, under the 4.5:1 WCAG AA asks of text — verified across the full 20–300° range, where all
570
+ 29 sampled hues fall short. Suitable where the avatar sits beside a name that is written out anyway;
571
+ where the initials are the only identifier, pass your own `lightness` / `foreground`.
572
+ **API:** the `chroma` option is gone, replaced by `saturation` (HSL %, default 50). `lightness` keeps
573
+ its name and its default of 62 but now means **HSL** lightness, so an existing numeric override will
574
+ land somewhere different — re-pick it rather than assuming it carried over. `foreground` now defaults
575
+ to `#fff` instead of auto-choosing; pass it explicitly to get anything else. `avoidHues` is unchanged.
576
+
577
+ - **`ds-input`'s `floating` label is removed, with no replacement.** It only ever did half the job: the
578
+ label was drawn inside a taller control, but it never moved out of the field on focus — the animation
579
+ from inside-the-box to above-it *is* the pattern, and without it an empty field reads as a
580
+ permanently mislabelled one rather than a floating-label one. Nobody had asked for it, and finishing
581
+ it is a real piece of motion work, so it goes. **Migration is deleting the attribute:**
582
+ `[floating]="true"` → nothing, and the label renders above the field like every other field in the
583
+ library. One thing to re-check when you do: a floating input stood at `--hit-touch` (48px at default
584
+ density) and now takes the ordinary size scale (`--field-h-md` → `--hit-cozy`, 40px at default
585
+ density), so a row whose height was built around one moves. Gone with it are the five internal
586
+ tokens only this variant read
587
+ (`--field-h-floating`, `--field-floating-label-fs`, `--field-floating-label-lh`,
588
+ `--field-floating-label-top`, `--field-floating-pad-t`) — overriding them is now inert.
589
+ `--ds-elevation-floating` is a different token for toasts and is untouched.
590
+
591
+ - **`ds-table`'s `sortKey` and `sortDir` are an `input` + `output` pair instead of a `model`** — the
592
+ mechanism behind the indicator fix above, because a `model` cannot tell a host's write apart from the
593
+ table's own. **Templates are unaffected:** `[(sortKey)]` still works (`sortKeyChange` and
594
+ `sortDirChange` are emitted), one-way `[sortKey]` with `(sortChange)` still works, and a static
595
+ `sortKey="project"` still works. What breaks is reaching into the component in TypeScript:
596
+ `table.sortKey.set(…)` no longer exists — nor `sortDir.set(…)` — so drive it from your own state and
597
+ bind it, which is what every server-paged list already does. Reading `table.sortKey()` still works and
598
+ now returns what the host bound; the marked state the header renders is internal. **One emission rule
599
+ moved with it:** both `…Change` outputs now fire on EVERY sort click, where a `model` suppressed the
600
+ emit when the value was unchanged. `[(sortKey)]` is unaffected — it rebinds the same value — but a
601
+ `(sortKeyChange)="reload()"` handler now also runs when only the DIRECTION changed. Listen to
602
+ `(sortChange)` instead, which carries both halves once.
603
+
604
+ - **`ds-modal` / `ds-modal-card`: `error: boolean` → `status: DsStatus`.** A boolean could not express
605
+ a warning or an info dialog, and the rest of the library settled on the `DsStatus` vocabulary in
606
+ 0.9.0. **Migration is one attribute:** `[error]="true"` → `status="error"`, and a computed
607
+ `[error]="isDangerous"` → `[status]="isDangerous && 'error'"`, since the input takes `false` and
608
+ `undefined` as "no status" — the longer `? 'error' : null` ternary works too. Unset stays neutral,
609
+ so a dialog that never used `error` looks identical. **What you gain beyond the rename:** a status now
610
+ drives the icon-badge tint, the title colour, a DEFAULT icon and the ARIA role — the same four
611
+ things `ds-alert`'s variant drives, so a status dialog and a status alert on one screen cannot
612
+ disagree. The default icon matters: a tint alone signals by colour only, which fails the
613
+ don't-rely-on-colour rule. `icon` still overrides the pick, and `error`/`warning` default the
614
+ dialog to `alertdialog`. `dialogRole` lives on `ds-modal-card` only — it is now
615
+ `'dialog' | 'alertdialog' | null`, defaulting to `null` rather than `'dialog'` so "unset" is
616
+ distinguishable from a deliberate `dialog`, and an explicit value still wins. `ds-modal` has no such
617
+ input, so `<ds-modal status="error">` becomes an `alertdialog` with nothing to override it. What
618
+ renders is unchanged unless you set a status. Three tokens come with the tints:
619
+ `--ds-modal-title-text-color-warning`, `-success` and `-info`, joining the `-error` that already
620
+ existed. **One thing rides along that no attribute of yours controls:** a
621
+ `ModalService.confirm({ tone: 'error' })` passes `status="error"` down internally, and a status now
622
+ supplies a default icon — so a destructive confirm that never set `options.icon` opens with a red
623
+ error badge where it previously had none. Pass `icon` to choose a different glyph; there is no input
624
+ that turns the badge back off.
625
+
626
+ - **Chips cap by width by default.** `maxVisibleChips` on `ds-autocomplete` and `ds-multi-select`
627
+ now defaults to `"fit"` instead of "show everything": the trigger keeps as many chips as it is
628
+ wide and collapses the rest into "+N more". A trigger that grew a line per selection was pushing
629
+ the rest of the form down the page. **To keep the old behaviour, bind `[maxVisibleChips]="null"`.**
630
+ Two more things moved with the default, and both are easy to miss. A trigger in any measuring mode is
631
+ now single-line (`flex-wrap: nowrap`), and its chips are held to one line each and clipped rather than
632
+ wrapped — so a chip carrying more than a short label gets squeezed, where `null` still wraps the row.
633
+ And **`[maxVisibleChips]="0"` has inverted**: it used to mean "show them all" and now means "show
634
+ none", putting the whole selection behind `+N more`. If you have a `0` anywhere, it was almost
635
+ certainly written for the old meaning; `null` is what that meant.
636
+
637
+ - **`size` is now `DsSize | null` on the fourteen controls that resolve `DS_CONFIG.control.size`**, so
638
+ an unbound `size` can fall through to it. `ds-drawer` and `ds-spinner` also take a `size` and are NOT
639
+ among them — theirs stays a non-null `DsSize` defaulting to `'md'`, so a grep for `DsSize` finds
640
+ sixteen controls and only fourteen changed. **Nothing changes in a template** — `size="sm"` binds as
641
+ before and an unbound control still renders `md`. **What changes is reading it back:** `size()` now
642
+ returns `null` when nothing was bound, where it used to return `'md'`. The same is true of
643
+ `ds-card`'s `elevation` and `padding`, `ds-icon`'s `size`, `ds-badge`'s `withDot`, `ds-table`'s
644
+ `bordered` and `stickyScrollbar`, `dividers` on both modal components, `dialogRole` on
645
+ `ds-modal-card`, `brand` and `logoLetter` on `ds-sidenav` and `ds-auth-layout`, and `tagline` on the
646
+ auth layout — all of them now answer `null` for "nothing bound"
647
+ rather than the old default. **There is no public accessor for the resolved value**, and this is the
648
+ awkward part of the release: each component holds a `sizeResolved()` (or `elevationResolved()`,
649
+ `withDotResolved()`, …) but declares it `protected`, so reading it from a host, a test or a
650
+ `viewChild` does not compile. `ds-field-group` is the single exception, where `sizeResolved` is
651
+ public. Until that is opened up, a host that needs to know what a control is rendering at should keep
652
+ the value it bound, or resolve `DS_CONFIG.control.size` itself — the fallbacks are unchanged, but
653
+ they are not all `false`: `'md'` for `size`, `'flat'` for `elevation`, `16` for the icon size,
654
+ `false` for `bordered` / `stickyScrollbar` / `withDot`, **`true`** for `dividers`, `''` for the brand
655
+ strings, and the card's own padding when `padding` is unset. **If you implement
656
+ `DsFieldGroupContext`**, its member is now
657
+ `sizeResolved` rather than `size`, for the same reason: a segment must not have to resolve the
658
+ group's size a second time.
659
+
660
+ - **`[data-density="ultra-compact"]` now compresses surface padding too** — `--ds-container-pad`,
661
+ the inner padding `ds-card` and `ds-stat` share, drops from 24px to 16px in that tier only.
662
+ Everything else is untouched: the default and the other three tiers still resolve to 24px. It was
663
+ the one padding the tier missed — it already compressed field padding and table cells, so a card
664
+ kept its full 24px frame while its own cells halved. **If you want the old 24px inside an
665
+ ultra-compact container**, re-declare `--ds-container-pad: var(--space-6)` on it. For a value
666
+ between the rungs — 20px, say — set that one token at `:root`; both components default to it, which
667
+ is why neither `ds-card` nor `ds-stat` should be pinned on its own.
668
+
669
+ - **`ds-tabs` `urlParam` now SLUGS a tab's label instead of using it raw.** A tab with no `value` used
670
+ to put its display string straight into the address — `?tab=License%20Verification%20Status`. It is now
671
+ kebab-cased and lowercased with diacritics dropped: `?tab=license-verification-status`. **If you
672
+ adopted `urlParam` in 0.9.0 with tabs that declare no `value`, your existing links change** — an old
673
+ one no longer matches and lands on the first tab, which is what a stale bookmark has always done.
674
+ Declare `value` on each tab to pin the names for good: a slug is still derived from copy, so renaming a
675
+ tab still moves the link. What `tabClosed` emits is unchanged — still the raw label.
676
+
677
+ - **`ds-auth-layout`'s projected `[brand]` slot no longer forces `width: auto`.** It shipped in 0.9.0
678
+ alongside the slot's `max-height`, but at `(0,2,0)` it out-ranks a width the consumer set on their
679
+ own logo, and with the default `max-height: none` it never did anything: an `<img>` with no CSS
680
+ width already keeps its ratio under `max-height`. If you opted into the max-height AND set an
681
+ explicit width on your logo, add `width: auto` yourself to keep the old scaling.
682
+
683
+ - **The chips of both pickers now render inside a `<span class="chip-row">`** rather than directly
684
+ in the trigger — the element the width measurement needs. **On `[maxVisibleChips]="null"` it is a
685
+ wrapper and nothing more**: `display: contents`, so it adds no box and the chips stay flex items of
686
+ the trigger, identical in spacing, wrapping and height. In the measuring modes — which includes the
687
+ new default — the row becomes a `nowrap` flex box that clips, which is how the cap is enforced.
688
+ Either way, what breaks is a CSS override that walks the structure:
689
+ `.autocomplete-trigger > ds-tag`, `:nth-child` written against the trigger's children, or
690
+ `ds-tag + .autocomplete-input` adjacency — the chips are no longer siblings of the filter input,
691
+ the addon slots or the chevron. Drop the combinator or insert `.chip-row`. Multi-select's trigger is
692
+ `.field-trigger`, not `.trigger`, if you are rewriting a selector against it. Chips carry `data-chip`
693
+ and the marker `data-chip-overflow`; the measurement finds them that way, so leave them in place.
694
+
695
+ - **If you EXTEND a DS component, this is the release that will break you.** `npm run class-surface`
696
+ against 0.9.1 reports **30 exported classes whose member surface grew** — among them `ButtonComponent`,
697
+ `TableComponent`, `ModalComponent`, `SearchComponent`, `AvatarComponent`, `IconComponent`, both
698
+ pickers, every bordered field that gained `controlState`, and every control that gained
699
+ `sizeResolved`. A subclass declaring any of those names now fails with TS4114. **Four classes also
700
+ LOST members**, which is the case a subclass notices differently — an `override` that now overrides
701
+ nothing: `ModalComponent.error` and `.onBackdrop`, `ModalCardComponent.error`,
702
+ `BottomSheetComponent.stop` and `InputComponent.floating`. Subclassing a DS component remains
703
+ unsupported, and this is the third release running where it broke someone, so it is stated in full
704
+ rather than by example. **Two kinds of break the report cannot see**, so check them by hand:
705
+ a member whose SIGNATURE changed keeps its name — `TableComponent.exporting` and `.exportStatus`
706
+ are still there, but as public readonly signals rather than the protected writables a subclass
707
+ could `.set()` — and a plain `private pending: … = null` is not a field the parser recognises, which
708
+ is how `SearchComponent`'s `pending` and `pushed` sit outside its reported seven.
709
+
710
+ ## 0.9.1 — 2026-08-10
711
+
712
+ ### Added
713
+
714
+ - **The token and component reference now documents every public token and prop** — 41 were
715
+ shipping with a name, a type and no description: 10 `--ds-*` tokens (the whole
716
+ `--ds-password-rules-*` set among them, plus `--ds-multi-select-panel-bg-color` and
717
+ `--ds-menu-item-radius`) and 31 inputs and outputs across `ds-calendar-day`, `ds-time-columns`,
718
+ `ds-field-message`, `ds-divider`, `ds-sidenav-footer` and the three layout primitives. **Three of
719
+ them were guessable wrong**, so check yours if you use them: `ds-time-columns` `value` is always
720
+ `HH:mm` in 24h and `format` changes only the DISPLAY, so a 12h picker still emits 24h;
721
+ `minTime`/`maxTime` disable the out-of-range rows rather than removing them, so the columns keep
722
+ their height as a bound moves; and `ds-calendar-day` `tabIndex` is a roving tabindex (one cell at
723
+ 0, the rest at -1), not a tab position you set per day. No behaviour changed — only what the
724
+ reference tells you.
725
+
726
+ ### Fixed
727
+
728
+ - **The changelog page on the docs site was rendering with browser defaults.** Its markdown styles
729
+ were scoped by emulated encapsulation, which stamps its attribute on the container but not on the
730
+ nodes the markdown renderer produces — so every rule in that block matched nothing: measured
731
+ border-top 0px and margin-top 0px on the version headings, and `h3` white instead of
732
+ `--text-secondary`. Docs-site only, nothing in the package.
733
+
734
+ ### Changed
735
+
736
+ - **`migrations/<version>.json` now carries the delete-list, so an upgrade tool can act on it.**
737
+ Each version's manifest gains `DELETE-LIST: if you have <X> -> <why it can go>` entries — 21 of
738
+ them for 0.9.0 — naming the workarounds that release made unnecessary, from the
739
+ `.button.button.button` triple-class to hand-binding `[value]`/`(valueChange)` on every field of a
740
+ signal form. They existed for 0.9.0 but only in a prose file the tooling does not read, so nothing
741
+ applied them. **Nothing here is required**: skipping it leaves working code that is merely
742
+ redundant. The same table is in this file under 0.9.0 if you would rather read than run.
743
+ `migrations/unreleased/README.md` no longer ships — it duplicated the manifest and had already gone
744
+ stale inside one release.
745
+
11
746
  ## 0.9.0 — 2026-08-10
12
747
 
748
+ ### What you can now DELETE
749
+
750
+ The half a release note usually leaves out. Two dogfooding audits (mm-ecm 2026-08-06, mm-broker
751
+ 2026-08-07) read consumer stylesheets as a record of what this library made them write, and both
752
+ found the same thing: **most of the workarounds were written against hooks that already existed** —
753
+ the consumer had no signal that anything had been tokenised since. That is a failure of these notes,
754
+ not of the consumer. None of this is required; skipping it leaves working code that is merely
755
+ redundant.
756
+
757
+ | If you have | Delete it, because |
758
+ | --- | --- |
759
+ | `.button.button.button { … }` or rules against `.v-outline` / `.c-secondary` | `ds-button` reflects `[data-variant]` and `[data-color]` on the HOST. Use `ds-button[data-variant="outline"]` |
760
+ | `--radius-sm: 0` to square a checkbox | `--ds-checkbox-radius` |
761
+ | `.title.title { font-size }` inside a modal | `--ds-modal-title-font-size` |
762
+ | Pagination label type overrides | `--ds-pagination-label-*` |
763
+ | `.size { display: none }` on a pager | `[showPageSize]="false"` — and it is now forwarded through `ds-table` too |
764
+ | `.actions:empty { display: none }` on a modal | The library already ships it |
765
+ | `--ds-modal-divider: transparent`, plus whatever you rewrote the modal padding to afterwards | `[dividers]="false"` — it drops the rules *and* the padding that existed to clear them |
766
+ | A defensive hover rule on the selected dropdown row | The `:not(.is-selected)` branch already handles it |
767
+ | `ds-menu-divider { padding: 0 }` | `--ds-menu-divider-spacing`, which already defaults to 0 |
768
+ | A dozen scattered `--ds-*-radius: 0` | For a fully square brand, four lines: `--radius-sm/md/lg/xl: 0` (leave `--radius-pill`). Measured — the three ROLES alone leave options, clear buttons and dropdown panels rounded; they are the tool for squaring one family and keeping another. Worked example on the Theming page |
769
+ | A global rule squaring `.ds-overlay-pane` | Radius and elevation roles now travel onto portaled panes when the host overrides them |
770
+ | Absolutely positioning a search glyph over an autocomplete, or hiding `.autocomplete-chevron` | `dsAutocompletePrefix` and `[showChevron]="false"` |
771
+ | Querying the autocomplete's inner `<input>` and dispatching a synthetic `input` event to clear it | `clear()` |
772
+ | A hand-built KPI tile whose value is a badge | `ds-stat` takes a projected `[dsStatValue]` |
773
+ | A pinned `--ds-search-height` (or any sibling) to get a shorter control row | `density="compact"` on the container — every field control is 32px there, measured |
774
+ | A hand-rolled `.scrim` + `.panel` dialog, written because the modal header could not hold a badge or a second line | `ds-modal` projects `[title-badge]` and takes a `subtitle`. You get back the focus trap, focus restore, the scroll lock, Escape and the footer |
775
+ | `[value]="f.x().value()" (valueChange)="f.x().value.set($event)"` on every field of a signal form | `[formField]="f.x"` — the control implements the contract already |
776
+ | `white-space: normal` forced onto a badge in a table cell | `--ds-badge-white-space` |
777
+ | `::ng-deep .card { height: 100% }` for equal-height cards | The card's box fills a stretched host on its own |
778
+ | `!important` on `ds-table` cell padding under `density="compact"` | Compact no longer out-specifies the padding hooks |
779
+ | A wrapper around `ds-table` for sort/range announcements, keyboard column resize, or a header filter the checklist cannot express | All three ship: the live region, the `role="separator"` handle, and `dsHeaderFilter` |
780
+
781
+ **To sweep for the rest:** grep your styles for `::ng-deep`, `!important` and any selector naming a
782
+ DS internal class (`.button`, `.trigger`, `.option`, `.modal`). Each hit is either a row above or a
783
+ genuine gap worth reporting.
784
+
13
785
  ### Changed (breaking, behaviour)
14
786
 
787
+ - **If you EXTEND a DS component, this release collides with your subclass.** Sixteen exported
788
+ classes gained members, so a subclass declaring the same name stops the build: `TS4114` wants
789
+ `override`, `TS2415` fires on a redeclared private, `TS2416` on a differing signature. Not
790
+ hypothetical — a consumer migrating to 0.8.0 hit exactly this on three `TableComponent` members.
791
+ **`TableComponent` is by far the largest**: `lazy`, `lazyLoad`, `showLabel`, `showPageSize`,
792
+ `filterMode`, `columnFilterOptions`, `sortAnnouncement`, `rangeAnnouncement` and `exportFailed`,
793
+ plus a dozen protected members. **And one signature changed rather than appeared:** `isStriped()`
794
+ now takes an ABSOLUTE row index instead of a window-relative one, so a subclass that overrode it
795
+ stripes the wrong rows rather than failing to compile. Elsewhere: both control-value-accessor
796
+ bases gained `hidden` and `focus()` (inherited by every field control); `ds-input` / `ds-textarea`
797
+ gained `readonlyBinding`, `isReadOnly`, `minLength`, `pattern`; `ds-modal` and `ds-modal-card`
798
+ gained `subtitle` and `dividers`; `ds-autocomplete` gained `maxVisibleChips`, `showChevron` and
799
+ `clear()`. One member was also REMOVED: `TableComponent`'s private `distinctValuesOf()`, now `optionsFor()`, which prefers the new `columnFilterOptions` input. The full per-class list is in `migrations/0.9.0.json`. **Using the `<ds-…>` elements in
800
+ a template needs no change** — this only reaches you through `extends`.
801
+
15
802
  - **`ds-table` `sortMode` and `filterMode` default to `'server'`, were `'client'`.** Server-paged is the
16
803
  normal case, and there the old default was actively wrong: the table sorted the current page, so the
17
804
  rows looked sorted and were not — a dev warning existed only to say so. An undeclared table now emits
@@ -24,8 +811,11 @@ While the package is on `0.x`, minor releases may contain breaking changes.
24
811
  - **The `ds-select` / `ds-multi-select` dropdown panel has a 12px corner, was 8px.** It was the one panel
25
812
  outside the radius role layer — modal, popover, date picker, time picker, autocomplete, bottom sheet, card,
26
813
  stat and page footer all resolve `--ds-radius-panel` — so it disagreed with its siblings by 4px and could
27
- not be retuned through the role consumers are told to use. Restore with
28
- `--ds-select-panel-radius: 8px`, or `--ds-radius-panel: 8px` to move every panel together.
814
+ not be retuned through the role consumers are told to use. Restore with `--ds-radius-panel: 8px`,
815
+ which moves every panel together. _(Corrected 2026-08-11: this note first offered
816
+ `--ds-select-panel-radius: 8px` as a way to restore just this panel. That token does not exist —
817
+ the dropdown resolves `--ds-radius-panel` directly — so setting it does nothing. `ds-autocomplete`
818
+ does have a per-panel `--ds-autocomplete-panel-radius`; the two dropdowns do not.)_
29
819
 
30
820
  - **Seven exit `@keyframes` are gone, replaced by four global presets.** `modal-out`, `ds-sheet-fade-out`
31
821
  and `drawer-scrim-out` become `ds-fade-out`; `ds-sheet-down` and the four `drawer-panel-close-*` become
@@ -43,6 +833,14 @@ While the package is on `0.x`, minor releases may contain breaking changes.
43
833
 
44
834
  ### Changed
45
835
 
836
+ - **`--ds-radius-inner` now reaches the small affordances it was written for.** Thirty-three reads across
837
+ fifteen component stylesheets took `var(--radius-sm)` directly — dropdown options, field clear buttons,
838
+ calendar days, chips, tag and toast close buttons — so the role a consumer is told to retune reached
839
+ exactly one component. Nothing moves (the role's default IS `--radius-sm`, verified by measuring a page
840
+ before and after), but it changes what a square brand costs: zeroing the three radius roles used to leave
841
+ five surfaces rounded and now squares every one. Five focus-ring radii inside `:focus-visible` keep
842
+ following the raw scale deliberately — a ring traces a box, it is not a surface a brand designs.
843
+
46
844
  - **`ds-auth-layout` compresses its own chrome on a short viewport, so the layout is never the reason a
47
845
  card scrolls.** Block padding, the column gap, the letter-mark tile and the masthead's inner gap clamp
48
846
  against `svh`. At ~330px of viewport — a landscape phone — that furniture costs ~131px instead of ~219px.
@@ -86,16 +884,6 @@ While the package is on `0.x`, minor releases may contain breaking changes.
86
884
  called a shell in 0.8.0 reintroduced the split vocabulary that rename existed to remove. Mechanical:
87
885
  rename the tag, the class and the six tokens. Nothing about the behaviour or the slots changes.
88
886
 
89
- ### Changed (internal, no action)
90
-
91
- - **`--ds-radius-inner` now reaches the small affordances it was written for.** Thirty-three reads across
92
- fifteen component stylesheets took `var(--radius-sm)` directly — dropdown options, field clear buttons,
93
- calendar days, chips, tag and toast close buttons — so the role a consumer is told to retune reached
94
- exactly one component. Nothing moves (the role's default IS `--radius-sm`, verified by measuring a page
95
- before and after), but it changes what a square brand costs: zeroing the three radius roles used to leave
96
- five surfaces rounded and now squares every one. Five focus-ring radii inside `:focus-visible` keep
97
- following the raw scale deliberately — a ring traces a box, it is not a surface a brand designs.
98
-
99
887
  ### Added
100
888
 
101
889
  - **Exit motion is swappable, the way entrances already were** — `--ds-modal-leave-keyframes`,
@@ -2067,7 +2855,7 @@ rect(…)` → `clip-path: inset(50%)` on visually-hidden helpers, and `min-/max
2067
2855
  set the `--primary-*` roles directly to hand-picked hex.
2068
2856
  - Relicensed from proprietary (UNLICENSED) to MIT.
2069
2857
 
2070
- ## 0.1.0 — 2026-06-12
2858
+ ## 0.1.0 — 2026-06-15
2071
2859
 
2072
2860
  Initial public release.
2073
2861