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

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,6 +8,549 @@ While the package is on `0.x`, minor releases may contain breaking changes.
8
8
 
9
9
  ## Unreleased
10
10
 
11
+ ## 0.10.2 — 2026-08-24
12
+
13
+ ### Added
14
+
15
+ - **`TableColumn.interactive` — the cell that says WHICH text opens the record.** On a
16
+ `[rowInteractive]` table the whole row is the control, so the hover tint says "clickable" and
17
+ nothing says what the click leads to; a `cursor: pointer` does not name a target. Mark the column
18
+ `interactive: true` and its cell takes a link colour plus an underline while the row is hovered —
19
+ **both, never hue alone** — through `--ds-table-cell-link-color` (default `--accent`) and
20
+ `--ds-table-cell-link-decoration` (default `underline`). Off unless a column asks for it, and inert
21
+ on a passive table for the same reason the row tint is: nothing should promise a click that does not
22
+ happen. Four list screens in one consumer had written this as
23
+ `:host ::ng-deep ds-table tr:hover .cell-name { color: var(--accent); text-decoration: underline }`,
24
+ which was their last table reach that no token could replace.
25
+
26
+ - **`TableRowAction` can vary its items per row: `hidden` and `disabledReason`.** The contract could
27
+ only GREY an item that was always there, so a menu whose items swap by status — a draft offering Edit
28
+ + Launch where a live record offers Revert + Delete — grew a permanently dead half on every row. That
29
+ is why the row-action column shipped in 0.6.3 and one consumer adopted it in **zero** of eleven row
30
+ menus. `hidden?: (row) => boolean` leaves the item out instead, and **a row with every item hidden
31
+ renders no kebab at all** rather than opening an empty menu. `disabledReason?: string | ((row) =>
32
+ string)` puts the why on the item's second line, read only when `disabled` returns true for that row —
33
+ a reason on a live item would read as a caveat on something that works.
34
+
35
+ - **`ds-menu-item` takes a `description` — a standing second line under the label.** For a limitation
36
+ the action carries ("only the first 1,000 rows", "read-only in this workspace"), visible without hover
37
+ or focus, which is what separates it from a `[dsTooltip]`. **It reaches assistive tech as
38
+ `aria-describedby`, not as part of the item's name:** the line is `aria-hidden` and referenced by id,
39
+ so the projected label alone names the action. Seven items across four files in one consumer
40
+ hand-rolled this with the same five-line rule; the width cap is now
41
+ `--ds-menu-item-description-max-width` instead of each app's own `14rem`.
42
+
43
+ - **`data-focus="inset"` — a focus style that survives a clipping ancestor.** The ring is a box-shadow
44
+ outside the border box, so any `overflow: hidden` ancestor ate it and left the element focusable with
45
+ **no indicator at all** — measured in four places in one app, one of them a `ds-button` inside a
46
+ wrapper that clips for its own animation. Clipping a card to hold a full-bleed child inside a rounded
47
+ corner is normal, and `ds-card` + `padding: none` invites exactly that. **Unlike the other four focus
48
+ styles this one is NOT pinned to `:root`:** a clip is a local problem, so the attribute works wherever
49
+ you set it and the declarations inherit into the subtree. Put it on the clipping element.
50
+
51
+ - **`ds-search.clear()` is public.** It empties the field, DROPS an armed keystroke and publishes `''`
52
+ at once — which writing `''` into `value` does not do: the effect watching `value` cancels the timer
53
+ only when the incoming text DIFFERS from what the control last pushed, so a host-owned Clear button
54
+ could not always drop the debounce it was clearing. Public for the same reason `focus()` is, and the
55
+ same button needs both.
56
+
57
+ - **`ds-search` binds to a form — both systems — and a disabled search now looks disabled.** It held a
58
+ value that nothing could bind: no `NG_VALUE_ACCESSOR`, so `[(ngModel)]`, a `formControlName` and a
59
+ signal form all slid off it while its own `[(value)]` kept working. It extends
60
+ `DsControlValueAccessor` now, like every other control that carries a value, and a new `disabled`
61
+ input folds together with the form's own disabled state. The shell paints the disabled surface from
62
+ the inner input's state, which it never did — a disabled search looked live and still took a click.
63
+ **Deliberately no label and no message row.** A toolbar filter is not a validated field, and giving
64
+ it the field chrome would restyle every toolbar it sits in; reach for `ds-input` where a search
65
+ needs a label.
66
+
67
+ - **`--ds-menu-radius` — the bare `ds-menu` corner, which two token descriptions already promised.**
68
+ The component hardcoded `var(--radius-md)` while `token-descriptions.json` referred to
69
+ `--ds-menu-radius` as though it were public; the dead-token audit caught it. Same default, so
70
+ nothing moves — this only makes the documented hook real. The panelled case stays separate: inside a
71
+ `ds-popover` the menu clips to `--ds-menu-clip-radius`, which the popover publishes.
72
+
73
+ ### Changed
74
+
75
+ - **`ds-search` no longer takes the field message inputs, because it never rendered them.**
76
+ Since it gained form binding it extended `DsControlValueAccessor`, which sits on `DsFieldBase` — so
77
+ the API reference advertised `hint`, `error`, `warning`, `errors`, `invalid`, `touched`,
78
+ `reserveMessage` and `messageIcon` on a component whose template has no `ds-field-message` and whose
79
+ class reads none of them. **A consumer binding `error="Too short"` on a `ds-search` got silence, and
80
+ the reference had told them it would work.** Those eight inputs are gone from it now; the reference
81
+ lists the ten it actually implements.
82
+ **BREAKING only if you bound one:** it used to compile and do nothing, and now it is a template type
83
+ error, which is the point. Where a search needs a label or an error line, that is `ds-input` — a
84
+ toolbar filter is not a validated field, which is the same reasoning that kept the message row off it
85
+ in the first place.
86
+ **How the split works, since it is a shape other controls may want:** the `ControlValueAccessor`
87
+ plumbing is now `valueControlBridge()`, a function rather than a base class, so a control can bind to
88
+ a form without inheriting the message API. `DsControlValueAccessor` is that function plus
89
+ `DsFieldBase` and delegates to it, so the logic exists once rather than twice. `hidden` stayed on
90
+ `ds-search`: it belongs to the forms contract — signal forms reaches every control through it — not to
91
+ the message API.
92
+ - **A field's message line now carries a glyph for `error`, `warning` and `success` — and not for
93
+ `hint`.** Colour was the whole signal before, and in the light theme warning (#8A7400) against success
94
+ (#156822) is a hue apart and nothing else: WCAG 1.4.1 is about exactly that, and four of the six
95
+ systems audited for the fill question carry a per-state icon in the field. **`hint` deliberately stays
96
+ bare** — it is the resting text rather than a state, and it is the majority of rows on any real form
97
+ (25 of 43 on our own input page), so a glyph there is noise rather than signal.
98
+ **Per state, independently, app-wide:**
99
+ `provideDsConfig({ field: { stateIcons: { warning: false, hint: 'info' } } })` — a name replaces the
100
+ glyph, `false` removes it, each key is independent of the others, and **`stateIcons: false` is the one
101
+ line back to how fields looked before**. **Per field:** `messageIcon` wins over both —
102
+ `[messageIcon]="false"` drops the glyph on that field alone. It is declared once on the shared
103
+ field base, so it reaches all fifteen fields that render a message row.
104
+ **Two new hooks:** `--ds-field-message-icon-gap`, and `--ds-field-message-icon-offset`, which centres
105
+ the glyph on the FIRST line rather than the block — the row is `align-items: flex-start` now, so a
106
+ message that wraps keeps its glyph beside the first line instead of floating in the middle. The offset
107
+ defaults to a calc over the two tokens that set that line, so it survives a retuned message type.
108
+ **The size is not a token, on purpose:** `ds-icon` takes a number and writes `width`/`height`
109
+ attributes, so a CSS hook would mean reaching into another component's template. The glyph is 14px
110
+ (`--icon-sm`, under the 12px message text); making icon size CSS-driven is a separate change to
111
+ `ds-icon`.
112
+ - **`ds-stat`'s `value` takes `string | number | null`, so Angular's own pipes bind to it.**
113
+ `number`, `currency`, `percent` and `date` are all typed `string | null`, so
114
+ `[value]="count | number"` failed `strictTemplates` with TS2322 and consumers wrote
115
+ `count.toLocaleString('en-US')` in the template instead — which pins a locale rather than reading
116
+ `LOCALE_ID`, and re-runs on every change-detection pass where a pure pipe is cached. One consumer's
117
+ KPI row carries both idioms side by side for exactly this reason. `null` renders as nothing, like the
118
+ empty default, and the four pipes now have a demo on the docs page — which is also the test, since
119
+ that section compiles under `strictTemplates`.
120
+
121
+ - **If you EXTEND a DS component, eleven classes grew and six members changed type.** `npm run
122
+ class-surface` against 0.10.1: `DsFieldBase` (`messageIcon` — the state glyph, declared once for
123
+ every field rather than per component), `DsControlValueAccessor` (`bridge`),
124
+ `FieldMessageComponent` (`config`, `iconResolved`), `AutocompleteComponent` and
125
+ `MultiSelectComponent` (`chipsMode`, `showsEveryChip`), `MenuItemComponent` (`description`,
126
+ `descriptionId`), `SearchComponent` (the CVA surface it now declares itself: `bridge`,
127
+ `disabled`, `formDisabled`, `hidden`, `isDisabled`, `markTouched`, `registerOnChange`,
128
+ `registerOnTouched`, `setDisabledState`, `writeValue`), `SidenavItemComponent` (`rail`,
129
+ `railResolved`), `SidenavComponent` (`rail`), `TableComponent` (`actionReason`, `actionsFor`,
130
+ `hasActionsFor`, `visibleRowActions`) and `TimePickerComponent` (`insideATrigger`). A subclass
131
+ declaring any of those names now fails with TS4114 — or TS2415, since a redeclared private
132
+ collides just as a public one does, and a name on `DsFieldBase` reaches every field through it.
133
+ **Six members kept their name and changed type**, which is the case that compiles for a caller
134
+ and breaks an overrider: `maxVisibleChips` on both pickers (widened to
135
+ `number | 'fit' | 'all' | null`, default now `null`), `FieldMessageComponent.icon` (widened to
136
+ `IconName | false | null`, so `false` can mean "no glyph" against a state that supplies one),
137
+ `DsConfig.field` (its shape grew the glyph defaults), `SearchComponent.clear` (`protected` →
138
+ public), `StatComponent.value` (widened to `string | number | null`) and
139
+ `TimeColumnsComponent.onKey` (its parameter list changed). **What the report does NOT show:**
140
+ `ds-search` no longer extends the field base, so it loses eight inherited inputs — the tool
141
+ compares declarations per file and a dropped `extends` moves nothing, so that break is documented
142
+ in its own entry above and not here.
143
+
144
+ - **Every readback that resolves through `DS_CONFIG` is now public.** `sizeResolved` on fourteen
145
+ controls, plus `elevationResolved` / `paddingResolved` (card), `withDotResolved` (badge),
146
+ `borderedResolved` / `stickyScrollbarResolved` (table), `dividersResolved` (both modals),
147
+ `reserveMessageResolved` (every field), the picker locale/format resolvers, and
148
+ `brandName` / `letterGlyph` / `taglineText` (sidenav, auth-layout). They were `protected`, so the
149
+ migration path 0.10.0 published — "read `sizeResolved()` now that `size()` returns null when unbound"
150
+ — did not compile: reading one from a host, a test or a `viewChild` was TS2445.
151
+ **The line is `DS_CONFIG`, and it is deliberate.** A host cannot recompute an app-level default, so
152
+ that readback has to be public. Members a host CAN derive from its own bindings stay closed:
153
+ `invalidResolved`, `railResolved`, `sortModeResolved`, `filterModeResolved`.
154
+ **Subclassers:** these are new public names on the classes, so a subclass that happens to use one now
155
+ needs `override`. Composition remains the supported route.
156
+
157
+ - **The focus ring's inner gap is `transparent`, not `--surface-canvas`.** The 2px band exists to
158
+ separate the ring from the element, so it has to match what is actually BEHIND — and a named surface
159
+ only is that when nothing intervenes. In a dark app with white cards it painted the dark canvas as a
160
+ rim around a white card, reading as a rendering artifact rather than a focus state. Transparent costs
161
+ nothing on a canvas-coloured ground (the same pixels show through) and is right on every other.
162
+
163
+ - **`maxVisibleChips`: `null` means "unset" now, and `'all'` is the mode that shows every chip.**
164
+ `ds-autocomplete` and `ds-multi-select` took `number | 'fit' | null`, in which `null` was the
165
+ LOUDEST setting — render every chip and let the trigger wrap — while 0.10.0 gave `null` a service
166
+ meaning on twenty-two other inputs: not deciding, fall through to the default. The three modes are
167
+ named now: `'fit'` measures the trigger and shows what fits, a number is a ceiling that is still
168
+ measured ("at most N"), `'all'` renders the lot. **BREAKING: `[maxVisibleChips]="null"` used to show
169
+ every chip and now resolves to `'fit'`** — bind `maxVisibleChips="all"` for the old behaviour. Leaving
170
+ it unbound behaves exactly as before, since `'fit'` was already the default, and `null` now leaves
171
+ room for a `DS_CONFIG` slot to answer it app-wide.
172
+
173
+ - **The active `ds-sidenav-item` is a tinted wash with a coloured label, not a solid brand pill** — and
174
+ the edge rail is an input rather than a token you blank out. The item filled with `--accent` and put
175
+ `--text-on-primary` on its label, making the loudest element on the screen out of a state that only
176
+ says "you are here"; two apps independently replaced it, which is the signal that decided this.
177
+ Material fills its navigation drawer's active item with `secondary-container` and labels it
178
+ `on-secondary-container`; Carbon uses `$background-selected` with a border and a weight bump.
179
+ Neither fills with the brand accent. Ours is `--accent-subtitle` behind an `--accent-strong` label,
180
+ and hover deepens toward the accent (`--accent-muted`) instead of lightening toward white — the old
181
+ 88%-toward-white mix was invisible on a wash. **The state still does not rest on colour alone:** the
182
+ edge rail and the weight bump both stay — and **the rail is now `--accent-strong`, the active label's
183
+ own colour, instead of `--secondary`.** An orange bar across a monochrome-blue row measured **2.33:1**
184
+ on the light wash, under the 3:1 floor a non-text indicator needs; the accent measures 6.16:1 light and
185
+ 5.28:1 dark. Carbon's indicator is the interactive colour and Material's IS the wash — neither
186
+ introduces a second hue. Restore the old bar with `--ds-sidenav-item-rail: var(--secondary)`.
187
+ Every `--ds-sidenav-item-*-active` token keeps its name, so
188
+ an app that already retuned them keeps its own look and needs no edit.
189
+ **`[rail]="false"` on `ds-sidenav`** drops the edge marker for every item, and an item can override
190
+ it for itself (`[rail]` on `ds-sidenav-item`, unset = follow the parent). The old route was
191
+ `--ds-sidenav-item-rail: transparent` or a `::ng-deep` box-shadow reset — both still work, but the
192
+ input says what it means. `SidenavContract` gained a `rail: () => boolean` member; nothing outside
193
+ the library is expected to implement it.
194
+
195
+ - **The shipped migration manifests say WHERE to look, not only what changed — and a lint now holds
196
+ them to it.** `migrations/<version>.json` (the files `dist/ds/migrations/` carries into your
197
+ `node_modules`, which the auto-update plugin runs) gained `surface`, `detect`, `verify`, `restore`,
198
+ `supersedes` / `supersededBy`, and a structured `deleteList`. The reason is a consumer upgrade that
199
+ went 0.6.0 → 0.10.1 and passed over two entries in silence: `0.7.1`'s
200
+ `table-sortkey-non-null-when-unsorted` pointed at `ds-table[sortKey]`, which appears in nobody's
201
+ template, while the code that breaks was their own store —
202
+ `sorting: store.sortKey() ? { path: store.sortKey()!, … } : undefined` — so the search found
203
+ nothing, the item was recorded not-applicable, and the re-check's clean grep agreed. Three
204
+ server-paged screens kept sorting by a column whose header showed no sort. `surface` and `detect`
205
+ make that item searchable in the artifact that actually changes; `verify` gives a behavioural entry
206
+ the positive assertion a re-check can test, since there is no removed symbol whose absence proves
207
+ anything. **Every published manifest was back-filled the same day:** 167 items across 19 releases
208
+ got a `surface`, every behavioural one a `verify`, every changed default a `restore`, and the 32
209
+ prose `DELETE-LIST:` lines became `deleteList` arrays with a greppable `find` each — four of those
210
+ "lines" turned out to be the words "the DELETE-LIST" inside ordinary prose. Two default flips that
211
+ reverse each other now link both ways: `0.7.0` / `0.7.1` on `reserveMessage`, and `0.8.0` / `0.9.0`
212
+ on the table's sort mode. `npm run migration-lint` enforces the contract with no warning level, and
213
+ both the release preflight and the PR gate run it, so a manifest nobody can act on stops the
214
+ pipeline instead of reaching a consumer. Three CHANGELOG blocks also gained the "What you can now
215
+ DELETE" table their manifests had been carrying alone — 0.10.0's nineteen rows, 0.10.1's and
216
+ 0.6.2's.
217
+
218
+ ### Fixed
219
+
220
+ - **One focus ring per field, not two.** Since 0.10.0 the universal `:where(:focus-visible)` rule has
221
+ given every focusable element a `box-shadow`, and these shells paint their own on `:focus-within` —
222
+ `outline: 0`, which each inner control already had, cannot cancel a shadow. So a focused field drew a
223
+ tight ring around its inner control AND a halo around the box. Measured on five shapes: `ds-search`,
224
+ `ds-autocomplete`, `ds-date-picker`, `ds-number-stepper`, and any field inside a `ds-field-group`
225
+ (fixed once in the shared segment mixin). It is the same trap 0.10.0 warned consumers about — an app
226
+ rule that styles focus with an `outline` only — landing in our own components.
227
+ **The reset is scoped to the control the shell speaks for, deliberately.** A `ds-number-stepper` step
228
+ button keeps its own ring, and so does a chip's close button: those are `tabindex="0"` tab stops, and
229
+ the halo is already on, so it cannot say which of them focus moved to. The date picker's calendar
230
+ toggle is `tabindex="-1"` and correctly loses its ring.
231
+
232
+ - **A flat line box stopped shaving descenders off clipped labels** (mm-broker MBP-245). `.option` sets
233
+ `line-height: 1` while `.option-label` adds the `overflow: hidden` its ellipsis needs and no padding,
234
+ so the label box was exactly the font size tall and the glyph box was taller: measured **2.13px above
235
+ the cap line and 1.47px below the baseline** clipped, on every option rather than only the ones with a
236
+ descender. Fixed with `overflow: clip` plus a `var(--space-1)` clip margin, which **moves no geometry**
237
+ — the option row stays 30px, the multi-select row 36px, the table row 38px.
238
+ **Six sites:** the shared dropdown overlay (`ds-select`, `ds-autocomplete`), `ds-multi-select`'s own
239
+ copy, `.cell-clip` in `ds-table` and `.label` in `ds-breadcrumbs` (both measured), and the `.crumb`
240
+ rules in `ds-topbar` / `ds-page-header`, which share the shape and are unreachable in our own docs.
241
+ **Two behaviours checked rather than assumed:** the ellipsis still applies (`text-overflow` reads any
242
+ non-`visible` overflow), and `ds-table`'s clipped-cell popover still fires, since `scrollWidth >
243
+ clientWidth` still reports true under `clip`.
244
+ - **A field bound with signal forms threw once per field, and then showed an error it had already
245
+ cleared.** `resolveFieldMessage` subscribes to `NgControl`'s `events` stream to follow reactive and
246
+ template-driven forms. The `NgControl` that signal forms bridges carries no such stream, so the
247
+ subscription threw `TypeError: Cannot read properties of undefined (reading 'pipe')` — four times on
248
+ our own Practice → Signal Forms page, swallowed into the console. **The second half is what a user
249
+ saw:** the throw left that snapshot frozen at first render, and the message resolver falls back to it
250
+ whenever the live errors go empty — so a field that had just become VALID went on showing its FIRST
251
+ failure, with `aria-invalid="true"`. Measured through CDP with real input: empty → "We need an email",
252
+ `nope` → "That does not look like an email address", a valid address → **the required message again**.
253
+ Now the `NgControl` path bows out entirely when it has no live stream, leaving the component's own
254
+ inputs — which is where a signal-forms field's errors and touched arrive — as the single source. The
255
+ same sequence now clears the message and drops `aria-invalid`. **Reactive and template-driven forms are
256
+ untouched** and were re-checked on `/components/input`: too short, empty and valid each render
257
+ correctly, as before.
258
+
259
+ - **`components.md` was missing two layouts and naming three sidenav defaults that are not the
260
+ defaults.** The digest `tools/build-schematics.mjs` copies into `dist/ds/` is what a consumer's own
261
+ agent reads to answer "what does this library have", and `ds-app-layout` and `ds-auth-layout` were
262
+ absent from it entirely — an agent asked to build a shell or a sign-in screen could not find either
263
+ and had no way to know they existed. It also named `--primary`, `--text-on-primary` and
264
+ `--secondary` as the active sidenav item's defaults, which the wash rework in this same release
265
+ replaced. Both are corrected. Three smaller claims went with them: the search page said two things
266
+ skip the debounce where the code and this changelog both say three, the `--ds-stat-value-white-space`
267
+ description said an unwrapped phrase is clipped when it escapes the tile instead, and `ds-badge`
268
+ carried a superseded docblock. **No API changed** — only what the shipped documentation says about it.
269
+
270
+ - **Five more overlays dismiss on a click in the host's own empty width.** `ds-select`,
271
+ `ds-multi-select`, `ds-autocomplete`, `ds-time-picker` and `ds-color-picker` all tested the whole
272
+ HOST in their outside-pointer guard, which is the defect `ds-date-picker` was fixed for in 0.10.1
273
+ (MBP-225): the trigger box hugs its own content while the host takes whatever width a consumer's
274
+ layout gives it, so the label, the message row and any bare strip beside the trigger swallowed the
275
+ dismiss instead of performing it. Each guard now tests its TRIGGER, as `ds-popover` always did;
276
+ `ds-time-picker` tests whichever of its three triggers are present, since a range renders two.
277
+ **Behaviour change if you relied on it:** a press on the label of an open picker now closes the
278
+ panel. A press on the trigger still keeps it open, which is what that exception exists for (the
279
+ caret, and re-focus).
280
+
281
+ - **`variant="tonal"` now reads as disabled in the dark theme, where it rested on desaturation alone.**
282
+ Measured on `/components/button`: the disabled label was **1.11:1** from the enabled one (#778ff8 →
283
+ #979eb5) and the fill **1.20:1**, so the only signal was a hue going grey — and the label sat at 5.51:1
284
+ on its own fill, which reads as a live control. Tonal now takes the same 40% label mix ghost, text and
285
+ outline already use, toward `--surface-default`: the state gap becomes **2.90:1** in dark and **3.39:1**
286
+ in light, and the label keeps its hue instead of turning grey. **Toward the surface and not toward
287
+ tonal's own fill, even though the label sits on that fill** — the disabled fill has already moved
288
+ toward the label, so mixing into it yields only 2.56:1. The fill itself still barely moves (1.09:1
289
+ light, 1.20:1 dark) and does not need to: the label carries the state, which is the same division of
290
+ labour the transparent variants shipped with in 0.10.1. Override with
291
+ `--ds-button-label-color-disabled` as before.
292
+
293
+ - **`ds-multi-select`'s panel follows `--ds-dropdown-panel-radius` like the other two.** Its panel
294
+ element is `class="panel"`, not `.dropdown-panel`, so it never picked up the shared overlay rule and
295
+ sat at a hardcoded `--radius-md` (8px) while `ds-select` and `ds-autocomplete` moved with the token. It
296
+ now resolves the same chain, so a brand that rounds its dropdowns rounds all three.
297
+
298
+ - **`ds-date-picker`: a click on the host's own empty width now dismisses the open calendar.** The
299
+ outside-pointer guard treated the whole host element as the trigger, but the visible trigger box
300
+ hugs its mask while the host takes whatever a consumer's layout gives it — `flex-grow: 1` beside a
301
+ Clear button leaves a wide bare strip between the field and the button, and a click there kept the
302
+ calendar open with no visible reason (mm-broker MBP-225). The guard now tests the trigger box
303
+ itself: a press on the field or its calendar glyph still keeps the panel up, while the label, the
304
+ message row and the host's empty width dismiss it like any other outside click.
305
+
306
+ ### What you can now DELETE
307
+
308
+ None of this is required — skipping it leaves working code that is merely redundant. Each row is a
309
+ workaround written against a hook that only landed in this release.
310
+
311
+ | If you have | Delete it, because |
312
+ | --- | --- |
313
+ | A hand-rolled second line inside a `ds-menu-item` — a projected span, a `max-width` near `14rem`, and probably no `aria-describedby` | The `description` input, capped by `--ds-menu-item-description-max-width` |
314
+ | `overflow: visible` forced back onto an element that needs to clip, or your own inset shadow standing in for a focus ring | `data-focus="inset"` on the clipping element |
315
+ | A `border-radius` override aimed at `ds-multi-select .panel` alone | `--ds-dropdown-panel-radius` now reaches all three connected panels |
316
+ | A timer of your own around a `ds-search` Clear button, or a value written twice to make the debounce let go | `clear()` |
317
+ | A copy of the config fallback chain in your own host — `this.size() ?? config.control?.size ?? 'md'` | The component's resolver is public now; read `sizeResolved()` |
318
+ | Your own wash replacing the solid active sidenav pill — a `--ds-sidenav-item-bg-color-active` override plus a matching label colour | That IS the default now; compare yours against it and drop it if they agree |
319
+ | `--ds-sidenav-item-rail: transparent`, or a `::ng-deep` box-shadow reset to hide the active rail | `[rail]="false"` on `ds-sidenav` |
320
+ | A `::ng-deep` `border-radius` rule on a bare `ds-menu` | `--ds-menu-radius` |
321
+ | `--ds-button-label-color-disabled` pinned on a tonal button to make its disabled state visible, most likely only in the dark theme | The default disabled-label recipe carries it |
322
+ | `count.toLocaleString('en-US')` (or any hand-rolled formatting) inside a `ds-stat` binding, because `[value]="count \| number"` would not typecheck | The pipe binds now, and it reads `LOCALE_ID` instead of a pinned locale |
323
+ | A `::ng-deep ds-table tr:hover .some-cell { color; text-decoration }` rule to make one cell read as the row's link target | `interactive: true` on that column, retuned with `--ds-table-cell-link-color` / `--ds-table-cell-link-decoration` |
324
+
325
+ ## 0.10.1 — 2026-08-20
326
+
327
+ ### Removed
328
+
329
+ - **`--opacity-muted` is gone from the token scale.** It was the last token in the file that no
330
+ component read: the disabled states moved onto `--text-disabled` + `--opacity-disabled` in
331
+ 0.10.0, and it had been sitting there since, labelled a legacy alias. Keeping a dead number in a
332
+ purpose-named scale is worse than removing it — it invites exactly the override that 0.10.0's
333
+ DELETE-LIST had to warn about twice, where a consumer retunes it on `ds-button` /
334
+ `ds-icon-button` and gets a silent no-op. **Nothing in the library changes.** If you set it, drop
335
+ the declaration; if you READ it in your own CSS, inline the 0.6 or move to the token that names
336
+ the job — `--opacity-disabled` (0.5) for a disabled state where opacity is the only signal,
337
+ `--opacity-text-disabled` (0.38) for disabled text. The comment above the block claims every
338
+ token in it has a real consumer; that is true again.
339
+
340
+ ### Added
341
+
342
+ - **`ds-segmented` joins the form systems, and gains a label and a message row.** It carried a value
343
+ and no form could bind it — no `NG_VALUE_ACCESSOR`, so `[(ngModel)]`, a `formControlName` and
344
+ signal forms all slid off it. It now extends `DsControlValueAccessor` and resolves its message
345
+ through the same `resolveFieldMessage` as every other field, mirroring `ds-radio-group`: `label`,
346
+ `hint`, `error`, `warning` and `errors` all behave as they do elsewhere, and `disabled` folds
347
+ together with the form's own disabled state. **The DOM grew a level to fit them:** the pill moved
348
+ off `:host` onto an inner `.track`, so the host can stack label, pill and message. The pill's own
349
+ tokens stayed on `:host` and inherit down, so a token override is unaffected — but a
350
+ `::ng-deep` rule written against the host AS the pill (a background, a border-radius, a grid) now
351
+ targets the stack instead, and wants `.track`.
352
+
353
+ - **`invalid` paints the error state only — it no longer promotes `hint` to the error message.**
354
+ Every state carries its own text now, and `hint` is never recoloured into somebody else's state.
355
+ **BREAKING:** `[invalid]="true" hint="Must be before end date"` used to render that hint in red,
356
+ through `role="alert"`. It now renders a red border with a **grey** hint. Use
357
+ `error="Must be before end date"` instead — the state and the message come together.
358
+ **Why, beyond tidiness.** The idiom lost the actual hint: when both were set, the help text the
359
+ author wrote was replaced by the error rather than shown alongside it. It also announced help text
360
+ as an alert, and it made a template unreadable — whether `hint="…"` was a hint or an error depended
361
+ on a different attribute. It was the last input that borrowed another one's text; `success` stopped
362
+ doing it in the same release.
363
+ **`invalid` is not going away and still has its own job:** the error state with NO message, for when
364
+ the text lives elsewhere — a form-level error summary, or one message covering a whole
365
+ `ds-field-group` — plus `aria-invalid` for that case. Carbon and Material split the boolean from
366
+ the text the same way.
367
+ Our own docs taught the old idiom on 13 components (14 of 19 `[invalid]` bindings also bound
368
+ `hint`); all of them now use `error`.
369
+
370
+ - **A form model can now raise a WARNING, not only an error** — `DS_FIELD_WARNING_KIND`, newly
371
+ exported. A validation error whose `kind` is `'warning'` paints the field's warning state and shows
372
+ its message, but leaves the control **valid**: `aria-invalid` stays off and a submit guard reading
373
+ validity is not blocked.
374
+ **Why it had to ride inside `errors`.** Angular's `AbstractControl` has no channel for an advisory
375
+ remark — it exposes `errors` and the validity derived from them, and nothing else. So there was no
376
+ way for a form to say "this is worth mentioning but not wrong": `warning` and `success` could only
377
+ be bound by hand from the consumer's own state.
378
+ **It works from both form systems with no new plumbing**, which is the point. A reactive or
379
+ template-driven validator returning `{ warning: 'Long runs of capitals are hard to scan' }` has its
380
+ KEY read as the kind; signal forms assigns its own `ValidationError[]`, which already carries a
381
+ `kind`. Both land in the same `errors` signal.
382
+ Ranked below the explicit `warning` input — the consumer's own string wins, exactly as `error` beats
383
+ `errors` — and shown only after the user has interacted, like any other validation message.
384
+ **`DsFieldError` and `DsFieldErrorsInput` are exported too**, so a typed validator can be written
385
+ against the shape the input accepts. Reserved-kind caveat: a validator already using the key
386
+ `warning` for a BLOCKING error now reads as advisory. Rename that key if you have one.
387
+
388
+ - **`success` exists on all nine bordered fields, and it is now a STRING that carries its own text.**
389
+ Added to `ds-textarea`, `ds-select`, `ds-multi-select`, `ds-autocomplete`, `ds-date-picker`,
390
+ `ds-time-picker`, `ds-otp-input` and `ds-color-picker` — it was on `ds-input` alone, so a form could
391
+ not use the state consistently. The three box-less controls (`ds-checkbox`, `ds-radio-group`,
392
+ `ds-switch`) and `ds-slider` deliberately do NOT get it: they have no box for a border to appear on,
393
+ so the state would show in the message line alone and read as a different treatment.
394
+ **BREAKING for `ds-input`, the one field that already had it:** `success` was
395
+ `input(false, { transform: booleanAttribute })` and is now `input<string>('')`. Replace
396
+ `[success]="true" hint="Available"` with `success="Available"`.
397
+ **Why the type changed rather than staying a flag.** It was the only state that could not say
398
+ anything: `error` and `warning` carry their own text, and `success` was a boolean that recoloured
399
+ the `hint` green. So `success` was the one state whose message had to be smuggled through a
400
+ different input, and a reader of the template could not tell a green hint from a grey one. It is now
401
+ a fourth rung in the same ladder — `error` → `errors` → `warning` → **`success`** → `hint` — and
402
+ reads exactly like `warning`: the text IS the state, no second binding.
403
+ **What this removes:** a success border with no message, which is no longer expressible — exactly as
404
+ it never was for `warning`. `invalid` still exists as the flag partner of `error`, for the
405
+ `[invalid]="…" [hint]="…"` idiom that predates `error`.
406
+
407
+ - **`ds-list-item` can hold its own controls: `[leading]` and `[trailing]` render OUTSIDE the row's
408
+ button.** A row with a checkbox AND a row-level action had no shape here — every projected node went
409
+ inside `<button class="activator">`, where a nested control is invalid HTML, its click bubbles into
410
+ `activated`, and a screen reader folds it into the button's name and never announces its checked
411
+ state. Dropping `clickable` was no answer either: `cursor`, `:hover`, `:focus-visible` and
412
+ `aria-current` all hung off that button. The row is now the flex container and the button wraps only
413
+ the text, so the master–detail shape works — a checkbox per row for a bulk action, the row itself
414
+ choosing what a detail pane shows, two independent targets.
415
+ **This stays a `role="list"`, deliberately not a `listbox`:** the ARIA spec is explicit that a
416
+ `listbox` option cannot hold interactive content, so a real listbox would have made the pattern
417
+ impossible rather than easier. `role="listitem"` carries no such restriction.
418
+ **`selected` also works properly now.** It set `aria-current` on the inner button, so it did nothing
419
+ at all unless `clickable` was on; `aria-current` sits on the host, which is the row that is current.
420
+ **BREAKING for CSS overrides only** — no API changed. `.activator` no longer carries the row's
421
+ padding, gap or hover tint: those moved to the host. A `::ng-deep .activator { padding: … }` now pads
422
+ the text alone, and a `::ng-deep .activator:hover` no longer paints the full row.
423
+
424
+ - **Per-side padding on `ds-modal` / `ds-modal-card`.** Each region resolved ONE `pad-y` applied to
425
+ both of its edges, so a layout whose header pads only at the top and whose actions row pads only
426
+ at the bottom — the body's own padding carrying the whole gap between them — could not be said
427
+ through the API at all. mm-broker has held three `!important` rules on `.modal > .header` /
428
+ `> .body` / `> .actions` for exactly this, reaching past the component into its internal class
429
+ names, and `DS_CONFIG.modal.dividers` could not retire them. Six new tokens —
430
+ `--ds-modal-header-pad-top` / `-pad-bottom` and the same for `body` and `actions` — each fall back
431
+ to their region's existing `pad-y`, so **nothing moves unless you set one**, and `--ds-modal-*-pad-y`
432
+ keeps working as the shorthand for both edges.
433
+
434
+ - **`ds-table`'s own icon buttons are themeable.** The row-action kebab and the column-picker trigger
435
+ hardcoded `--icon-default`, `--icon-strong` on hover and an `--accent` focus outline, and neither is a
436
+ `ds-icon-button`, so the icon-button tokens never reached them — a consumer whose design calls for a
437
+ teal row menu had no supported way to get one short of repainting `--icon-default` for the whole app.
438
+ Three resolvers now cover both: `--ds-table-icon-btn-color`, `--ds-table-icon-btn-color-hover` and
439
+ `--ds-table-icon-btn-focus-color`, defaulting to exactly what was hardcoded, so nothing moves unless
440
+ you set them.
441
+
442
+ ### Fixed
443
+
444
+ - **`ds-field-message`'s docs claimed `state` picks an icon. It never did.** The input's docblock
445
+ said it "decides colour and icon" and `icon`'s said it "overrides the glyph the `state` would
446
+ pick" — but `icon` is a plain `input<IconName | null>(null)` with no per-state default, so a
447
+ consumer following the reference got a colour and no glyph. **Nothing in the library changes**: the
448
+ JSDoc and the generated API reference now say what the code does — `state` sets the colour, and a
449
+ field that wants an icon passes one.
450
+
451
+ - **A nullable binding on a message input no longer throws.** `hint`, `error`, `warning` and
452
+ `success` took a bare `string`, and the resolver called `.trim()` on whatever arrived — so
453
+ `[error]="form.errors?.message"` put `null` in and crashed the render with a `TypeError` the
454
+ moment the expression was empty. All four now transform at the input boundary, absorbing
455
+ `null`/`undefined` to `''` and trimming, so a blank binding simply means "no message". **You can
456
+ now delete** the `?? ''` you wrapped such a binding in.
457
+
458
+ - **A `ds-menu` inside a `ds-popover` clips its rows to the panel's rounded corners.** The first and
459
+ last row's fill — a hover tint, or the red of a destructive item — painted through the panel's
460
+ corner, so a destructive last item showed **two square red corners under a rounded popover**.
461
+ **The cause was not a missing clip; it was a clip of the wrong shape.** `ds-menu` has
462
+ `overflow: hidden`, and that is what rounds the edge rows for a bare menu. But its
463
+ `:host-context(.popover)` block flattened `border-radius` to `--radius-flat` while leaving `overflow`
464
+ in force, so inside a popover the menu clipped its rows **square** and the panel's 12px corner
465
+ showed that square fill through it. The popover now publishes `--ds-menu-clip-radius` — its own
466
+ radius less the border it contains — and the menu clips to that, concentric at 11px inside a 12px
467
+ panel. A brand overriding `--ds-popover-radius` is followed automatically.
468
+ **Not fixed with `overflow: hidden` on the panel**, which was the obvious move: a submenu is a CDK
469
+ overlay portaled to `body`, so clipping the panel would not have reached it, and the panel's clip
470
+ would have cut an edge row's focus ring — the same defect fixed in `ds-filter-bar` this month.
471
+ Nothing else changes: the item radius token `--ds-menu-item-radius` still defaults to 0, because the
472
+ MENU owns the edge corners, not the row.
473
+
474
+ - **Clearing or replacing `ds-date-picker`'s `value` from outside now clears the picker's own typing
475
+ error.** `typedInvalid` / `rangeInvalid` were set by the typing paths and cleared only by those and
476
+ `applyPreset`, so `value.set(null)` re-rendered the field to empty and left **"Enter a valid date
477
+ (MM/DD/YYYY)" standing over it**. `[error]` was no help: a consumer who has just cleared the field
478
+ has no error of its own to bind, and an empty string falls straight back to the picker's.
479
+ The `value → text` effect now clears both flags. It is the right place because every typing path
480
+ holds an `editing` guard while it runs, so reaching the effect means the value did NOT come from the
481
+ keyboard — and a leftover error no longer describes what the field is about to show. Verified that
482
+ neither typing path writes `value` on the invalid branch, so blur validation still stands.
483
+ **This retires two consumer workarounds.** One app was tearing down a whole modal body on `closed`
484
+ purely to get a fresh picker — and that had a hole, since reopening inside the 300 ms leave animation
485
+ cancels the close, `closed` never fires and the stale error survived. A second dialog had no
486
+ workaround at all, so a mistyped date of birth read "Enter a valid date" over an empty field the next
487
+ time it opened.
488
+
489
+ - **A disabled `ds-button` with `variant="ghost"`, `variant="text"` or `variant="outline"` mixes its
490
+ label toward the surface instead of taking the shared fixed-lightness recipe.** New default:
491
+ `color-mix(in srgb, <label> 40%, var(--surface-default))`. These three share one accent source and
492
+ have no fill that could carry the state, so the label is the whole signal — and the shared recipe
493
+ was failing it, badly in dark. Measured against the enabled label: light **2.54 → 3.41:1**, dark
494
+ **1.11 → 2.91:1**. `outline` does have a border, but its disabled border resolves to only
495
+ **1.30:1** against the page — less than its own *enabled* border at 1.49:1 — so it never covered
496
+ for the label.
497
+ **The dark number is the real defect.** `--primary-strong` there is already light (OKLCH L 67.9%),
498
+ so a recipe pinning the disabled label at L 70% landed two points from the enabled one and the two
499
+ differed in chroma alone. A fixed lightness cannot serve both themes: in light, disabled is
500
+ lighter than the accent; in dark the accent is already light, so disabled has to go darker. The
501
+ surface knows that direction and a constant does not — which is the whole reason the mix target is
502
+ `--surface-default` rather than a number.
503
+ **The trade:** the disabled label is fainter against its own ground — **2.00:1** light, 1.99:1
504
+ dark, where the old recipe gave 2.69 / 6.45. Disabled text is exempt from WCAG 1.4.3 and 1.4.11
505
+ and Material ships its equivalent at 1.93:1, so this is inside practice. Chroma rises with the
506
+ mix (0.036 → 0.099 light), so the disabled label stays tinted rather than going grey; that was
507
+ chosen deliberately over a desaturating variant after looking at both.
508
+ **`solid` and `tonal` are unchanged**, deliberately: a white label mixed into a white surface does
509
+ not move, and tonal's disabled fill already carries the state on its own.
510
+ **Known limitation:** the mix target is `--surface-default`, a stand-in for "whatever is behind" — CSS cannot read the actual
511
+ backdrop, so on a tinted ground (a card at `--surface-secondary`, an alert) the disabled label is
512
+ computed against the page colour rather than that ground. Consumers who set
513
+ `--ds-button-label-color-disabled` are unaffected.
514
+ ### Changed
515
+
516
+ - **A disabled `ds-icon-button variant="standard"` mixes its glyph toward the surface too.** It is
517
+ the only icon-button variant with neither a fill nor a border, so the glyph's colour is the whole
518
+ disabled signal — and the shared fixed-lightness recipe could not carry it in dark, where the
519
+ enabled icon is already light (OKLCH L 80%) and a disabled one pinned at L 70% sat **1.46:1** away.
520
+ The new default is `color-mix(in srgb, <icon> 40%, var(--surface-default))`, the same mix the
521
+ borderless button variants take, which picks its direction per theme: light **4.17 → 5.19:1**, dark
522
+ **1.46 → 3.58:1**. Scoped to `standard` deliberately — `filled`'s icon is `--c-on`, and white
523
+ mixed into a white surface does not move at all. `--ds-icon-button-icon-color-disabled` is the same
524
+ hook as before and still wins; only the default under it changed.
525
+
526
+ - **If you EXTEND a DS field component, read this before trusting `class-surface`.** The report
527
+ against 0.10.0 says fourteen field components LOST eight members each — `hint`, `error`,
528
+ `warning`, `errors`, `invalid`, `touched`, `reserveMessage` and `reserveMessageResolved`.
529
+ **Nothing was removed.** Those inputs were declared once per component and are now declared once in
530
+ total, on a new internal `DsFieldBase`, which every field reaches either directly or through
531
+ `DsControlValueAccessor` / `DsBooleanControlValueAccessor`. All fourteen still carry all eight by
532
+ inheritance, so a template binding, a TS read and an existing `override` all behave exactly as
533
+ before. The tool counts declarations per FILE, and `migrations/AUTHORING.md` already names a member
534
+ that moved to a base class as one of the two things it cannot see — this release is that case.
535
+ What genuinely grew is smaller: **eight bordered fields gained `success`** (`ds-autocomplete`,
536
+ `ds-color-picker`, `ds-date-picker`, `ds-multi-select`, `ds-otp-input`, `ds-select`,
537
+ `ds-textarea`, `ds-time-picker`), `ds-input` having had it all along. `ds-segmented`
538
+ is the tenth grown class and the one with real new surface — joining the form systems gave it
539
+ `label`, `disabled`, `isDisabled`, `message`, `invalidResolved`, `fieldMessage`, `hintId` and
540
+ `uid`. A subclass declaring
541
+ `success` on one of those eight now fails with TS4114; declaring any of the eight moved names still
542
+ collides exactly as it did, because an inherited member collides the same way an own one does.
543
+ `DsFieldBase` is internal and deliberately not exported — it holds only the inputs every field has,
544
+ which is why `success`, `label`, `required` and `optional` stayed on the components.
545
+
546
+ ### What you can now DELETE
547
+
548
+ None of this is required — skipping it leaves working code that is merely redundant. Each row is a workaround this release made unnecessary.
549
+
550
+ | If you have | Delete it, because |
551
+ | --- | --- |
552
+ | A `?? ''` guard wrapped around a message binding - `[error]="form.errors?.message ?? ''"` - added because a null pushed into `hint` / `error` / `warning` / `success` threw a TypeError during render. | nothing - bind the expression directly, the inputs absorb null now |
553
+
11
554
  ## 0.10.0 — 2026-08-18
12
555
 
13
556
  ### Added
@@ -78,10 +621,7 @@ While the package is on `0.x`, minor releases may contain breaking changes.
78
621
  The two signals are read-only — a subclass that used to `.set()` them (they were protected writables)
79
622
  drives them through `runExport()` now.
80
623
 
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,
624
+ - **`provideDsConfig` answers seven more inputs, so an app stops restating itself.** Five new sections: `control.size` (honoured by button, icon-button, input, textarea, select, autocomplete, search,
85
625
  date/time picker, number stepper, checkbox, radio, switch and field-group), `card.elevation` and
86
626
  `card.padding`, `table.stickyScrollbar` and `table.bordered`, `icon.size`, and `badge.withDot`.
87
627
  Precedence is **input → config → built-in**, so a screen that differs still binds the attribute and
@@ -128,7 +668,7 @@ While the package is on `0.x`, minor releases may contain breaking changes.
128
668
 
129
669
  - **`--ds-dropdown-panel-radius` — the lever 0.9.0's notes promised and never shipped.** That release
130
670
  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
671
+ so the advice did nothing. This is the honest version, and it is
132
672
  panel-level rather than per-component on purpose: retuning one picker's corner is not a thing to
133
673
  encourage, while `--ds-radius-panel` moves modal, popover and date picker too. Defaults to that
134
674
  role, so an untouched theme is unchanged, and it is forwarded onto the portaled pane — scope it with
@@ -453,6 +993,12 @@ While the package is on `0.x`, minor releases may contain breaking changes.
453
993
  specificity. **If you deliberately suppressed a focus ring** by leaving an element unstyled, it will now
454
994
  show one; give that element `box-shadow: none` explicitly. Note the rule also drops the outline such an
455
995
  element used to get from the browser, so if an `outline` was what you wanted there, declare it yourself.
996
+ **The case that actually bites, added 2026-08-21 after a consumer hit it fourteen times:** an app rule
997
+ that styles `:focus-visible` with an **`outline` only**. That rule keeps winning on `outline`, but it
998
+ says nothing about `box-shadow`, so the base rule still supplies one and the element renders **both** —
999
+ a second ring in the app's colour around the DS ring. Nothing fails a build and nothing greps for it:
1000
+ the app rule looks untouched because it is. Add `box-shadow: none` to that rule, or — better, and what
1001
+ this release is for — delete the rule and retint the DS ring through `--ds-control-focus-shadow`.
456
1002
 
457
1003
  - **A disabled `ds-button` / `ds-icon-button` now reads as disabled on a COLOURED accent.** One label recipe
458
1004
  for every variant — `oklch(from accent 70% 0.035 h)` — replacing the 58% default, and on `ds-button` the
@@ -558,6 +1104,35 @@ While the package is on `0.x`, minor releases may contain breaking changes.
558
1104
 
559
1105
  ### Changed
560
1106
 
1107
+ - **The seven inputs every field shares are declared once, in `DsFieldBase`.** `hint`, `error`,
1108
+ `warning`, `errors`, `invalid`, `touched` and `reserveMessage` — plus the `reserveMessageResolved`
1109
+ helper — were hand-copied into all fourteen fields, 98 declarations. **Nothing about the public API
1110
+ changed:** every input keeps its name, type, default and documentation, and the docs API tables are
1111
+ byte-identical apart from the eight new `success` rows (verified by diffing the generated
1112
+ reference: 0 lost, 8 gained).
1113
+ **Why it is worth knowing anyway:** the duplication had already drifted twice — `success` was
1114
+ missing from eight fields, and `ds-date-picker` had quietly moved to a different `invalid` source.
1115
+ A new state added to the base now reaches every field at once.
1116
+ `DsControlValueAccessor` and `DsBooleanControlValueAccessor` extend the base (so single inheritance
1117
+ still holds for the thirteen fields that already extended one of them) and `ds-radio` extends it
1118
+ directly. Only the UNIVERSAL inputs moved: `success`, `label`, `required` and `optional` stay on the
1119
+ components, because they exist on 9, 9, 7 and 5 fields respectively and lifting them would hand a
1120
+ checkbox a `success` or a slider a `label` it never had.
1121
+
1122
+ - **`ds-icon-button` with `variant="standard"` mixes its disabled glyph toward the surface too.**
1123
+ New default on that variant only: `color-mix(in srgb, <icon colour> 40%, var(--surface-default))`.
1124
+ Same defect as ghost, and it matters more here — there is no word to read, just a 16px glyph.
1125
+ Measured: light **4.17 → 5.19:1**, dark **1.46 → 3.58:1**. Light was already healthy, because the
1126
+ enabled glyph is `--text-secondary` at OKLCH L 35% and the old recipe moved it to L 70%; **dark was
1127
+ the break**, where the enabled glyph is L 80% and a disabled one pinned at L 70% left ten points
1128
+ and a 1.46:1 gap.
1129
+ **Scoped to `standard` deliberately, and this is the trap worth knowing:** the resolver is declared
1130
+ once on the base and no variant overrode it, so touching the base would have hit `filled` too —
1131
+ whose glyph is `--c-on`, i.e. white, and white mixed into a white surface does not move at all,
1132
+ which would have put an invisible white glyph on a pale disabled fill. `filled`, `tonal` and
1133
+ `outlined` keep the base recipe unchanged. Consumers who set
1134
+ `--ds-icon-button-icon-color-disabled` are unaffected.
1135
+
561
1136
  - **`avatarTint` switches from OKLCH to `hsl(H 50% 62%)` with white initials, always.** The seeded
562
1137
  tints read as dull, and every set of initials came out black. The auto-contrast was not the fault:
563
1138
  measured across the hue circle, the old `oklch(62% 0.14 h)` put every hue's luminance between 0.218
@@ -707,6 +1282,32 @@ While the package is on `0.x`, minor releases may contain breaking changes.
707
1282
  could `.set()` — and a plain `private pending: … = null` is not a field the parser recognises, which
708
1283
  is how `SearchComponent`'s `pending` and `pushed` sit outside its reported seven.
709
1284
 
1285
+ ### What you can now DELETE
1286
+
1287
+ None of this is required — skipping it leaves working code that is merely redundant. Each row is a workaround this release made unnecessary.
1288
+
1289
+ | If you have | Delete it, because |
1290
+ | --- | --- |
1291
+ | A `ResizeObserver`, a container query or a hand-tuned per-breakpoint `maxVisibleChips` number, keeping a chip trigger on one line. | `maxVisibleChips="fit"`, which re-splits on any width change rather than at the breakpoints you listed |
1292
+ | A `max-height` plus `overflow: hidden` on a chip trigger, stopping it growing a line per selection - it clips a chip mid-glyph and hides the count. | `maxVisibleChips` (a number, or `"fit"`), which drops whole chips and reports how many are hidden |
1293
+ | Your own `max-height` on a logo projected into `ds-sidenav`'s `[brand]` slot, or a wrapper sized to hold it. | `--ds-sidenav-brand-max-height` (default `none`, so nothing changes until you set it) |
1294
+ | A global rule against `.ds-dropdown-panel` or `.cdk-overlay-pane` to change a dropdown corner. | `--ds-dropdown-panel-radius`, which scopes to one picker when written under a component selector |
1295
+ | A query for `ds-autocomplete`'s inner `<input>` plus a synthetic `input` event, clearing leftover filter text after a pick. | `clear()` - and the component clears that text itself now |
1296
+ | A local `.link-button` class, or a padding / border / background / font reset on `button.link` in your overrides. | the global `.link` class with `.inline` / `.standalone` / `.sm` / `.xs` |
1297
+ | A `[dsStatValue]` projection used only to set `white-space: normal` or a smaller font size on a TEXT value. | the two hooks on the ordinary `value` input - keep the slot for a value that is genuinely another component, like a badge |
1298
+ | A wrapper around `ds-search` adding a typing debounce (typically 200ms) with an immediate path when the field empties. | `[debounce]`, which does both plus the Enter flush |
1299
+ | `--ds-button-height` / `--ds-button-font-size` / `--ds-button-pad-x` pinned under `ds-filter-bar` to force its trigger smaller. | `triggerSize="sm"` |
1300
+ | `[dividers]="false"` repeated on every modal (one consumer had 41), or a reach into `.modal > .header` / `.body` / `.actions` with `!important` because hiding the rules left the padding stacked. | `provideDsConfig({ modal: { dividers: false } })`, which drops the rules AND the padding that existed to clear them |
1301
+ | A helper keeping the last visited tab per path in `sessionStorage`. | `rememberLastTab` on `ds-tabs` (needs `urlParam`, which supplies the names) |
1302
+ | An adapter component that injects a brand object and fans it out into `brand` / `logoLetter` / `tagline` bindings on each auth screen. | `provideDsConfig({ brand: … })`; the accent stays a `[dsBrandName]` projection instead of a `brandAccent` string plus an `indexOf` split |
1303
+ | The `ds-avatar` wiring around your own initials helper (the helper itself stays yours). | `[name]` plus one `[initialsRule]` |
1304
+ | An attribute repeated identically on every element - one consumer binds `[stickyScrollbar]="true"` on all 35 of its tables and `size="sm"` on 146 buttons. | `provideDsConfig` with the matching section (`table`, `control.size`, …) |
1305
+ | A button wired to `exportCsv()` on a SERVER-PAGED table - it serialises the rows the table holds, so the file is one page. | `runExport()` with an `exportFetcher` |
1306
+ | The computed beside every list table - `items().length > 0 ? 'overlay' : 'skeleton'` - one consumer feature carried three copies of it. | `[loading]="true"`, which resolves the treatment itself; pin a value only where you mean to override the rule |
1307
+ | An override retuning `--opacity-muted` to compensate for a washed-out disabled state. That token is a de-emphasis level for hints and secondary text and carries no disabled state at all - and on `ds-button` / `ds-icon-button` it was always inert, because neither ever read it. | `--ds-button-label-color-disabled` / `--ds-icon-button-icon-color-disabled` |
1308
+ | A `::ng-deep ds-table { .table th, .table td { width: 1%; white-space: nowrap } }` override - the shrink-to-content idiom. | `TableColumn.width: 'content'` |
1309
+ | A `stopPropagation()` on a control inside a clickable row, added so the row would not steal the control's KEY. Read each hit before deleting: a CLICK still bubbles (`onRowClick` only skips a target inside an `<input>`), so a click-path guard stays. | nothing on the key path - `onRowKey` now requires `target === currentTarget` |
1310
+
710
1311
  ## 0.9.1 — 2026-08-10
711
1312
 
712
1313
  ### Added
@@ -808,14 +1409,14 @@ genuine gap worth reporting.
808
1409
 
809
1410
  ### Changed (breaking, visual)
810
1411
 
811
- - **The `ds-select` / `ds-multi-select` dropdown panel has a 12px corner, was 8px.** It was the one panel
812
- outside the radius role layer — modal, popover, date picker, time picker, autocomplete, bottom sheet, card,
813
- stat and page footer all resolve `--ds-radius-panel` — so it disagreed with its siblings by 4px and could
1412
+ - **The `ds-select` dropdown panel has a 12px corner, was 8px.** It was the one panel outside the
1413
+ radius role layer — modal, popover, date picker, time picker, autocomplete, bottom sheet, stat and
1414
+ page footer all resolve `--ds-radius-panel` — so it disagreed with its siblings by 4px and could
814
1415
  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.)_
1416
+ which moves every panel together; there is no per-panel token for the select, and
1417
+ `--ds-select-panel-radius` does not exist. `ds-multi-select` is not part of this: its panel is a
1418
+ separate element with a hardcoded `border-radius: var(--radius-md)` that the shared rule does not
1419
+ reach, so it stays at 8px.
819
1420
 
820
1421
  - **Seven exit `@keyframes` are gone, replaced by four global presets.** `modal-out`, `ds-sheet-fade-out`
821
1422
  and `drawer-scrim-out` become `ds-fade-out`; `ds-sheet-down` and the four `drawer-panel-close-*` become
@@ -2120,6 +2721,15 @@ genuine gap worth reporting.
2120
2721
  scrim click-to-close, panel-scoped plus document-level Escape, `animationend` teardown, and the focus
2121
2722
  trap are all unchanged.
2122
2723
 
2724
+ ### What you can now DELETE
2725
+
2726
+ None of this is required — skipping it leaves working code that is merely redundant. Each row is a workaround this release made unnecessary.
2727
+
2728
+ | If you have | Delete it, because |
2729
+ | --- | --- |
2730
+ | A logo overlaid or absolutely positioned on top of ds-sidenav's brand row, written when there was no slot for one. | project it into `[brand]` |
2731
+ | A scrollTop pin or a scroll-lock hack written against the content jolt an opening sheet used to cause in a shell that is a containing block for fixed descendants. | nothing - the entering panel no longer contributes that overflow |
2732
+
2123
2733
  ## 0.6.1 — 2026-07-16
2124
2734
 
2125
2735
  ### Fixed