@ids-group-ltd/ids-design-system 0.11.0 → 0.11.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.
Files changed (47) hide show
  1. package/CHANGELOG.md +1164 -1011
  2. package/components.md +49 -26
  3. package/design-system.md +18 -18
  4. package/fesm2022/ids-group-ltd-ids-design-system.mjs +527 -116
  5. package/fesm2022/ids-group-ltd-ids-design-system.mjs.map +1 -1
  6. package/migrations/0.10.0.json +19 -19
  7. package/migrations/0.10.1.json +20 -7
  8. package/migrations/0.10.2.json +8 -8
  9. package/migrations/0.10.3.json +2 -2
  10. package/migrations/0.11.0.json +12 -12
  11. package/migrations/0.11.1.json +305 -0
  12. package/migrations/0.2.2.json +1 -1
  13. package/migrations/0.3.0.json +1 -1
  14. package/migrations/0.5.1/badge-statuses.md +1 -3
  15. package/migrations/0.5.1.json +1 -1
  16. package/migrations/0.6.3.json +1 -1
  17. package/migrations/0.7.1.json +3 -3
  18. package/migrations/0.8.0.json +5 -5
  19. package/migrations/0.9.0.json +10 -9
  20. package/migrations/0.9.1.json +2 -2
  21. package/migrations/README.md +34 -52
  22. package/package.json +1 -1
  23. package/styles/_dropdown-overlay.scss +35 -13
  24. package/styles/_ds-color.scss +3 -3
  25. package/styles/_field-box.scss +2 -6
  26. package/styles/_field-label.scss +5 -10
  27. package/styles/_field-state.scss +3 -2
  28. package/styles/_focus.scss +0 -2
  29. package/styles/_layout-utils.scss +2 -2
  30. package/styles/_overlay-motion.scss +2 -3
  31. package/styles/_press.scss +3 -5
  32. package/styles/_reset.scss +0 -1
  33. package/styles/_scrollbar.scss +1 -3
  34. package/styles/_status.scss +1 -2
  35. package/styles/_surface-motion.scss +3 -4
  36. package/styles/_text-clip.scss +1 -1
  37. package/styles/_theme-activation.scss +1 -1
  38. package/styles/_tokens-charts.scss +1 -3
  39. package/styles/_tokens.scss +4 -3
  40. package/styles/_typography.scss +2 -2
  41. package/themes/README.md +3 -3
  42. package/themes/_base-palette.scss +2 -2
  43. package/themes/_semantic.scss +2 -2
  44. package/themes/dark/_palette.scss +1 -2
  45. package/themes/light/_palette.scss +1 -1
  46. package/themes/light/_theme.scss +1 -1
  47. package/types/ids-group-ltd-ids-design-system.d.ts +274 -49
@@ -0,0 +1,305 @@
1
+ {
2
+ "version": "0.11.1",
3
+ "items": [
4
+ {
5
+ "id": "autocomplete-panel-classes-renamed",
6
+ "kind": "class-rename",
7
+ "old": ".autocomplete-list, .autocomplete-optgroup, .autocomplete-optgroup-label, and the check icon's .icon inside an option",
8
+ "new": ".dropdown-list, .optgroup, .optgroup-label, .option-check — all inside a new .dropdown-panel wrapper",
9
+ "appliesWhen": "You wrote a global rule against `.ds-overlay-pane .autocomplete-list` or a sibling. Nothing to do if you only use the `<ds-autocomplete>` element and its inputs.",
10
+ "pitfall": "The panel is portaled to document.body, so these rules are almost always global rather than component-scoped — grep your global stylesheets, not just the component next to the picker.",
11
+ "searchHints": [
12
+ "autocomplete-list",
13
+ "autocomplete-optgroup"
14
+ ],
15
+ "surface": "style",
16
+ "detect": [
17
+ ".autocomplete-list",
18
+ ".autocomplete-optgroup",
19
+ ".autocomplete-optgroup-label"
20
+ ],
21
+ "verify": "The autocomplete's open panel carries `ds-dropdown-panel` on its `.cdk-overlay-pane`, and its rows have 4px padding and a 4px radius without any rule of yours.",
22
+ "restore": null,
23
+ "note": "The panel now renders through the same shared partial as ds-select and ds-multi-select, so it inherits their padding, row radius, selected-row hooks and pressed states. An override that existed only to close that gap is dead weight, and one that names an old class silently stops matching.",
24
+ "action": "Retarget every rule that names an old class, then delete the ones that only restored padding or row radius."
25
+ },
26
+ {
27
+ "id": "autocomplete-option-hover-token-removed",
28
+ "kind": "token-rename",
29
+ "old": "--ds-autocomplete-option-bg-color-hover",
30
+ "new": "--ds-option-selected-bg-color, --ds-option-selected-label-color, --ds-option-selected-bg-color-hover, --ds-option-check-color",
31
+ "appliesWhen": "You set --ds-autocomplete-option-bg-color-hover anywhere.",
32
+ "pitfall": "The old token painted BOTH the hover and the selected row, because the autocomplete had no separate selected treatment. The panel-level hooks separate them, so a single old value may need splitting across two.",
33
+ "searchHints": [
34
+ "ds-autocomplete-option-bg-color-hover"
35
+ ],
36
+ "surface": "style",
37
+ "detect": [
38
+ "--ds-autocomplete-option-bg-color-hover"
39
+ ],
40
+ "verify": "A :root or ds-autocomplete override of --ds-option-selected-bg-color repaints the selected row in ds-select and ds-autocomplete. ds-multi-select marks selection with a checkbox, so it answers to --ds-multi-select-check-* instead.",
41
+ "restore": null,
42
+ "note": "The autocomplete had no separate selected treatment, so one token painted both hover and selection. The panel-level hooks reach all three pickers and separate the two states, which is what the 0.9.0 notes already claimed was true.",
43
+ "action": "Replace --ds-autocomplete-option-bg-color-hover with the panel-level --ds-option-* hooks."
44
+ },
45
+ {
46
+ "id": "autocomplete-single-value-ellipsizes",
47
+ "kind": "behavior",
48
+ "old": "A settled single value wider than the trigger wrapped onto a second line and pushed the chevron onto a third — measured 40px to 63px at a 144px trigger.",
49
+ "new": null,
50
+ "appliesWhen": "You use `<ds-autocomplete>` in single mode in a narrow column.",
51
+ "pitfall": "Multi mode is unchanged — its chips already had a measured cap. This only affects the settled single value.",
52
+ "searchHints": [
53
+ "ds-autocomplete"
54
+ ],
55
+ "surface": "template",
56
+ "detect": [
57
+ "<ds-autocomplete"
58
+ ],
59
+ "verify": "A long value in a 144px-wide single-select autocomplete keeps the trigger one row tall and ends in an ellipsis, with the full text on the element's title.",
60
+ "restore": "valueOverflow=\"wrap\"",
61
+ "note": "A settled single value now clips with an ellipsis and keeps the trigger one row tall, with the full text on the element title. Multi mode is untouched — its chips already had a measured cap. Nothing in your markup has to change unless the wrapping was deliberate.",
62
+ "action": "Do nothing, or set valueOverflow=\"wrap\" on the pickers that relied on the value wrapping."
63
+ },
64
+ {
65
+ "id": "exported-class-members-grew",
66
+ "kind": "behavior",
67
+ "old": "class MySelect extends SelectComponent, class MyMultiSelect extends MultiSelectComponent, class MyAutocomplete extends AutocompleteComponent",
68
+ "new": null,
69
+ "appliesWhen": "Subclassing a DS component is unsupported, but consumers do it. Template users of the `<ds-…>` elements need nothing.",
70
+ "pitfall": "`protected` is no protection: a redeclared protected member collides exactly as a public one does.",
71
+ "searchHints": [
72
+ "extends SelectComponent",
73
+ "extends MultiSelectComponent",
74
+ "extends AutocompleteComponent"
75
+ ],
76
+ "surface": "typescript",
77
+ "detect": [
78
+ "extends SelectComponent",
79
+ "extends MultiSelectComponent",
80
+ "extends AutocompleteComponent"
81
+ ],
82
+ "verify": "The app builds with no TS2415 or TS2416 naming a picker component.",
83
+ "restore": null,
84
+ "note": "All three pickers gained members: ds-select a width input and a private panelTokens field, ds-multi-select and ds-autocomplete a label/required/optional block plus projection slots. Subclassing a DS component is unsupported but consumers do it, and a redeclared member collides whether it is public or protected. The compiler enumerates every collision, so a build is the whole check and no list here could stay current.",
85
+ "action": "Build after upgrading, and rename or mark `override` every member of yours the compiler reports as colliding."
86
+ },
87
+ {
88
+ "id": "autocomplete-width-type-widened",
89
+ "kind": "behavior",
90
+ "old": "export type AutocompleteWidth = 'fill' | 'content';",
91
+ "new": null,
92
+ "appliesWhen": "You import AutocompleteWidth by name.",
93
+ "pitfall": "Only a declaration that re-declares the type structurally (rather than importing it) could notice, and it still sees the same union.",
94
+ "searchHints": [
95
+ "AutocompleteWidth"
96
+ ],
97
+ "surface": "typescript",
98
+ "detect": [
99
+ "AutocompleteWidth"
100
+ ],
101
+ "verify": "The app builds and `width` still accepts only 'fill' and 'content'.",
102
+ "restore": null,
103
+ "note": "AutocompleteWidth is now an alias of the shared DsControlWidth that SelectWidth and MultiSelectWidth also alias. The union it resolves to is unchanged, so an import keeps compiling and `width` still accepts exactly `fill` and `content`.",
104
+ "action": "Do nothing."
105
+ },
106
+ {
107
+ "id": "autocomplete-option-groups-input-removed",
108
+ "kind": "input-rename",
109
+ "old": "optionGroups",
110
+ "new": "options",
111
+ "action": "Move the array you passed to `optionGroups` into `options`.",
112
+ "note": "The autocomplete took groups in a second input and documented `options` as ignored whenever it was set, so two inputs existed and one silently won. `options` now accepts flat options, groups, or both mixed, in the order given, which is the shape ds-select already used and ds-multi-select has gained.",
113
+ "appliesWhen": "You bind `[optionGroups]` on a `<ds-autocomplete>`.",
114
+ "pitfall": "If you were passing BOTH inputs and relying on the flat one being dropped, merging them changes what renders — the flat options now appear alongside the groups rather than vanishing.",
115
+ "searchHints": [
116
+ "optionGroups"
117
+ ],
118
+ "surface": "template",
119
+ "detect": [
120
+ "[optionGroups]",
121
+ "optionGroups="
122
+ ],
123
+ "verify": "The autocomplete renders its labelled sections with only `options` bound, and filtering still hides a group whose options all fail the query.",
124
+ "restore": null
125
+ },
126
+ {
127
+ "id": "multi-select-panel-classes-renamed",
128
+ "kind": "class-rename",
129
+ "old": ".panel, .options (inside ds-multi-select’s portaled panel)",
130
+ "new": ".dropdown-panel, .dropdown-list",
131
+ "action": "Retarget any rule naming the old classes, then delete the ones that only restored what the shared panel already gives.",
132
+ "note": "The multi-select carried its own copy of the panel and the option row while its pane also carried ds-dropdown-panel, so both rule sets applied at once and the component’s won. It renders through the shared partial now, like the other two pickers.",
133
+ "appliesWhen": "You wrote a global rule against `.ds-overlay-pane .panel` or `.options` for the multi-select.",
134
+ "pitfall": "The panel is portaled to document.body, so such a rule is almost always global rather than beside the component.",
135
+ "searchHints": [
136
+ "ds-overlay-pane .panel",
137
+ ".options"
138
+ ],
139
+ "surface": "style",
140
+ "detect": [
141
+ ".ds-overlay-pane .panel",
142
+ ".ds-overlay-pane .options"
143
+ ],
144
+ "verify": "The multi-select panel renders with 4px padding and 4px row radius with no rule of yours, and its rows pick up the shared partial’s hover and active fills.",
145
+ "restore": null
146
+ },
147
+ {
148
+ "id": "trigger-display-compact-renamed",
149
+ "kind": "value-remap",
150
+ "old": "triggerDisplay=\"compact\"",
151
+ "new": "triggerDisplay=\"count\"",
152
+ "map": {
153
+ "compact": "count"
154
+ },
155
+ "action": "Replace the value `compact` with `count`.",
156
+ "note": "A third value, `labels`, now sits beside it and names the selection instead of counting it, so the old name no longer said which of the two it was.",
157
+ "appliesWhen": "You set triggerDisplay on a ds-multi-select. The input shipped inside this same unreleased block, so only work in flight is affected.",
158
+ "pitfall": "None — the rendering of `count` is exactly what `compact` did.",
159
+ "searchHints": [
160
+ "triggerDisplay"
161
+ ],
162
+ "surface": "template",
163
+ "detect": [
164
+ "triggerDisplay=\"compact\"",
165
+ "triggerDisplay: 'compact'"
166
+ ],
167
+ "verify": "The trigger still shows a caption and a count badge.",
168
+ "restore": null
169
+ },
170
+ {
171
+ "id": "published-manifest-corrections",
172
+ "kind": "behavior",
173
+ "old": "a repo upgraded through 0.5.1, 0.9.0 or 0.10.1 before this release",
174
+ "new": null,
175
+ "surface": [
176
+ "template",
177
+ "typescript",
178
+ "style"
179
+ ],
180
+ "action": "Re-run three items whose earlier text could not do its job. 0.5.1#progress-variant-remap: search for `variant=\"warn\"` and `variant=\"indeterminate\"` on ds-progress and for `ProgressVariant` in TypeScript, and finish that remap — the colour vocabulary is `default | success | warning | error` and the indeterminate state is the bare `indeterminate` attribute. 0.9.0#search-height-joins-field-scale: search for `--hit-min` and drop the pin where it was set only to shorten a ds-search row. 0.10.1: search for `(closed)` on a modal whose body holds a ds-date-picker and keep the body mounted instead.",
181
+ "appliesWhen": "Only if your last upgrade ran BEFORE this release and crossed 0.5.1, 0.9.0 or 0.10.1. A first-time consumer, or one whose upgrade runs from here on, reads the corrected files and needs none of this. The three are independent — crossing 0.5.1 says nothing about 0.10.1.",
182
+ "pitfall": "The 0.5.1 one is the silent case: its old check inspected ds-badge chips and the status registry, so it passed on a ds-progress that was never migrated. A clean upgrade report from that run proves nothing about ds-progress, so search rather than trusting it. The other two leave redundant code, not broken code — a `--hit-min` pin set deliberately for density is not this, so read each hit before deleting it.",
183
+ "note": "These manifests are executed by an upgrade tool, so a wrong verify or a locator that finds nothing lands in the consumer repo as an unapplied migration that reported success.",
184
+ "searchHints": [
185
+ "variant=\"warn\"",
186
+ "variant=\"indeterminate\"",
187
+ "ProgressVariant",
188
+ "--hit-min",
189
+ "ds-progress",
190
+ "(closed)"
191
+ ],
192
+ "detect": [
193
+ "variant=\"warn\"",
194
+ "variant=\"indeterminate\"",
195
+ "ProgressVariant",
196
+ "--hit-min",
197
+ "@if (open())"
198
+ ],
199
+ "verify": "No ds-progress binds `variant=\"warn\"` or `variant=\"indeterminate\"` and nothing is typed against a removed ProgressVariant member; no `--hit-min` pin exists whose only purpose was a shorter ds-search row; no modal body is torn down on `(closed)` to reset a ds-date-picker.",
200
+ "restore": null,
201
+ "supersedes": null
202
+ },
203
+ {
204
+ "id": "autocomplete-options-element-type-widened",
205
+ "kind": "behavior",
206
+ "old": "ds-autocomplete [options] typed readonly AutocompleteOption<T>[]",
207
+ "new": null,
208
+ "surface": "typescript",
209
+ "action": "Only where you READ the array back or type a variable against its element: change `AutocompleteOption<T>` to `AutocompleteItem<T>` and narrow each element with `isDsOptionGroup` before touching `.value`. Narrow before reading: `for (const item of picker.options()) { if (isDsOptionGroup(item)) continue; /* item.value is safe here */ }`. `isDsOptionGroup` and `flattenDsOptions` are exported from the package root.",
210
+ "appliesWhen": "Only code that reads the input back, declares a variable or field typed against its element, or overrides a member typed that way. Passing plain options IN is unchanged and needs nothing — a template binding is unaffected.",
211
+ "pitfall": "The compiler catches the type, not the assumption. Code that already destructures `.value` off each element keeps compiling wherever the variable is inferred rather than annotated, and then reads `undefined` at runtime for a group.",
212
+ "note": "The element type is now `AutocompleteItem<T>`. The input takes flat options, groups, or both mixed, so an element is no longer always an option.",
213
+ "searchHints": [
214
+ "AutocompleteOption",
215
+ "AutocompleteItem",
216
+ "ds-autocomplete",
217
+ "[options]",
218
+ "isDsOptionGroup"
219
+ ],
220
+ "detect": [
221
+ "AutocompleteOption<",
222
+ ": AutocompleteOption",
223
+ "AutocompleteOption[]"
224
+ ],
225
+ "verify": "No variable, field or override is typed `AutocompleteOption` where it receives the contents of an `options` array, and every `.value` read off such an element is guarded by `isDsOptionGroup`.",
226
+ "restore": null,
227
+ "supersedes": null
228
+ },
229
+ {
230
+ "id": "multi-select-options-element-type-widened",
231
+ "kind": "behavior",
232
+ "old": "ds-multi-select [options] typed readonly MultiSelectOption[]",
233
+ "new": null,
234
+ "surface": "typescript",
235
+ "action": "Only where you READ the array back or type a variable against its element: change `MultiSelectOption` to `MultiSelectItem` and narrow with `isDsOptionGroup` before touching `.value`. Narrow before reading: `for (const item of picker.options()) { if (isDsOptionGroup(item)) continue; /* item.value is safe here */ }`. `isDsOptionGroup` and `flattenDsOptions` are exported from the package root.",
236
+ "appliesWhen": "Only code that reads the input back, declares a variable or field typed against its element, or overrides a member typed that way. Passing plain options IN is unchanged.",
237
+ "pitfall": "ds-multi-select accepted no groups at all before this release, so existing code has no reason to guard and every element really was an option. That is exactly why the read sites are worth finding rather than trusting.",
238
+ "note": "The element type is now `MultiSelectItem`. Groups are new on this component, so the element union is new here too.",
239
+ "searchHints": [
240
+ "MultiSelectOption",
241
+ "MultiSelectItem",
242
+ "ds-multi-select",
243
+ "[options]",
244
+ "isDsOptionGroup"
245
+ ],
246
+ "detect": [
247
+ "MultiSelectOption<",
248
+ ": MultiSelectOption",
249
+ "MultiSelectOption[]"
250
+ ],
251
+ "verify": "No variable, field or override is typed `MultiSelectOption` where it receives the contents of an `options` array, and every `.value` read off such an element is guarded by `isDsOptionGroup`.",
252
+ "restore": null,
253
+ "supersedes": null
254
+ },
255
+ {
256
+ "id": "multi-select-select-all-type-widened",
257
+ "kind": "behavior",
258
+ "old": "ds-multi-select selectAll typed boolean",
259
+ "new": null,
260
+ "surface": "typescript",
261
+ "action": "Only where you READ `selectAll` back into a `boolean`: widen the receiving type to `boolean | 'group' | 'both'`, or compare against the value you meant (`selectAll() === true`).",
262
+ "appliesWhen": "Only code that assigns the input back into a `boolean`, or a subclass that re-declares it. Setting it — `[selectAll]=\"true\"` or the bare attribute — is unchanged, and the default is still `false`.",
263
+ "pitfall": "A truthiness test that used to mean \"the whole panel\" now also passes for `'group'`, where there is no panel-wide row at all — so a guard written as `if (selectAll())` silently changes meaning while still compiling.",
264
+ "note": "The type is now `boolean | 'group' | 'both'`. `'group'` renders a row per group and `'both'` adds the panel-wide row beside them.",
265
+ "searchHints": [
266
+ "selectAll",
267
+ "ds-multi-select",
268
+ "'group'",
269
+ "'both'"
270
+ ],
271
+ "detect": [
272
+ "selectAll()",
273
+ "[selectAll]",
274
+ "selectAll:"
275
+ ],
276
+ "verify": "Nothing assigns `selectAll` into a `boolean`, and any truthiness test on it has been read once to confirm it still means what it did.",
277
+ "restore": null,
278
+ "supersedes": null
279
+ }
280
+ ],
281
+ "informational": [
282
+ "ds-multi-select and ds-select gained `width`, the input ds-autocomplete already had: `content` takes the trigger width as the panel's floor instead of its width, so a short trigger stops forcing an unreadable panel. Default `fill` is unchanged.",
283
+ "New panel bounds for that mode: --ds-dropdown-panel-minw and --ds-dropdown-panel-maxw.",
284
+ "ds-select now forwards its panel custom properties onto the portaled pane, which it never did — a `ds-select { --ds-dropdown-panel-*: … }` reaches the panel now instead of being silently dropped.",
285
+ "ds-multi-select gained option groups, which it never had. A group disables all of its options when its own `disabled` is set.",
286
+ "ds-multi-select and ds-autocomplete gained `label`, `required` and `optional`, which existed on ds-select alone; ds-multi-select gained `size`, which the other two already had.",
287
+ "New slots: dsEmptyTemplate on all three pickers, dsCreateTemplate on ds-autocomplete. ds-select shows an empty row when it has no options, where it used to open a blank panel.",
288
+ "selectAll on ds-multi-select accepts 'group' and 'both' beside true/false.",
289
+ "All three pickers now forward the four panel-level --ds-option-* hooks onto their portaled pane, so a per-instance override reaches the panel.",
290
+ "The dropdown panel geometry now lives only in styles/_dropdown-overlay.scss, behind --ds-dropdown-panel-bg-color/-radius/-maxh/-minw/-maxw. The per-picker names (--ds-multi-select-panel-bg-color, --ds-autocomplete-panel-bg-color/-radius/-maxh) are aliases of those and still work; a global rule of yours that relied on a component stylesheet out-ranking the partial no longer has a competing rule to beat."
291
+ ],
292
+ "deleteList": [
293
+ {
294
+ "id": "autocomplete-listbox-padding-override",
295
+ "surface": "style",
296
+ "find": [
297
+ ".ds-overlay-pane .autocomplete-list",
298
+ "padding",
299
+ "border-radius"
300
+ ],
301
+ "why": "The autocomplete panel shipped with `padding: 0` and square rows while ds-select's dropdown had `--space-1` padding and rounded rows, so consumers patched the difference globally. The panel now uses the same shared partial as the other two pickers and matches without help.",
302
+ "replaceWith": "Nothing — delete the rule. The padding is --space-1 and the row radius is --ds-radius-inner out of the box; --ds-dropdown-panel-minw / -maxw are there if you want to bound the panel."
303
+ }
304
+ ]
305
+ }
@@ -3,7 +3,7 @@
3
3
  "items": [],
4
4
  "informational": [
5
5
  "New .t-mono-inline typography utility (inline code chip), completing the mono family alongside .t-mono and .t-mono-block — additive.",
6
- "npm package hygiene: repository field dropped from package.json, maintainer docs moved to repo-only CONTRIBUTING.md, README license entry made plain text (fixes the npm 404). No consumer action."
6
+ "npm package hygiene: repository field dropped from package.json, README license entry made plain text (fixes the npm 404). No consumer action."
7
7
  ],
8
8
  "deleteList": []
9
9
  }
@@ -25,7 +25,7 @@
25
25
  "kind": "behavior",
26
26
  "old": "--ds-*-fg",
27
27
  "new": null,
28
- "action": "For each `-fg` token you override, look the replacement up in the installed 0.3.0 package (`themes/`, `styles/`, and the component SCSS) and use the exact name you find. Three suffixes are in play and the split is real: at 0.3.0 the sources carry 23 `-text-color`, 49 `-label-color` and 21 `-icon-color`.",
28
+ "action": "For each `-fg` token you override, look the replacement up in the 0.3.0 token reference on the documentation site, which lists every `--ds-*`; the global roles are also readable in the installed package under `themes/` and `styles/`. Three suffixes are in play and the split is real: at 0.3.0 the package carries 23 `-text-color`, 49 `-label-color` and 21 `-icon-color`.",
29
29
  "appliesWhen": "Only to DS-owned tokens. A variable of your own ending in `-fg` is untouched.",
30
30
  "pitfall": "The suffix is NOT derivable from the old name, so guessing produces a name nothing reads and a silently unstyled element. Same shape, three answers: `--ds-modal-title-fg` became `-text-color`, `--ds-sidenav-group-fg` became `-label-color`, `--ds-icon-button-fg` became `-icon-color`.",
31
31
  "note": "The `fg` abbreviation was dropped for a suffix that says what the token paints — text, a control or nav label, or a glyph. It covers the public `--ds-<component>-…-fg` hooks on avatar, badge, banner, breadcrumbs, button, date-picker, dropzone, empty-state, icon-button, input, menu, modal, page-header, pagination, search, sidenav, table, tabs, tag and topbar, plus the `--status-*` and chart-tooltip globals.",
@@ -27,9 +27,7 @@ There are three moving parts:
27
27
  `[data-status='…']` rules that set the public component tokens:
28
28
 
29
29
  ```scss
30
- // external consumer of the published package:
31
30
  @use '@ids-group-ltd/ids-design-system/styles/status' as status;
32
- // inside this repo (ds-docs, loadPaths: src/lib): @use 'styles/status' as status;
33
31
 
34
32
  @include status.define(
35
33
  (
@@ -178,4 +176,4 @@ ds-badge.chip.in-transit { … } // .chip now carries layout rules only
178
176
  ```
179
177
 
180
178
  This unifies every badge on one mechanism and restores the values that used to rely on factory
181
- colours. See the field app's `_badge-status.scss` for a full real-world map.
179
+ colours.
@@ -84,7 +84,7 @@
84
84
  "style",
85
85
  "typescript"
86
86
  ],
87
- "verify": "No `variant` remains on the component. The chips render in their status colours, not grey: the `styles/status` partial is included and any custom status is registered through DsStatusRegistry, or the colour resolves to the neutral default and you meant that."
87
+ "verify": "No ds-progress binds `variant=\"warn\"` or `variant=\"indeterminate\"`: the colour vocabulary is `default | success | warning | error`, and the indeterminate state is the bare `indeterminate` attribute. Nothing is typed with a removed ProgressVariant member."
88
88
  },
89
89
  {
90
90
  "id": "modal-confirm-tone-danger-remap",
@@ -41,7 +41,7 @@
41
41
  "kind": "behavior",
42
42
  "old": null,
43
43
  "new": null,
44
- "action": "Build the consumer immediately after the bump — the compiler enumerates every collision. Per member: where the base means the same thing, keep the name and add `override` with a base-compatible signature; otherwise rename your own member. Observed collisions: zebra, columnOrder, orderedColumns, visibleColumns, toggleColumn, onColumnDrop, moveColumn, resetColumns, columnFilters, exportCsv, onResizeMove, onResizeEnd.",
44
+ "action": "Build the consumer immediately after the bump — the compiler enumerates every collision. Per member: where the base means the same thing, keep the name and add `override` with a base-compatible signature; otherwise rename your own member. Base members it collides on: zebra, columnOrder, orderedColumns, visibleColumns, toggleColumn, onColumnDrop, moveColumn, resetColumns, columnFilters, exportCsv, onResizeMove, onResizeEnd.",
45
45
  "appliesWhen": "Only a consumer that EXTENDS TableComponent. Subclassing a DS component is unsupported (design-system.md § Components); anyone using the `<ds-table>` element is unaffected.",
46
46
  "pitfall": "Two ways to fix it wrongly. Adding `override` to `zebra` without adopting the base booleanAttribute transform changes what the input accepts. And renaming your member to something else can collide again — check the new name against the base member list, because the private and protected ones are internal and give no warning.",
47
47
  "note": "The new column API added about 76 members to TableComponent, so a subclass that already used one of those names stops compiling: TS4114 wants an `override` modifier, TS2416 fires where the signature differs.",
@@ -8,7 +8,7 @@
8
8
  "new": "@use '@ids-group-ltd/ids-design-system/styles/surface-motion';\n@use '@ids-group-ltd/ids-design-system/styles/overlay-motion';",
9
9
  "action": "Add `@use '@ids-group-ltd/ids-design-system/styles/surface-motion';` to your styles entry, beside `styles/overlay-motion`. If you have no overlay-motion line, put it beside whatever DS partials you do `@use`. Order does not matter.",
10
10
  "appliesWhen": "Only à-la-carte consumers who `@use` DS partials individually. `styles/ds` forwards it, so its users need nothing at all.",
11
- "pitfall": "Missing it fails SILENTLY — no error, no warning. The keyframes simply do not exist, and modal, drawer, bottom-sheet, toast, banner, alert, loading-overlay and the overlay panels all render with no entrance animation. Write the package-qualified specifier too: a bare `styles/…` resolves only inside the DS repo, which puts `includePaths: [\"src/lib\"]` on its own docs build.",
11
+ "pitfall": "Missing it fails SILENTLY — no error, no warning. The keyframes simply do not exist, and modal, drawer, bottom-sheet, toast, banner, alert, loading-overlay and the overlay panels all render with no entrance animation. Write the package-qualified specifier too: a bare `styles/…` does not resolve in a consumer build.",
12
12
  "note": "A new global partial `styles/_surface-motion.scss` holds the shared entrance keyframes — ds-fade-in, ds-scale-in, ds-slide-in, ds-slide-edge-in — that every DS surface names through `--ds-<surface>-enter-keyframes`.",
13
13
  "searchHints": [
14
14
  "styles/overlay-motion",
@@ -25,7 +25,7 @@
25
25
  "new": null,
26
26
  "action": "Gate on `sortDir`, not on `sortKey`. `if (sortKey())` becomes `if (sortDir())`, and a server query built as `orderBy: sortKey()` must skip the clause when `sortDir()` is null.",
27
27
  "appliesWhen": "Hosts that already read both need nothing, and neither do those passing `sortingOrder: ['asc','desc']`, which has no unsorted state. The table's own icons, aria-sort and client-side sorting were always gated on `sortDir` and are unchanged.",
28
- "pitfall": "This item finds NOTHING in a template. The code that breaks is the host's own — a store, a page class, a query builder — and it names no DS symbol at all, so a search for `ds-table` comes back clean and the item gets recorded not-applicable. mm-broker had three, each written as `sorting: store.sortKey() ? { path: store.sortKey()!, order: store.sortDir() ?? 'Asc' } : undefined`, and all three kept ordering a server-paged list by the last column the reader touched while the header showed no sort. Grep the `.ts` for the `detect` shapes.",
28
+ "pitfall": "This item finds NOTHING in a template. The code that breaks is the host's own — a store, a page class, a query builder — and it names no DS symbol at all, so a search for `ds-table` comes back clean and the item gets recorded not-applicable. A common shape is `sorting: store.sortKey() ? { path: store.sortKey()!, order: store.sortDir() ?? 'Asc' } : undefined`, which keeps ordering a server-paged list by the last column the reader touched while the header shows no sort. Grep the `.ts` for the `detect` shapes.",
29
29
  "note": "`sortKey` is no longer nulled when the cycle reaches unsorted: it keeps naming the column the user last touched, and `sortDir === null` alone means unsorted. It fixes a header desync for hosts that map \"off\" back to their own default sort.",
30
30
  "searchHints": [
31
31
  "sortKey",
@@ -231,7 +231,7 @@
231
231
  "find": [
232
232
  "[reserveMessage]=\"false\""
233
233
  ],
234
- "why": "The default is FALSE again, so an opt-out binding only restates it - unless the field sits under a `dsReserveMessages` host or an app config that turns it on, where the binding is still the way back out. mm-broker carried six, three of them dead (2026-08-21).",
234
+ "why": "The default is FALSE again, so an opt-out binding only restates it - unless the field sits under a `dsReserveMessages` host or an app config that turns it on, where the binding is still the way back out.",
235
235
  "replaceWith": "nothing - delete the binding where no host reserves"
236
236
  },
237
237
  {
@@ -8,7 +8,7 @@
8
8
  "new": "sortMode",
9
9
  "action": "`[clientSort]=\"true\"` and a bare `clientSort` become `sortMode=\"client\"`; `[clientSort]=\"false\"` or `[clientSort]=\"expr\"` becomes `[sortMode]=\"expr ? 'client' : 'server'\"`. A table that had NO clientSort binding and reorders in its own `(sortChange)` handler must declare `sortMode=\"server\"`. A table that renders a sortable column but sorts nowhere declares `sortMode=\"none\"`, which drops the button, the caret and `aria-sort` instead of leaving a dead control. TypeScript callers can type the value with `import type { TableSortMode }`.",
10
10
  "pitfall": "The last case is the one that is not a find/replace, because the DEFAULT CHANGED: unset resolves to `client` at this version. A server-paged table that only emitted `sortChange` will now ALSO sort its own rows — and client sorting reorders the current page only, so the rows look sorted and are not. Dev builds warn on `total` plus client, but a production build says nothing.",
11
- "note": "The boolean could not express \"nothing sorts\", so a column marked `sortable: true` on a table with no sorting drew a header that looked live, showed a caret on hover and did nothing. mm-broker shipped several detail tables that way and caught it only in a browser walkthrough.",
11
+ "note": "The boolean could not express \"nothing sorts\", so a column marked `sortable: true` on a table with no sorting drew a header that looked live, showed a caret on hover and did nothing.",
12
12
  "searchHints": [
13
13
  "clientSort",
14
14
  "[clientSort]",
@@ -29,7 +29,7 @@
29
29
  "new": null,
30
30
  "action": "Build after upgrading — the compiler enumerates every collision. Per member: rename your own, or add `override` where the base semantics genuinely match. A subclass that overrode `messageState` should move its logic to an `error` or `warning` binding on the element instead, since the message is resolved centrally now.",
31
31
  "appliesWhen": "Only a consumer that EXTENDS a DS component class. Subclassing is unsupported (design-system.md § Components); template users of the `<ds-…>` elements need nothing.",
32
- "pitfall": "A PRIVATE member collides too — TS2415 — and `TableComponent.saveLayout()` is the one that actually bit a consumer whose own table happened to declare the same name. Two more shapes hide here: this release REMOVES members as well as adding them (the fourteen fields dropped protected `messageState`, DatePicker also `messageText`, and Checkbox, Switch and Radio dropped protected `devMode`), so an `override` can start naming nothing; and `close()` gained an optional `cause`, which an override declared as `close()` still satisfies — only a subclass that re-declares the parameter list differently breaks.",
32
+ "pitfall": "A PRIVATE member collides too — TS2415 — and `TableComponent.saveLayout()` is the likeliest to collide, because a table wrapper commonly declares the same name. Two more shapes hide here: this release REMOVES members as well as adding them (the fourteen fields dropped protected `messageState`, DatePicker also `messageText`, and Checkbox, Switch and Radio dropped protected `devMode`), so an `override` can start naming nothing; and `close()` gained an optional `cause`, which an override declared as `close()` still satisfies — only a subclass that re-declares the parameter list differently breaks.",
33
33
  "note": "Additions: the fourteen field classes gained the `error`, `warning`, `errors` and `touched` inputs plus protected `message` and `invalidResolved`; both CVA bases gained protected `touchedSelf`; AppLayoutComponent gained `railOverlay` and `railId`; TableComponent lost `clientSort` and gained `sortModeResolved`, `sortableCol()`, `exporting`, `runExport()`, `virtualizing`, `virtualRowHeight`, `virtualWindow`, `windowData`, `isStriped()`, the `persistLayout`, `storageKey`, `exportButton`, `exportFilename`, `exportFetcher`, `virtualScroll` and `virtualRowSize` inputs and the private `saveLayout()` / `restoreLayout()`; ButtonComponent gained `ariaControls`; IconButtonComponent `ariaExpanded` and `ariaControls`; LayoutScrollService `scroller`, `scrollTo()`, `configureRestore()`, `consumePendingOffset()` and `contentReady()`.",
34
34
  "searchHints": [
35
35
  "extends InputComponent",
@@ -230,13 +230,13 @@
230
230
  "ds-table gained [persistLayout] + storageKey (round-tripping columnOrder, columnWidths and hiddenKeys through localStorage) and [exportButton] + exportFilename + exportFetcher. All opt-in and off by default, so NO ACTION. A consumer who wrote their own localStorage effect for the three column models, or their own export button, can delete both - together with the sortValue accessor these were the last three reasons to keep a wrapper around ds-table. exportCsv() is unchanged for existing callers and now accepts an optional row set as its second argument.",
231
231
  "New component ds-password-rules: the live requirement checklist under a new-password field. Purely additive, NO ACTION. A consumer with a hand-rolled password checklist can replace it - pass the rule set as { label, test } pairs (the policy stays yours, it has to mirror your server), bind [value] to the field and [showUnmet] to whether the user has tried to submit. Exposes metCount and allMet for gating a submit button, and the standalone passwordRulesMet(value, rules) function — the same predicate that backs allMet — for gating one without rendering the list. Also exported: the DsPasswordRule ({ label, test }) and DsPasswordRuleState ('pending' | 'met' | 'failed') types for typing the rule set, plus a listId input that names the <ul> so a field's aria-describedby can point at the checklist.",
232
232
  "ds-input gained ariaDescribedBy, merged with the field's own message id rather than replacing it - for describing a field with a password-rule list or a policy note. Additive, NO ACTION. Note that setting aria-describedby on the <ds-input> element itself does NOT work: it lands on the wrapper, not the inner input.",
233
- "New component ds-auth-shell: the scaffold for the screens in front of the login (sign-in, forgot password, reset, MFA), counterpart to ds-app-layout. Purely additive, NO ACTION. A consumer with a hand-rolled auth scaffold can replace it: brand lockup + optional tagline + one card holding the form + a support line. The brand row is the ds-sidenav row - same brand / logoLetter / [dsBrandName] contract and the same letter-mark tile - so it is NOT the string-splitting brandAccent the ports used; project [dsBrandName] to tint a slice of the wordmark. Card body is the default slot, the support line goes in [dsAuthSupport] (a real <footer>, so it carries the contentinfo landmark). cardElevation / cardPadding pass through to ds-card. Tokens: --ds-auth-shell-min-height, -card-max-width, -gap, -bg-color, -mark-bg-color, -mark-label-color. WORTH KNOWING when porting: the shell owns the full-height box itself, so do NOT wrap it in your own 100vh/100dvh container - the ports that stacked two scrolled a page whose content fits. It also adds env(safe-area-inset-*) padding, and centres with auto margins rather than centre alignment so a form taller than the box stays reachable when the shell is embedded at min-height 100%.",
233
+ "New component ds-auth-shell: the scaffold for the screens in front of the login (sign-in, forgot password, reset, MFA), counterpart to ds-app-layout. Purely additive, NO ACTION. A consumer with a hand-rolled auth scaffold can replace it: brand lockup + optional tagline + one card holding the form + a support line. The brand row is the ds-sidenav row - same brand / logoLetter / [dsBrandName] contract and the same letter-mark tile - so it is NOT a string-splitting brandAccent; project [dsBrandName] to tint a slice of the wordmark. Card body is the default slot, the support line goes in [dsAuthSupport] (a real <footer>, so it carries the contentinfo landmark). cardElevation / cardPadding pass through to ds-card. Tokens: --ds-auth-shell-min-height, -card-max-width, -gap, -bg-color, -mark-bg-color, -mark-label-color. WORTH KNOWING when porting: the shell owns the full-height box itself, so do NOT wrap it in your own 100vh/100dvh container - nesting two of them scrolls a page whose content fits. It also adds env(safe-area-inset-*) padding, and centres with auto margins rather than centre alignment so a form taller than the box stays reachable when the shell is embedded at min-height 100%.",
234
234
  "New component ds-filter-bar: a Priority+ filter row - as many filters as fit inline, the rest behind a \"+N more\" panel. Purely additive, NO ACTION. A consumer with a hand-rolled filter row (or one that wraps to two lines on a laptop) can replace it. Each filter goes in an <ng-template [dsFilterItem]=\"180\"> carrying the width it should occupy; the bar decides the split from those numbers plus a ResizeObserver on the row. Trailing controls (search, Clear) carry the dsFilterBarTrailing attribute - mark each control, do NOT wrap them in a div: the bar owns that group's gap and alignment, and a projected wrapper is a plain block whose children stack. Tokens: --ds-filter-bar-gap, --ds-filter-bar-panel-gap. Inputs moreLabel and panelLabel exist for translation. WORTH KNOWING: the declared width is a contract, not a hint - the slot is sized to exactly that number, so declare what the control actually occupies. And because a filter that collapses is MOVED into the panel, its view is destroyed and re-created: internal state such as an open dropdown or focus does not survive that, while its value does (it lives in your signal or form control). Content that reaches the bar with neither slot marker is dropped, with a dev-mode console warning.",
235
- "ds-table gained virtual scrolling: [virtualScroll]=\"true\" plus virtualRowSize (px). Opt-in and off by default, so NO ACTION. Only the rows in view stay in the DOM (~25 regardless of row count), padded by two spacer rows so the scrollbar still spans the whole data set. REQUIRES maxHeight - a bounded scroller is the viewport it windows against, and without one nothing is virtualized (dev warning). CONSTRAINTS in virtual mode, all enforced rather than assumed: every row is exactly virtualRowSize tall (the CSS height comes from that same input), table-layout becomes fixed, and cells are kept to one line - so declare column widths, and do not rely on wrapping cell text there. Row EXPANSION is suppressed with a dev warning (an expanded row is taller than virtualRowSize and every offset below it would be wrong); pageSize alongside virtualScroll is also warned about, since virtual scrolling is what pagination was for. Sorting, filtering, selection, sticky header, sticky first column and column resizing all keep working. NOT built on the CDK virtual-scroll viewport on purpose: that wraps the table in a transformed content wrapper, and the transform breaks this table's sticky header and sticky first column. STILL OPEN: lazy loading (fetching slices from a server as they scroll into view) is NOT part of this - see the backlog item.",
235
+ "ds-table gained virtual scrolling: [virtualScroll]=\"true\" plus virtualRowSize (px). Opt-in and off by default, so NO ACTION. Only the rows in view stay in the DOM (~25 regardless of row count), padded by two spacer rows so the scrollbar still spans the whole data set. REQUIRES maxHeight - a bounded scroller is the viewport it windows against, and without one nothing is virtualized (dev warning). CONSTRAINTS in virtual mode, all enforced rather than assumed: every row is exactly virtualRowSize tall (the CSS height comes from that same input), table-layout becomes fixed, and cells are kept to one line - so declare column widths, and do not rely on wrapping cell text there. Row EXPANSION is suppressed with a dev warning (an expanded row is taller than virtualRowSize and every offset below it would be wrong); pageSize alongside virtualScroll is also warned about, since virtual scrolling is what pagination was for. Sorting, filtering, selection, sticky header, sticky first column and column resizing all keep working. NOT built on the CDK virtual-scroll viewport on purpose: that wraps the table in a transformed content wrapper, and the transform breaks this table's sticky header and sticky first column. STILL OPEN: lazy loading (fetching slices from a server as they scroll into view) is NOT part of this.",
236
236
  "FIXED in ds-table: with stickyHeader and stickyFirstColumn both on, the first body row painted OVER the header in the pinned columns, so the header read as that row's data. --table-sticky-corner-z was already there to keep the corner above the body, but the sticky-header rule out-specified it and both ended up at the same z-index, where DOM order puts the body on top. No action needed - it is a pure CSS fix. If you worked around it with your own z-index on DS table cells, that override can go. (delete list: table-sticky-corner-zindex-workaround)",
237
237
  "ds-checkbox / ds-switch / ds-radio now RENDER a projected caption instead of dropping it, and expose the caption's colour and size. Additive, NO ACTION - [label] stays the documented API and still wins when both are supplied. If you added a dev-warning workaround after 0.7.1 (moving markup-bearing captions into a string), you can move them back: <ds-checkbox>I accept the <a href=...>Terms</a></ds-checkbox> now works. ONE DIFFERENCE: the required asterisk comes with [label] only - a projected caption owns its own marker, since only your markup knows where it belongs. New hooks: --ds-checkbox-label-color / -label-font-size, the same pair on ds-switch, and --ds-radio-label-font-size (--ds-radio-label-color already shipped). The font-size hook beats the size class. These are deliberately NOT part of the --ds-field-label-* contract: a label above an input is a heading for the field and reads secondary, a caption beside a checkbox is the content being agreed to and reads primary. If you were overriding the caption colour with a descendant selector against .control-text, replace it with the token.",
238
238
  "Overlay panels now fade out when DISMISSED and still close instantly when something is CHOSEN. No action - behaviour only. Escape, a press outside, or the page scrolling away fades the panel over --ds-motion-exit-duration (120ms); picking an option, pressing the trigger again, or Tab still closes instantly, because a fade on a deliberate choice reads as the panel lagging behind it. Applies to select, autocomplete, multi-select, date-picker, time-picker, color-picker and popover. Tune with --ds-overlay-leave-duration / --ds-overlay-leave-easing, or set the duration to 0ms to get the old always-instant close everywhere. Reduced motion already zeroes it. A fading panel is pointer-events: none, so it cannot swallow a click aimed at what is behind it. If you built anything that assumed the overlay pane is removed from the DOM synchronously on Escape, note that it now lives for one exit duration longer (the component state - open(), overlayRef - is still cleared immediately).",
239
- "design-system.md now states the --ds-* token contract once instead of repeating it per component, and carries a warning that its hand-written API and token lists have drifted from the code (ds-button is documented with its pre-color/variant API and the pre-rename --ds-button-bg / -fg names). For the authoritative surface use the auto-generated Component API tables and token reference in ds-docs, which are extracted from source on every build. No action - documentation only."
239
+ "design-system.md now states the --ds-* token contract once instead of repeating it per component, and carries a warning that its hand-written API and token lists have drifted from the code (ds-button is documented with its pre-color/variant API and the pre-rename --ds-button-bg / -fg names). For the authoritative surface use the Component API tables and token reference on the documentation site, generated from the source of each release. No action - documentation only."
240
240
  ],
241
241
  "deleteList": [
242
242
  {
@@ -89,6 +89,7 @@
89
89
  "searchHints": [
90
90
  "ds-search",
91
91
  "--ds-search-height",
92
+ "--hit-min",
92
93
  "--search-h"
93
94
  ],
94
95
  "surface": "style",
@@ -191,8 +192,8 @@
191
192
  "kind": "behavior",
192
193
  "old": "extends TableComponent",
193
194
  "new": null,
194
- "action": "Run `npm run class-surface v0.8.0 v0.9.0` for the authoritative list, then per member: rename your own, or add `override` where the base semantics genuinely match. Build after upgrading — the compiler enumerates every collision.",
195
- "appliesWhen": "Only a consumer that EXTENDS a DS component class. Subclassing is unsupported (design-system.md § Components); template users need nothing. This is not hypothetical: migrating to 0.8.0, one consumer's ids-data-table failed on exactly three.",
195
+ "action": "Build after upgrading: the compiler raises most of these collisions, but NOT the ones named in `pitfall` below — check those by hand, because they compile clean. Then per member: rename your own, or add `override` where the base semantics genuinely match.",
196
+ "appliesWhen": "Only a consumer that EXTENDS a DS component class. Subclassing is unsupported (design-system.md § Components); template users need nothing.",
196
197
  "pitfall": "Two things the compiler will NOT tell you. `isStriped()` keeps its signature but now takes an ABSOLUTE row index rather than a window-relative one, so a subclass that overrode it silently computes the wrong row. And `distinctValuesOf()` was replaced by `optionsFor()` — a subclass that CALLED the old name loses it silently at the call site while only the declaration errors. Also note both CVA bases gained a `focus()` inherited by every field control, so a subclass with its own needs `override`, and four new exported symbols can shadow a local name: FieldGroupComponent, DS_FIELD_GROUP, HeaderFilterDirective, HeaderFilterContext.",
197
198
  "note": "TableComponent changed by far the most; ModalComponent, ModalCardComponent, InputComponent, TextareaComponent, SelectComponent, AutocompleteComponent, BreadcrumbsComponent, MenuItemComponent, AppLayoutComponent, AuthLayoutComponent, TabsComponent, LayoutScrollService and both CVA bases also moved. TS4114 demands `override`, TS2415 fires on a redeclared private, TS2416 on a differing signature.",
198
199
  "searchHints": [
@@ -252,11 +253,11 @@
252
253
  }
253
254
  ],
254
255
  "informational": [
255
- "--ds-radius-inner now actually reaches the small affordances. 33 reads across fifteen component stylesheets took var(--radius-sm) directly - dropdown options, field clear buttons, calendar days, chips, tag and toast close buttons - so the role a consumer is told to retune reached exactly one component. They resolve the role now, and its default IS --radius-sm, so NOTHING MOVES: verified by measuring a component page before and after, identical surfaces at identical radii. NO ACTION, but it changes what a square brand costs you: zeroing the three roles used to leave five surfaces rounded and now leaves one. Two deliberate exclusions - five focus-ring radii inside :focus-visible keep following the raw scale (a ring traces a box, it is not a brand surface), and the shared dropdown panel behind ds-select / ds-multi-select still reads --radius-md (8px) where every other panel resolves --ds-radius-panel (12px). That last one is a tracked inconsistency, not a hook: squaring it needs the scale. Worked example on the Theming page.",
256
- "A 32px toolbar is `density=\"compact\"`, not a per-control height pin. Measured on a nine-control row: search, input, select, autocomplete, date-picker, time-picker, multi-select, number-stepper and button are all 40px by default and all 32px under [data-density=\"compact\"] on the container. DELETE-LIST MATERIAL: if you pin --ds-search-height (or any sibling) to get a shorter row - one consumer pins --hit-min and its comment complains that md used to be 36px - that pin can go, and after the height contract it was fighting the family rather than joining it. Known limit at the bottom of the scale: ds-multi-select and ds-autocomplete hold chips, so they set a min-height rather than a height and stop following the floor once it drops below what the text needs - under ultra-compact they are 33px and 29px where the rest reach 24px, because a density tier scales padding and hit targets but not the type scale. Compact is unaffected in practice (33 against 32). Documented on the Density page. (delete list: search-height-pinned-for-a-short-row)",
256
+ "--ds-radius-inner now actually reaches the small affordances. 33 reads across fifteen component stylesheets took var(--radius-sm) directly - dropdown options, field clear buttons, calendar days, chips, tag and toast close buttons - so the role a consumer is told to retune reached exactly one component. They resolve the role now, and its default IS --radius-sm, so NOTHING MOVES. NO ACTION, but it changes what a square brand costs you: zeroing the three roles used to leave five surfaces rounded and now leaves one. Two deliberate exclusions - five focus-ring radii inside :focus-visible keep following the raw scale (a ring traces a box, it is not a brand surface), and the shared dropdown panel behind ds-select / ds-multi-select still reads --radius-md (8px) where every other panel resolves --ds-radius-panel (12px). That last one is a known inconsistency, not a hook: squaring it needs the scale. Worked example on the Theming page.",
257
+ "A 32px toolbar is `density=\"compact\"`, not a per-control height pin. Measured on a nine-control row: search, input, select, autocomplete, date-picker, time-picker, multi-select, number-stepper and button are all 40px by default and all 32px under [data-density=\"compact\"] on the container. DELETE-LIST MATERIAL: if you pin --ds-search-height, or reach past it to --hit-min, to get a shorter row - that pin can go, and after the height contract it was fighting the family rather than joining it. `--hit-min` is also a legitimate density knob, so discard hits where it is set deliberately rather than to shorten a search row. Known limit at the bottom of the scale: ds-multi-select and ds-autocomplete hold chips, so they set a min-height rather than a height and stop following the floor once it drops below what the text needs - under ultra-compact they are 33px and 29px where the rest reach 24px, because a density tier scales padding and hit targets but not the type scale. Compact is unaffected in practice (33 against 32). Documented on the Density page. (delete list: search-height-pinned-for-a-short-row)",
257
258
  "SIGNAL FORMS WORK — no adapter, no wrapper, no DS import. Put [formField] from @angular/forms/signals on any DS control and the form owns the value, validation, touched and disabled state. This was ALWAYS nearly true and nobody knew: FormValueControl requires exactly one member, a `value` model(), and every DS control already had it. Measured across all fifteen controls - thirteen bound with no library change at all. Additive, NO ACTION. WHAT CHANGED HERE, and it is why the other four rules now work too: min/max/maxLength on ds-input, ds-textarea and ds-number-stepper accept undefined on the WRITE side (the binder sends it for an unset bound; the read type is untouched); `readonly` joins ds-input, ds-textarea and ds-select as the contract spelling of the existing readOnly, because signal forms binds by NAME and a readonly() rule was reaching nothing; `minLength` and `pattern` are new native attributes on ds-input and ds-textarea; and `hidden` is declared on both control-value-accessor bases, so a hidden() rule now removes the control on all thirteen that carry one. focus() is implemented too, so focusBoundControl() - the usual way to reach the first invalid field after a failed submit - lands on the element that holds the value rather than on the host, which is a <ds-*> element and not focusable, so focus previously went nowhere. It resolves per control: the stepper's number box rather than its minus button, the tabbable radio rather than the first in the DOM, a picker's trigger rather than an input inside its closed panel. NOT implemented: dirty, pending and disabledReasons - the form still tracks them, and they are blocked on a visual decision rather than wiring. ERROR TEXT still comes from your validator: required(path.email, { message: '...' }) or a provideDsConfig field.errorMessages mapping, otherwise the field goes red with no words and only a dev warning explains why. Docs: the Practice > Signal Forms page, with a live form and the measured contract table.",
258
- "ds-modal / ds-modal-card gained [dividers] (default true = today's rendering). Additive, NO ACTION - but DELETE-LIST MATERIAL if you set --ds-modal-divider: transparent. Two consumer apps did exactly that, and both were then left with header and actions padding sized to clear a rule that was no longer drawn, stacking into a 35px gap where 16px was wanted; one needed !important plus a stylelint-disable to win it back. [dividers]=\"false\" drops the rules AND the padding in one move, because those are one design decision. If you kept a deliberate --ds-modal-divider colour, nothing changes. If you set it transparent, replace it with [dividers]=\"false\" and delete whatever padding overrides you wrote afterwards - and note --ds-modal-body-pad-y now falls to 0 in that mode, so set it explicitly if you want a value in both. (delete list: modal-divider-transparent-plus-padding)",
259
- "ds-modal / ds-modal-card gained a [title-badge] content slot and a subtitle input, so a dialog header can carry a status chip and a second line without abandoning the component. Additive, NO ACTION - both are absent by default and the header renders exactly as before. WORTH A LOOK IF YOU HAND-ROLLED A DIALOG: a consumer audit found two screens that dropped ds-modal purely because the header could not hold `title + ds-badge` over a `carrier - type` line, and re-implemented the scrim, the body scroll lock, backdrop-click and Escape by hand - losing the focus trap, focus restore, the enter/leave animation and, in one case, the footer, which put a destructive action next to the close button. The shape matches ds-page-header: [title-badge] projects beside the title, subtitle is a plain string under it. The accessible name is still the title string - projected markup never enters aria-labelledby. Retune with --ds-modal-subtitle-text-color and --ds-modal-subtitle-font-size.",
259
+ "ds-modal / ds-modal-card gained [dividers] (default true = today's rendering). Additive, NO ACTION - but DELETE-LIST MATERIAL if you set --ds-modal-divider: transparent. Setting it transparent leaves the header and actions padding sized to clear a rule that is no longer drawn, stacking into a 35px gap where 16px was wanted. [dividers]=\"false\" drops the rules AND the padding in one move, because those are one design decision. If you kept a deliberate --ds-modal-divider colour, nothing changes. If you set it transparent, replace it with [dividers]=\"false\" and delete whatever padding overrides you wrote afterwards - and note --ds-modal-body-pad-y now falls to 0 in that mode, so set it explicitly if you want a value in both. (delete list: modal-divider-transparent-plus-padding)",
260
+ "ds-modal / ds-modal-card gained a [title-badge] content slot and a subtitle input, so a dialog header can carry a status chip and a second line without abandoning the component. Additive, NO ACTION - both are absent by default and the header renders exactly as before. WORTH A LOOK IF YOU HAND-ROLLED A DIALOG: a header that has to carry `title + ds-badge` over a second line used to be a reason to drop ds-modal and re-implement the scrim, the body scroll lock, backdrop-click and Escape by hand - which costs the focus trap, focus restore, the enter/leave animation and, easily, the footer, leaving a destructive action next to the close button. The shape matches ds-page-header: [title-badge] projects beside the title, subtitle is a plain string under it. The accessible name is still the title string - projected markup never enters aria-labelledby. Retune with --ds-modal-subtitle-text-color and --ds-modal-subtitle-font-size.",
260
261
  "NEW COMPONENT ds-field-group: several controls in one bordered box (select + input, input + button, search + date-picker). Additive, NO ACTION. If you hand-rolled a glued row by stripping borders off two controls and wrapping them, this replaces it - wrap them in <ds-field-group> and mark the stretching one with grow. Six controls can be segments: ds-input, ds-select, ds-search, ds-autocomplete, ds-date-picker, ds-button. ds-number-stepper and ds-multi-select are excluded by design. Grouped controls must not be given a label or hint - the message row would break the glued line and is suppressed.",
261
262
  "ds-table gained [lazy] + (lazyLoad) for fetching rows as they scroll into view. Additive and opt-in, NO ACTION. If you paged a long list yourself to keep it responsive, this is the alternative: set lazy with virtualScroll and total, make data a SPARSE array total long, and write each fetched row at its ABSOLUTE index - gaps inside the window render skeleton rows. Note sortMode must not be \"client\" (it would sort only the rows that happen to have arrived); the new server default is already right.",
262
263
  "--ds-field-height now reaches ds-autocomplete, ds-multi-select, ds-color-picker, ds-number-stepper, ds-split-button and the ds-modal confirm input. All six spelled their height as the raw --hit-* value, so the token the name advertises did nothing for them; they read the field scale now. Pixel-identical at every size EXCEPT ds-number-stepper at size=\"lg\" (its own actionable entry above). NO ACTION unless you had already worked around the gap by pinning height on one of these - that pin can go.",
@@ -268,9 +269,9 @@
268
269
  "ds-date-picker and ds-time-picker resolve their trigger's horizontal padding from --field-pad-x (new hooks: --ds-date-picker-trigger-pad-x, --ds-time-picker-trigger-pad-x) instead of a hard-coded --space-3. Identical at the default density; the difference shows under [data-density], where the token shrinks and the literal did not, leaving a picker 8px wider than the input beside it. NO ACTION unless you hand-pinned picker padding to compensate.",
269
270
  "The ds-auth-shell -> ds-auth-layout rename is vocabulary only: no input, output, slot, token value or behaviour changed, and it is the same component 0.8.0 shipped. If you never adopted ds-auth-shell (it was added in 0.8.0), there is nothing to do.",
270
271
  "FIXED in ds-textarea: size=\"sm\" and size=\"lg\" rendered the md vertical padding (12px top and bottom) regardless of the size. The size blocks set the inner textarea's vertical pad, but a :host-prefixed pin at the end of the file out-ranked them once emulated encapsulation shimmed both selectors - it carries one more attribute than the size selector. There are now three pins, one per size, and the size blocks keep only the horizontal padding they own. NO ACTION: the change is visible only on a non-md textarea and the md default is unchanged. Note that retuning --ds-input-pad-y previously moved all three sizes together; if you compensated for the wrong padding with your own override on a sm or lg textarea, that override now stacks on the corrected value and can go.",
271
- "ds-auth-layout now COMPRESSES its own chrome on a short viewport: block padding, the column gap, the letter-mark tile and the masthead inner gap clamp against svh. No action - behaviour only, and a viewport 800px tall or more renders exactly what it did before. Read that as a VIEWPORT height, not a screen size: a 1366x768 laptop sits near 630px after browser and OS chrome, and a 1080p screen at 150% display scaling near 585px, so plenty of desktops do get the compressed furniture - an earlier wording of this line said 'so desktop is unchanged', which was wrong. Type is deliberately NOT clamped: the wordmark and the tile's glyph were measured to buy zero vertical space (the tile sets the row height at every viewport, and the glyph sits in a fixed-size box) while flattening the brand against a fixed 14px tagline, so both keep the fixed sizes 0.8.0 ships. Below 800px the remaining furniture shrinks so it is not what pushes a card into scrolling (~131px instead of ~219px at a landscape phone's ~330px). Two tokens opt out per dimension: --ds-auth-layout-pad-block and --ds-auth-layout-mark-size; setting any of those or the existing --ds-auth-layout-gap to a fixed value stops that one compressing. A card taller than the remaining space still scrolls - that is intended.",
272
+ "ds-auth-layout now COMPRESSES its own chrome on a short viewport: block padding, the column gap, the letter-mark tile and the masthead inner gap clamp against svh. No action - behaviour only, and a viewport 800px tall or more renders exactly what it did before. Read that as a VIEWPORT height, not a screen size: a 1366x768 laptop sits near 630px after browser and OS chrome, and a 1080p screen at 150% display scaling near 585px, so plenty of desktops do get the compressed furniture. Type is deliberately NOT clamped: the wordmark and the tile's glyph were measured to buy zero vertical space (the tile sets the row height at every viewport, and the glyph sits in a fixed-size box) while flattening the brand against a fixed 14px tagline, so both keep the fixed sizes 0.8.0 ships. Below 800px the remaining furniture shrinks so it is not what pushes a card into scrolling (~131px instead of ~219px at a landscape phone's ~330px). Two tokens opt out per dimension: --ds-auth-layout-pad-block and --ds-auth-layout-mark-size; setting any of those or the existing --ds-auth-layout-gap to a fixed value stops that one compressing. A card taller than the remaining space still scrolls - that is intended.",
272
273
  "ds-auth-layout audit fixes, all additive or corrective - NO ACTION. The letter-mark tile is now aria-hidden (a screen reader announced 'A MyAdmin', now 'MyAdmin') and carries flex-shrink: 0 so a long wordmark cannot squash it out of square; logoLetter on its own renders its tile instead of nothing; the glyph is taken by code point rather than charAt(0), which returned half a surrogate pair for a brand starting with an emoji; box-sizing: border-box is declared on the host rather than inherited, so the component still avoids its own overflow scrollbar for a consumer composing style partials without styles/reset. The four env(safe-area-inset-*) calls gained 0px fallbacks and moved to physical padding-left/padding-right so the insets cannot swap sides under RTL - and note they are inert unless YOUR app sets viewport-fit=cover in its viewport meta, which the library cannot set for you. New tokens, both defaulting to today's behaviour: --ds-auth-layout-mark-radius (the tile's radius was the one value with no override hop) and --ds-auth-layout-brand-max-height (none by default; set it to cap a projected [brand] logo, which nothing constrained). New input landmark, default 'none': set landmark=\"main\" on a standalone auth page so the card - an <article>, which is not a landmark - becomes something a screen-reader user can jump to; it stays opt-in because this layout is also embedded inside pages that already own a main.",
273
- "ds-icon now logs a dev-mode warning when an icon name is in neither the DS set nor your provideDsIcons() registry - previously it rendered an empty <svg> silently. No action, and nothing changes in production. Expect the warning to surface real typos the moment you upgrade: an audit of three screens in one consumer is what prompted it.",
274
+ "ds-icon now logs a dev-mode warning when an icon name is in neither the DS set nor your provideDsIcons() registry - previously it rendered an empty <svg> silently. No action, and nothing changes in production. Expect the warning to surface real typos the moment you upgrade.",
274
275
  "ds-app-layout gained scrollReset: \"path\" | \"never\" | \"always\" (default \"path\" = existing behaviour, so NO ACTION), and LayoutNavigationService is now exported. If you wrote your own \"did the path change?\" check to work around the layout resetting scroll - or to skip a view transition, or to reset a tab - replace it with inject(LayoutNavigationService).pathChanged: it is NavigationEnd, path only, de-duplicated, and it skips a navigation carrying state: { dsSamePage: true }. Note a naive split(\"?\") is NOT equivalent, it keeps the fragment this stream strips. To stop the layout resetting scroll on a paged or filtered list, set scrollReset=\"never\" and call LayoutScrollService.scrollToTop() where you actually want it.",
275
276
  "Options in ds-select / ds-autocomplete / ds-multi-select panels now have a pressed state (they had hover only, which does nothing on touch). No action - visual only. If you styled :active on .option yourself to work around it, you can drop that override; if you want a different pressed fill, it reads --surface-muted (neutral rows) and --primary-subtitle (the selected row). (delete list: dropdown-option-active-override)",
276
277
  "ds-table gained filterMode: \"client\" | \"server\" | \"none\" and columnFilterOptions. It resolves to \"server\" when unset - see the table-sort-filter-mode-default-server item, which is where the action for that lives. If your table is server-paged (you bind `total`) and any column has filter: \"set\", you WANT filterMode=\"server\" plus columnFilterOptions with the real value domain - otherwise the checklist offers only the values on the current page and then filters locally on top of the server. A dev warning now points this out.",
@@ -283,7 +284,7 @@
283
284
  "ds-date-picker keeps its trigger indicator while the panel is open (an \"open\" class alongside the focus rules). Visual only, NO ACTION. If you styled .trigger:focus-within yourself to work around the trigger going dark, you can drop it. (delete list: date-picker-trigger-focus-within-override)",
284
285
  "ds-autocomplete in single mode collapses its filter input once a value is chosen and the panel is closed, so the field reads as a picker instead of a text box. Visual only, NO ACTION. Clicking the field still opens the panel and expands the input, and typing still filters. If you set --ds-autocomplete-input-minw to work around the empty box, you can drop it. (delete list: autocomplete-input-minw-override)",
285
286
  "ds-date-picker: clicking the calendar glyph no longer moves focus into the day grid. It now behaves like a click on the field - with allowInput (the default) the caret stays in the field, and a read-only field still focuses the grid. No action; ArrowDown on the field enters the grid as before. If you scripted tests that assumed a glyph click lands focus on a day button, they need updating.",
286
- "WHAT THE DELETE LIST COVERS - the half a release note usually leaves out. Two dogfooding audits (mm-ecm 2026-08-06, mm-broker 2026-08-07) read consumer stylesheets as a record of what this library made them write, and both found the same thing: most of the workarounds were written against hooks that ALREADY existed, because a release note says what broke and never says what became unnecessary. Each line below is SEARCH-FOR -> WHY IT CAN GO. None of it is required: skipping it leaves working code that is merely redundant. How to sweep for the rest: grep your styles for ::ng-deep, !important, and any selector naming a DS internal class (.button, .trigger, .option, .modal) - each hit is either an entry below or a genuine gap worth reporting."
287
+ "WHAT THE DELETE LIST COVERS - the half a release note usually leaves out. Most of the workarounds are written against hooks that ALREADY existed, because a release note says what broke and never says what became unnecessary. Each line below is SEARCH-FOR -> WHY IT CAN GO. None of it is required: skipping it leaves working code that is merely redundant. How to sweep for the rest: grep your styles for ::ng-deep, !important, and any selector naming a DS internal class (.button, .trigger, .option, .modal) - each hit is either an entry below or a genuine gap worth reporting."
287
288
  ],
288
289
  "deleteList": [
289
290
  {
@@ -2,10 +2,10 @@
2
2
  "version": "0.9.1",
3
3
  "items": [],
4
4
  "informational": [
5
- "Nothing in this release changes the package's runtime. Its entire src/ diff is JSDoc, which feeds the generated token and component reference; every component behaves exactly as it did on 0.9.0.",
5
+ "Nothing in this release changes the package's runtime. The entire change is documentation, feeding the token and component reference; every component behaves exactly as it did on 0.9.0.",
6
6
  "THREE documented behaviours were guessable wrong, so check these if you use them - the code always worked this way, only the reference was silent. (1) ds-time-columns `value` is always HH:mm in 24h and `format` changes only the DISPLAY, so a picker showing 12h still emits 24h - code that parsed the emitted value as 12h was wrong. (2) ds-time-columns `minTime`/`maxTime` DISABLE the out-of-range rows rather than removing them, so the columns keep their height as a bound moves - a layout that assumed the list shortens was wrong. (3) ds-calendar-day `tabIndex` is a roving tabindex owned by the grid (exactly one cell at 0, the rest at -1), not a tab position to set per day - setting it per cell fights the grid's keyboard model.",
7
7
  "41 public tokens and props gained descriptions in the reference: 10 --ds-* tokens (the whole --ds-password-rules-* set, --ds-multi-select-panel-bg-color and --ds-menu-item-radius among them) and 31 inputs and outputs across ds-calendar-day, ds-time-columns, ds-field-message, ds-divider, ds-sidenav-footer and the three layout primitives. Names, types and defaults are unchanged.",
8
- "Every version's migration manifest now carries its DELETE-LIST entries, so an upgrade tool can act on what a release made UNNECESSARY and not only on what it broke. 0.9.0 has 21 of them. They existed before only in a prose file no tooling read, and that file has been retired."
8
+ "A release manifest carries a deleteList wherever that release made a workaround unnecessary, so an upgrade tool can act on what became redundant and not only on what broke. Each row is machine-readable: { id, surface, find, why, replaceWith }."
9
9
  ],
10
10
  "deleteList": []
11
11
  }