@ids-group-ltd/ids-design-system 0.8.0 → 0.9.1

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,454 @@ While the package is on `0.x`, minor releases may contain breaking changes.
8
8
 
9
9
  ## Unreleased
10
10
 
11
+ ## 0.9.1 — 2026-08-10
12
+
13
+ ### Added
14
+
15
+ - **The token and component reference now documents every public token and prop** — 41 were
16
+ shipping with a name, a type and no description: 10 `--ds-*` tokens (the whole
17
+ `--ds-password-rules-*` set among them, plus `--ds-multi-select-panel-bg-color` and
18
+ `--ds-menu-item-radius`) and 31 inputs and outputs across `ds-calendar-day`, `ds-time-columns`,
19
+ `ds-field-message`, `ds-divider`, `ds-sidenav-footer` and the three layout primitives. **Three of
20
+ them were guessable wrong**, so check yours if you use them: `ds-time-columns` `value` is always
21
+ `HH:mm` in 24h and `format` changes only the DISPLAY, so a 12h picker still emits 24h;
22
+ `minTime`/`maxTime` disable the out-of-range rows rather than removing them, so the columns keep
23
+ their height as a bound moves; and `ds-calendar-day` `tabIndex` is a roving tabindex (one cell at
24
+ 0, the rest at -1), not a tab position you set per day. No behaviour changed — only what the
25
+ reference tells you.
26
+
27
+ ### Fixed
28
+
29
+ - **The changelog page on the docs site was rendering with browser defaults.** Its markdown styles
30
+ were scoped by emulated encapsulation, which stamps its attribute on the container but not on the
31
+ nodes the markdown renderer produces — so every rule in that block matched nothing: measured
32
+ border-top 0px and margin-top 0px on the version headings, and `h3` white instead of
33
+ `--text-secondary`. Docs-site only, nothing in the package.
34
+
35
+ ### Changed
36
+
37
+ - **`migrations/<version>.json` now carries the delete-list, so an upgrade tool can act on it.**
38
+ Each version's manifest gains `DELETE-LIST: if you have <X> -> <why it can go>` entries — 21 of
39
+ them for 0.9.0 — naming the workarounds that release made unnecessary, from the
40
+ `.button.button.button` triple-class to hand-binding `[value]`/`(valueChange)` on every field of a
41
+ signal form. They existed for 0.9.0 but only in a prose file the tooling does not read, so nothing
42
+ applied them. **Nothing here is required**: skipping it leaves working code that is merely
43
+ redundant. The same table is in this file under 0.9.0 if you would rather read than run.
44
+ `migrations/unreleased/README.md` no longer ships — it duplicated the manifest and had already gone
45
+ stale inside one release.
46
+
47
+ ## 0.9.0 — 2026-08-10
48
+
49
+ ### What you can now DELETE
50
+
51
+ The half a release note usually leaves out. Two dogfooding audits (mm-ecm 2026-08-06, mm-broker
52
+ 2026-08-07) read consumer stylesheets as a record of what this library made them write, and both
53
+ found the same thing: **most of the workarounds were written against hooks that already existed** —
54
+ the consumer had no signal that anything had been tokenised since. That is a failure of these notes,
55
+ not of the consumer. None of this is required; skipping it leaves working code that is merely
56
+ redundant.
57
+
58
+ | If you have | Delete it, because |
59
+ | --- | --- |
60
+ | `.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"]` |
61
+ | `--radius-sm: 0` to square a checkbox | `--ds-checkbox-radius` |
62
+ | `.title.title { font-size }` inside a modal | `--ds-modal-title-font-size` |
63
+ | Pagination label type overrides | `--ds-pagination-label-*` |
64
+ | `.size { display: none }` on a pager | `[showPageSize]="false"` — and it is now forwarded through `ds-table` too |
65
+ | `.actions:empty { display: none }` on a modal | The library already ships it |
66
+ | `--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 |
67
+ | A defensive hover rule on the selected dropdown row | The `:not(.is-selected)` branch already handles it |
68
+ | `ds-menu-divider { padding: 0 }` | `--ds-menu-divider-spacing`, which already defaults to 0 |
69
+ | 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 |
70
+ | A global rule squaring `.ds-overlay-pane` | Radius and elevation roles now travel onto portaled panes when the host overrides them |
71
+ | Absolutely positioning a search glyph over an autocomplete, or hiding `.autocomplete-chevron` | `dsAutocompletePrefix` and `[showChevron]="false"` |
72
+ | Querying the autocomplete's inner `<input>` and dispatching a synthetic `input` event to clear it | `clear()` |
73
+ | A hand-built KPI tile whose value is a badge | `ds-stat` takes a projected `[dsStatValue]` |
74
+ | 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 |
75
+ | 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 |
76
+ | `[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 |
77
+ | `white-space: normal` forced onto a badge in a table cell | `--ds-badge-white-space` |
78
+ | `::ng-deep .card { height: 100% }` for equal-height cards | The card's box fills a stretched host on its own |
79
+ | `!important` on `ds-table` cell padding under `density="compact"` | Compact no longer out-specifies the padding hooks |
80
+ | 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` |
81
+
82
+ **To sweep for the rest:** grep your styles for `::ng-deep`, `!important` and any selector naming a
83
+ DS internal class (`.button`, `.trigger`, `.option`, `.modal`). Each hit is either a row above or a
84
+ genuine gap worth reporting.
85
+
86
+ ### Changed (breaking, behaviour)
87
+
88
+ - **`ds-table` `sortMode` and `filterMode` default to `'server'`, were `'client'`.** Server-paged is the
89
+ normal case, and there the old default was actively wrong: the table sorted the current page, so the
90
+ rows looked sorted and were not — a dev warning existed only to say so. An undeclared table now emits
91
+ `(sortChange)` / updates `columnFilters` and reorders nothing itself. **A table that holds every row
92
+ must now declare `sortMode="client"` / `filterMode="client"`**; the dev warning has been turned around
93
+ to catch exactly that case (no `total` bound + sortable or filterable columns + no declared mode).
94
+
95
+ ### Changed (breaking, visual)
96
+
97
+ - **The `ds-select` / `ds-multi-select` dropdown panel has a 12px corner, was 8px.** It was the one panel
98
+ outside the radius role layer — modal, popover, date picker, time picker, autocomplete, bottom sheet, card,
99
+ stat and page footer all resolve `--ds-radius-panel` — so it disagreed with its siblings by 4px and could
100
+ not be retuned through the role consumers are told to use. Restore with
101
+ `--ds-select-panel-radius: 8px`, or `--ds-radius-panel: 8px` to move every panel together.
102
+
103
+ - **Seven exit `@keyframes` are gone, replaced by four global presets.** `modal-out`, `ds-sheet-fade-out`
104
+ and `drawer-scrim-out` become `ds-fade-out`; `ds-sheet-down` and the four `drawer-panel-close-*` become
105
+ `ds-slide-edge-out`. They were view-encapsulated, so referencing one was only possible from a global
106
+ stylesheet — but if you did, that is the mapping. Nothing about the rendered motion changed.
107
+
108
+ - **`ds-search` is 40px tall by default, was 36px.** It was the only control in the library on that
109
+ height — `ds-button`, `ds-input`, `ds-select` and both pickers all resolve `--field-h-md` — so a search
110
+ box in a toolbar sat a step short of everything beside it. All three sizes now come off the field scale
111
+ (sm 32 / md 40 / lg 48; only md moved). Restore with `ds-search { --ds-search-height: 36px; }`. The
112
+ height also falls through `--ds-field-height` now, so one token levels a whole toolbar.
113
+
114
+ - **The global `--search-h` token is gone.** It existed only to hold that 36px and nothing reads it.
115
+ Use `--ds-search-height` to retune search alone, or `--ds-field-height` for the family.
116
+
117
+ ### Changed
118
+
119
+ - **`--ds-radius-inner` now reaches the small affordances it was written for.** Thirty-three reads across
120
+ fifteen component stylesheets took `var(--radius-sm)` directly — dropdown options, field clear buttons,
121
+ calendar days, chips, tag and toast close buttons — so the role a consumer is told to retune reached
122
+ exactly one component. Nothing moves (the role's default IS `--radius-sm`, verified by measuring a page
123
+ before and after), but it changes what a square brand costs: zeroing the three radius roles used to leave
124
+ five surfaces rounded and now squares every one. Five focus-ring radii inside `:focus-visible` keep
125
+ following the raw scale deliberately — a ring traces a box, it is not a surface a brand designs.
126
+
127
+ - **`ds-auth-layout` compresses its own chrome on a short viewport, so the layout is never the reason a
128
+ card scrolls.** Block padding, the column gap, the letter-mark tile and the masthead's inner gap clamp
129
+ against `svh`. At ~330px of viewport — a landscape phone — that furniture costs ~131px instead of ~219px.
130
+ Every multiplier reaches its maximum at a viewport **800px tall or more** — a viewport height, not a
131
+ screen size: a 1366x768 laptop sits near 630px once browser and OS chrome come off, and a 1080p screen at
132
+ 150% display scaling near 585px, so a good many desktops render the compressed furniture too.
133
+ **Type is deliberately excluded.** An earlier draft clamped the wordmark and the tile's glyph as well;
134
+ both were measured to buy zero vertical space — the wordmark shares a flex row with the tile, whose height
135
+ exceeds the wordmark's line box at every viewport height, and the glyph sits in a fixed-size grid box —
136
+ while shrinking the brand against a fixed 14px tagline, worst for the users who scale their display up.
137
+ Both are back to the fixed sizes 0.8.0 ships.
138
+ `svh` rather than `dvh` because the dynamic unit changes as a mobile URL bar hides, which would re-space
139
+ the column mid-scroll; `min-height` stays on `dvh` so no strip of body background shows when the bar
140
+ retracts. New opt-outs: `--ds-auth-layout-pad-block` and `--ds-auth-layout-mark-size` (set
141
+ either, or the existing `-gap`, to a fixed value and that dimension stops compressing). A card taller than
142
+ the space left still scrolls — deliberately, because the alternative (pinning the masthead and footer out
143
+ of the flow) frees more room but lets chrome overlap a tall form.
144
+
145
+ - **`ds-auth-layout` — a round of fixes from an audit of the above.** All additive or corrective; nothing
146
+ to migrate. The letter-mark is now `aria-hidden`, so a screen reader announces "MyAdmin" rather than
147
+ "A MyAdmin"; it also carries `flex-shrink: 0`, so a long wordmark can no longer squash the square tile
148
+ into a rectangle. `logoLetter` on its own renders its tile instead of nothing (the outer gate never
149
+ tested it). The glyph is taken with a code-point split rather than `charAt(0)`, which returned half a
150
+ surrogate pair for a brand starting with an emoji. `box-sizing: border-box` is declared on the host
151
+ rather than inherited, because the documented à-la-carte style path omits `styles/reset` and without it
152
+ `min-height: 100dvh` plus the block padding overflows by exactly that padding — the scrollbar this
153
+ component exists to avoid. The four `env(safe-area-inset-*)` calls gained `0px` fallbacks and moved to
154
+ physical `padding-left`/`padding-right`, since the safe area belongs to the device and must not swap
155
+ sides with text direction; note the insets are inert unless the **host app** sets `viewport-fit=cover`
156
+ in its viewport meta, which the library cannot do and did not previously say. New tokens, both
157
+ defaulting to today's behaviour: `--ds-auth-layout-mark-radius` (the tile's radius was the one value
158
+ with no override hop) and `--ds-auth-layout-brand-max-height` (`none` by default — set it to cap a
159
+ projected `[brand]` logo, which nothing constrained). New input `landmark` (`'none'` by default): the
160
+ card holds the whole content of an auth screen but `ds-card` renders an `<article>`, which is not a
161
+ landmark, so `landmark="main"` gives a screen-reader user something to jump to on a standalone auth
162
+ page. It is opt-in because the layout is also embedded inside pages that already own a `main`.
163
+
164
+ - **BREAKING: `ds-auth-shell` is renamed `ds-auth-layout`** (`AuthShellComponent` → `AuthLayoutComponent`,
165
+ and `--ds-auth-shell-*` → `--ds-auth-layout-*`). "Shell" is not this library's word for a layout — the
166
+ app-level one was renamed `ds-app-shell` → `ds-app-layout` back in 0.7.0, and shipping an auth counterpart
167
+ called a shell in 0.8.0 reintroduced the split vocabulary that rename existed to remove. Mechanical:
168
+ rename the tag, the class and the six tokens. Nothing about the behaviour or the slots changes.
169
+
170
+ ### Added
171
+
172
+ - **Exit motion is swappable, the way entrances already were** — `--ds-modal-leave-keyframes`,
173
+ `--ds-drawer-leave-keyframes` and `--ds-bottom-sheet-leave-keyframes`, plus four global presets that
174
+ mirror the entrance vocabulary (`ds-fade-out`, `ds-scale-out`, `ds-slide-out`, `ds-slide-edge-out`).
175
+ This was blocked by a real constraint the code documented: teardown matched the animation NAME on
176
+ `animationend`, so renaming the keyframe broke closing entirely. The guard now checks that the event came
177
+ from the animated element rather than from a child, which frees the name — and that same check collapsed
178
+ the drawer's four direction-specific exits into one preset, since an exit reads `--_ds-exit-x/y/scale`
179
+ and falls back to the matching `--_ds-enter-*`. Point a token at your own **global** `@keyframes`; a
180
+ component-scoped name is renamed by Angular and will not resolve.
181
+
182
+ - **Signal Forms bind to every DS control, with no wrapper and no adapter** — `<ds-input [formField]="f.email" />`
183
+ and the form owns the value, the validation, `touched`, `disabled` and the error text. This was very nearly
184
+ true already and nobody knew: `FormValueControl` requires exactly one member, a `value` `model()`, and all
185
+ fifteen controls had it. Measured across all of them — thirteen bound with no library change at all. What
186
+ was fixed here: `min`/`max`/`maxLength` on `ds-input`, `ds-textarea` and `ds-number-stepper` now accept
187
+ `undefined` on the write side (the binder sends it for an unset bound; read types are untouched);
188
+ `readonly` joins `ds-input`, `ds-textarea` and `ds-select` as the contract spelling of the existing
189
+ `readOnly`, because signal forms binds by NAME and a `readonly()` rule was reaching nothing; `minLength`
190
+ and `pattern` are new native attributes on `ds-input` and `ds-textarea`; `hidden` is declared on both
191
+ control-value-accessor bases, so a `hidden()` rule removes the control on all thirteen that carry one; and
192
+ `focus()` resolves the element that holds the value, so `focusBoundControl()` reaches the stepper's number
193
+ box rather than its minus button and the tabbable radio rather than the first in the DOM. Not implemented:
194
+ `dirty`, `pending`, `disabledReasons`. Reactive and template-driven forms are untouched. Docs: **Practice →
195
+ Signal Forms**, with a live form and a contract table stating the measured state.
196
+
197
+ - **`ds-modal` takes a `[title-badge]` slot and a `subtitle`.** Two consumer screens had abandoned
198
+ `ds-modal` and hand-rolled a `.scrim` + `.panel` because the header could only hold one string — losing
199
+ the focus trap, focus restore, the scroll lock, Escape, the enter/leave animation and, in one case, the
200
+ footer, which put a destructive action beside the close button. Same shape as `ds-page-header`; `title`
201
+ stays the accessible name, so projected markup never enters `aria-labelledby`. Two tokens:
202
+ `--ds-modal-subtitle-text-color` and `-font-size`.
203
+
204
+ - **`[dividers]` on `ds-modal` / `ds-modal-card`, default `true`.** `[dividers]="false"` drops the header
205
+ and actions rules AND the vertical padding that existed to clear them, because those are one design
206
+ decision. Two consumers had set `--ds-modal-divider: transparent` and were left with a 35px gap where 16
207
+ was wanted; one needed `!important` to win it back.
208
+
209
+ - **`ds-table`: the rest of what mm-broker's fork did that the base could not.** Keyboard column resizing —
210
+ the handle is a focusable `role="separator"` with Arrow (16px), PageUp/PageDown (64px) and Home to hand
211
+ the column back to automatic sizing; a drag handle that answered only to a pointer made a resizable column
212
+ unusable without a mouse. `exportFetcher` may now resolve a `Blob` or a URL as well as rows, for a file
213
+ the backend already formatted, and `exportFailed` emits the rejection — swallowing it made a failed export
214
+ indistinguishable from a slow one. Two box tokens: `--ds-table-min-width` (a readability floor, default 0)
215
+ and `--ds-table-hscroll-bottom` (offsets the sticky scrollbar out of a padded container, default 0).
216
+
217
+ - **The three `ds-modal` regions take their padding from tokens** — `--ds-modal-pad-x` for the gutter all
218
+ three share, plus `--ds-modal-header-pad-y`, `-body-pad-y` and `-actions-pad-y`. Two consumers were
219
+ rewriting these, one with `!important`, because the regions are padded for a divider-separated layout:
220
+ set `--ds-modal-divider: transparent` and you are left with spacing sized for dividers that are no
221
+ longer there. Nothing moves by default. Note the tokens go on `ds-modal` AND `ds-modal-card` — a dialog
222
+ opened through `ModalService` renders the card with no `ds-modal` ancestor.
223
+
224
+ - **`maxItems` on `ds-breadcrumbs`** — collapses the middle of a deep trail into a crumb that says how
225
+ many it stands for, keeping the first and, crucially, the LAST. Without a cap the row is `nowrap` with
226
+ `overflow: hidden`, so an overlong trail is clipped from the END — hiding the current page, the one
227
+ crumb the reader needs most. Opt-in; every crumb still renders by default.
228
+
229
+ - **Dev warnings no longer repeat themselves.** Every component with one wrote the same four lines around
230
+ it — `isDevMode`, an `effect`, a condition, a `console.warn` — and each copy shared the same flaw: the
231
+ effect re-runs when ANY signal it read changes, so a warning about a static misconfiguration could be
232
+ logged again on every keystroke. They now go through one internal helper that fires at most once per
233
+ message. Eleven hand-written warnings across `ds-button`, `ds-stat` and `ds-table` moved onto it —
234
+ ten call sites at HEAD, since the table gained more with lazy loading. `ds-tabs` keeps its own, because
235
+ its effect also owns registry bookkeeping that a plain warning cannot express.
236
+
237
+ - **`maxVisibleChips` on `ds-autocomplete`** — caps the chips in the trigger and collapses the rest into
238
+ "+N more". Without it a multi-select trigger grows a line per selection and pushes the rest of the form
239
+ down the page, which is how it was reported. Same input name, same transform and same wording as
240
+ `ds-multi-select`, which already had it — the two multi-value pickers should not diverge on this.
241
+ Backspace still removes the last SELECTED chip, not the last visible one.
242
+
243
+ - **`ds-stat` takes a projected value** — `[dsStatValue]` for a tile whose headline is a badge, a status
244
+ dot or anything a number slot cannot hold. `value` is now optional and acts as the fallback, the same
245
+ shape `[delta]` already had; existing tiles are untouched. The slot is namespaced on purpose: twenty
246
+ components in this library have a `value` input, so a bare `value` attribute would have set theirs to
247
+ the empty string on the way past. A dev warning fires if `unit` is set with no `value`, since a
248
+ projected headline owns the whole line and the suffix would silently vanish.
249
+
250
+ - **The package now ships `design-system.md` and `components.md`.** `design-system.md` is no longer a
251
+ catalogue: it carries the RULES — which spacing token goes between what, which type role a piece of
252
+ text takes, the field-height contract, who owns a gap, and how to override a component (including the
253
+ two things that break it: reaching for an internal class, and portaled panels). The 491-line inventory
254
+ it used to be moved to `components.md`. Both are readable from `node_modules`, so a consumer's agents
255
+ and tooling can follow the system instead of guessing plausible token values.
256
+
257
+ - **`ds-tabs` warns when two strips claim the same `urlParam`.** Both write the same query parameter, so
258
+ each erases the other's tab and a reload restores whichever wrote last — nothing throws and the URL
259
+ looks plausible. It is the easy mistake when turning `urlParam` on across an app, because `"tab"` is the
260
+ obvious name every time. Dev-mode only.
261
+
262
+ - **Selected dropdown rows have their own hooks** — `--ds-option-selected-bg-color`, `-label-color`,
263
+ `-bg-color-hover` and `--ds-option-check-color`, defaulting to the theme roles they used to read
264
+ directly. A brand that wanted a different selected treatment previously had to RETARGET `--primary-*`
265
+ inside `.ds-dropdown-panel` and then track what else in the panel read the same role. Panel-level: one
266
+ partial paints select, autocomplete and multi-select alike. Nothing moves by default.
267
+
268
+ - **`ds-field-group` — several controls in one bordered box** (`select + input`, `input + button`,
269
+ `input + select`). The group owns the border, the radius, the divider and a single `:focus-within` ring;
270
+ the controls inside render naked. Segments hug their content, `grow` takes the slack. `size` uses the
271
+ field height scale, plus `invalid` and `fullWidth`. A control knows it is a segment by injecting
272
+ `DS_FIELD_GROUP` rather than being told with an input — the alternative is manual, and one segment where
273
+ it was forgotten draws its own border mid-row. Six controls can be segments: `ds-input`, `ds-select`,
274
+ `ds-search`, `ds-autocomplete`, `ds-date-picker` and `ds-button`. Not `ds-number-stepper` (a composite
275
+ already) or `ds-multi-select` (its chips wrap, which a fixed-height row cannot take). Grouped controls must not carry a `label` or `hint` — the message row
276
+ would break the glued line, so it is suppressed and a group-level one is not built.
277
+
278
+ - **`ds-table` lazy loading** — `[lazy]` plus a `(lazyLoad)` output emitting `{ first, rows }` for the
279
+ range now on screen. `data` becomes a sparse array `total` long: write each fetched row at its absolute
280
+ index, and every gap inside the window renders a skeleton row until it arrives. The scroller is sized
281
+ from `total` rather than from what has arrived, so the scrollbar tells the truth from the first frame.
282
+ Needs `virtualScroll` (there is no window to fetch against otherwise) and `total`; a request is not
283
+ re-sent while the range it covered is still on screen. Dev warnings cover all three ways to wire it
284
+ wrong, including `sortMode="client"`, which would sort only the rows that happen to have loaded.
285
+
286
+ - **`[quiet]` on `ds-menu-item`** — a muted row for a secondary action like "Sign out" under a divider,
287
+ the sibling of the existing `[error]`. Recolouring one item was previously impossible through the
288
+ token: `--ds-menu-item-label-color` resolves on the host against the value inherited from `ds-menu`, so
289
+ setting it per item did not win and the colour had to go on the inner element. `[error]` still wins if
290
+ both are set. Colour comes from `--ds-menu-item-quiet-label-color`.
291
+
292
+ - **21 hooks for type and box values that a `font:`/`border:`/`padding` shorthand had swallowed.** Same
293
+ shape every time: the value sat inside a shorthand, so overriding the one property meant a selector
294
+ out-ranking the shimmed component rule. `ds-description-item` completes the eyebrow set both halves
295
+ (`--ds-description-list-term-weight` / `-tracking` / `-transform`, `-details-font-size` / `-weight`) —
296
+ the same five `ds-field-label` and the modal eyebrow already exposed. `ds-segmented` gains
297
+ `--ds-segmented-btn-border` (for a hairline chip row), `-btn-pad-x` and label type; `ds-tabs` gains
298
+ `--ds-tab-pad-top` / `-bottom` (an underline tab wants bottom-only and could not say so), label type,
299
+ `--ds-tabs-strip-gap` and `--ds-tabs-panel-pad-top`; `ds-menu` gains item padding, item label type and
300
+ `--ds-menu-gap`; `ds-checkbox` gains `--ds-checkbox-label-weight`, the third label property where size
301
+ and colour were already hookable. Every default reproduces today's value.
302
+
303
+ - **The theme's radius and elevation roles now reach portaled panels.** A pane lives under `<body>`, so
304
+ nothing component-scoped could reach it: squaring `--ds-radius-panel` left a square app with round
305
+ dropdowns, and the only fix was re-declaring the roles on `.ds-overlay-pane` globally. Roles now travel
306
+ with the tokens each component already forwards — but only where the host actually overrides the root,
307
+ so an open panel still follows a theme switch instead of pinning the value it opened with.
308
+
309
+ - **`--ds-badge-white-space`** (default `nowrap`, so nothing moves). A badge in a narrow, fixed-layout
310
+ table column has to be allowed to wrap or its label clips, and the property was the one thing on that
311
+ element not reachable through a token — the workaround was a global rule against the private `.badge`.
312
+
313
+ - **`showPageSize` and `showLabel` on `ds-table`**, forwarded to its footer pager. Both have always existed
314
+ on the standalone `ds-pagination` but were unreachable once the pager was inside a table, so hiding the
315
+ size picker on a fixed-page-size table meant a global selector reaching into the DS. Default `true` — no
316
+ change unless set.
317
+
318
+ - **`--ds-table-head-pad-top` / `--ds-table-head-pad-bottom`.** Header cells were the one padding in the
319
+ table that stayed symmetric — body cells have had per-side hooks since 07-31 — so a header wanting its
320
+ label tight to the top with air above the rule could only be reached with `!important`. Both fall back to
321
+ the density value, so nothing moves until one is set.
322
+
323
+ - **`ds-autocomplete` can be built as a search field.** `dsAutocompletePrefix` / `dsAutocompleteSuffix`
324
+ content slots — the same names and the same contract as `ds-input`'s addon slots — plus `[showChevron]`
325
+ (default `true`) to drop the trailing arrow, which on a search field invites a click that would list
326
+ everything. Previously a leading glyph had to be absolutely positioned over the field and the chevron
327
+ hidden with a global selector reaching for `.autocomplete-chevron`. Unlike a fixed `variant="search"`,
328
+ the slots also cover the icon-**and**-chevron case a combobox often wants.
329
+
330
+ - **`ds-autocomplete.clear()`**, emptying both the selected value and the text the user typed. Setting
331
+ `value` to null from outside left the typed query on screen, because the query is component state with no
332
+ input bound to it — so a host resetting the field after navigating had to query the inner `<input>` and
333
+ dispatch a synthetic `input` event at it. It deliberately does not move focus.
334
+
335
+ - **`--ds-autocomplete-panel-maxh`**, so the dropdown's height before it scrolls no longer needs the private
336
+ `--picker-maxh` (which `ds-multi-select` also reads, making it the wrong lever for one component).
337
+
338
+ - **`--ds-autocomplete-panel-radius`, bringing the last panel into the radius role layer.** Its dropdown was
339
+ the one portaled surface still hard-coding `--radius-lg` while modal, popover, card, bottom-sheet and both
340
+ picker panels resolve `--ds-radius-panel`, so a consumer who squared the three radius roles got a square
341
+ app with one rounded panel and no hook to reach it. Nothing moves by default — the role still resolves to
342
+ `--radius-lg` — and the token is forwarded onto the portaled pane on open like the other panel tokens.
343
+
344
+ - **`ds-app-layout` takes a `scrollReset` strategy, and `LayoutNavigationService` is public** (both asked
345
+ for by the ai-sdlc starter after their `ds-app-layout` migration). Owning the scroll CONTAINER had
346
+ quietly meant owning the POLICY: `scrollToTop()` was public so a screen could ADD a reset, but nothing
347
+ could suppress one the layout decided to do. `scrollReset: 'path' | 'never' | 'always'` defaults to
348
+ `'path'`, which is exactly today's behaviour — no consumer sees a change unless they set it. `'always'`
349
+ also resets on a query- or fragment-only navigation (what a server-paged list wants); `'never'` hands the
350
+ decision to the screen.
351
+ — Exporting the navigation service removes a duplication the layout was causing: "did the path change?"
352
+ was being re-derived per consumer, and one of them had THREE answers that disagreed, because a
353
+ `split('?')` keeps the fragment `pathChanged` strips. It is root-provided and stateless, so exposing it
354
+ costs nothing.
355
+
356
+ - **`ds-icon` warns in dev when a name resolves to nothing** (asked for by the ai-sdlc starter after an audit
357
+ found misspelled names on three screens). An unknown name rendered an empty `<svg>` in silence: the types
358
+ cannot catch it, because `IconName` stays open (`| (string & {})`) so a consumer can register their own
359
+ glyphs through `provideDsIcons()`, and closing the union would reject every registered name. The warning
360
+ names the offending value and sits on the one branch that knows — production pays a single falsy check.
361
+
362
+ ### Fixed
363
+
364
+ - **Opening `ds-date-picker` with the mouse no longer takes the caret out of the field.** Clicking the
365
+ calendar glyph moved focus into the day grid, which a mouse user did not ask for and which, with
366
+ `allowInput` on by default, pulled them out of a field they may have been typing in. The glyph now behaves
367
+ like a click on the field itself: focus follows what the field IS — typeable keeps the caret, read-only
368
+ focuses the grid. The keyboard path is unchanged, ArrowDown still enters the grid however the panel opened.
369
+
370
+ - **A settled `ds-autocomplete` no longer shows an empty text box beside its value.** In single mode the
371
+ chosen label has always rendered as its own element, but the filter input stayed 80px wide next to it and
372
+ took the caret, so a field with a value read as free text rather than a picker. With a value and the panel
373
+ closed the input now collapses to zero width — it keeps focus, so clicking still opens the panel and
374
+ typing still filters.
375
+
376
+ - **A column resize no longer moves columns the reader never touched.** Only the dragged column had a width,
377
+ so the browser redistributed the remainder across the auto-sized rest and they visibly jumped. The first
378
+ resize — pointer or keyboard — now freezes every visible column at what it currently measures, once.
379
+
380
+ - **The clipped-cell popover reaches template cells, and a narrowed header keeps its label.** Clip detection
381
+ walks descendants, so overflow inside a `dsCellTemplate` behaves like a plain truncated cell; a header
382
+ narrowed by resizing gets a `title` with the full label on hover. Scoped to columns that asked for
383
+ `truncate` — a handler on every cell would swallow the row click on an interactive table.
384
+
385
+ - **`sortValue` string ordering is case- and accent-insensitive** (`sensitivity: 'base'`), matching the
386
+ comparator consumers are migrating off, so a column of strings does not silently reorder.
387
+
388
+ - **`--ds-field-height` now reaches six more controls.** `ds-autocomplete`, `ds-multi-select`,
389
+ `ds-color-picker`, `ds-number-stepper`, `ds-split-button` and the `ModalService` confirm input each
390
+ spelled their height as the raw `--hit-*` value, so the knob the token name advertises did nothing for
391
+ them. All six are on the `field-box-height` contract now, and no raw `--hit-cozy` height is left in the
392
+ library. Same pixels at every size **except `ds-number-stepper` at `size="lg"`, which goes 44px → 48px**
393
+ to match the family's large field; the other sizes are unchanged.
394
+
395
+ - **Date and time pickers keep step with the fields beside them under `[data-density]`.** Both triggers
396
+ hard-coded their horizontal padding, which happened to equal `--field-pad-x` at default density but did
397
+ not shrink with it — so setting a density left a picker 8px wider than the `ds-input` next to it. Both now
398
+ resolve `--ds-date-picker-trigger-pad-x` / `--ds-time-picker-trigger-pad-x` from the field family.
399
+
400
+ - **`ds-card`'s box fills a stretched host**, so a grid row of cards with unequal content paints equal
401
+ heights instead of a stretched host wrapping a short bordered box. `ds-stat` already did this; cards
402
+ needed a `::ng-deep .card { height: 100% }` from the consumer. Nothing changes where the host is
403
+ content-sized, which is every card not in a stretching row.
404
+
405
+ - **`density="compact"` no longer defeats every `ds-table` padding hook.** It pinned `padding` straight onto
406
+ the cells, which out-specifies the `--ds-table-cell-pad-*` and head hooks, so a compact table silently
407
+ ignored all of them. It now retunes the same density tokens `[data-density]` uses — identical spacing, and
408
+ the hooks apply.
409
+
410
+ - **`ds-date-picker`'s trigger stays visibly active while its own panel is open.** The indicator was bound to
411
+ focus only, and opening from the calendar glyph moves focus into the day grid — so the trigger went dark
412
+ while its panel was open, and the refocus on close made it read as a flicker.
413
+
414
+ - **`ds-table`: the three things that still forced a consumer wrapper.** All from mm-broker folding its
415
+ 2160-line `ids-data-table` fork onto the base.
416
+ — **`filterMode: 'client' | 'server' | 'none'`**, mirroring `sortMode` — it shipped defaulting to
417
+ `'client'` and the default was flipped to `'server'` later in this same release, above — plus
418
+ **`columnFilterOptions`** for the real value domain. A header filter on a server-paged table was wrong
419
+ twice over: the checklist could only offer values from the page in hand, and the local pass then filtered
420
+ what the server had already filtered. `'server'` tracks `columnFilters` and filters nothing; `'none'`
421
+ drops the affordance. A dev warning catches the silent case — `filter: 'set'` with `total` bound and no
422
+ declared mode.
423
+ — **`dsHeaderFilter`**, a template slot for a criterion the checklist cannot express (a date range, a
424
+ numeric threshold, an async lookup). The table keeps the header button, the popover and the active-filter
425
+ styling; `active` on the directive tells the highlight whether your criterion is set, because only you
426
+ know. The context carries `close`, so the panel can dismiss itself after applying.
427
+ — **A live region for sort state and row range.** The table announced loading and nothing else, so a
428
+ screen-reader user got no confirmation that the order changed and paging never announced the new range.
429
+ One `role="status"` now carries both, with loading taking precedence while it lasts. `sortAnnouncement`
430
+ and `rangeAnnouncement` take the facts and return the sentence, so translation and word order stay with
431
+ the consumer.
432
+
433
+ - **`ds-tabs` keeps the active tab in the URL: `urlParam="tab"`** (asked for by the ai-sdlc starter). The
434
+ input both switches it on and names the parameter; leave it out and the URL is untouched. Names come from
435
+ each `ds-tab`'s `value` — the identifier `tabClosed` already emits — so there is no second list to keep in
436
+ step. The evidence for shipping it: in one admin port THREE of the four tabbed screens never got the
437
+ hand-wiring at all, so only the screen whose author reached for a helper worked.
438
+ — Names, not indices (`?tab=1` would repoint every old link the moment a tab is inserted); the first tab
439
+ writes no parameter and every write replaces (clean address, and flipping tabs does not fill the Back
440
+ button); an unknown or missing name lands on tab 0 rather than throwing. Outside a routed context the
441
+ input is inert — the router is injected optionally, so a strip in a dialog is unaffected.
442
+
443
+ - **Options in the picker panels had no pressed state.** Hover only — so on a phone, where there is no
444
+ hover, tapping a row in `ds-select`, `ds-autocomplete` or `ds-multi-select` gave no feedback that it had
445
+ been hit. The equivalent rows elsewhere (`ds-menu-item`, `ds-list-item`) have had one since 0.7.x. Fixed
446
+ once in the shared dropdown-overlay partial, so all three pickers get it, with a selected-row variant that
447
+ stays in the brand family rather than stranding the selected label colour on a neutral fill.
448
+
449
+ - **`ds-textarea size="sm"` and `="lg"` got the md vertical padding.** The size variants set the inner
450
+ `<textarea>`'s vertical pad (`--space-2` / `--space-4`), but the `:host`-prefixed pin at the end of the
451
+ file — added so the docs' unencapsulated `.field .control` specimen could not zero it — out-ranks them
452
+ once emulated encapsulation shims both selectors: `[_nghost] .field[_ngcontent] .control[_ngcontent]
453
+ textarea[_ngcontent]` carries one more attribute than `.field.sm[_ngcontent] …`. So every textarea
454
+ rendered with 12px top and bottom regardless of `size`, and retuning
455
+ `--ds-input-pad-y` moved all three. There are now three pins, one per size, and the size blocks keep
456
+ only the horizontal padding they own. Consumers see it only on a non-md textarea; the md default is
457
+ unchanged.
458
+
11
459
  ## 0.8.0 — 2026-08-05
12
460
 
13
461
  ### Added