@ids-group-ltd/ids-design-system 0.10.3 → 0.11.0

This diff represents the content of publicly available package versions that have been released to one of the supported registries. The information contained in this diff is provided for informational purposes only and reflects changes between package versions as they appear in their respective public registries.
@@ -3,7 +3,25 @@
3
3
  "items": [],
4
4
  "informational": [
5
5
  "ds-date-picker's panel now closes when ANY ancestor scroll container scrolls, not only the one 0.6.0 watched. Nothing to change: a panel that used to hang over the page while a nested pane scrolled underneath now dismisses itself.",
6
- "ds-date-picker masked typing works on mobile keyboards. Segment-aware editing was wired to keydown, which soft keyboards (Gboard among them) do not report faithfully; the mobile path now goes through beforeinput. If you shipped a workaround that bypassed the masked field on touch devices, it can go.",
6
+ "ds-date-picker masked typing works on mobile keyboards. Segment-aware editing was wired to keydown, which soft keyboards (Gboard among them) do not report faithfully; the mobile path now goes through beforeinput. If you shipped a workaround that bypassed the masked field on touch devices, it can go. (delete list: date-picker-touch-bypass-workaround)",
7
7
  "ds-date-picker's panel no longer sets aria-modal. The calendar is non-modal - the page stays interactive behind it - so the attribute told screen readers something untrue. No API changed; an assistive-tech test that asserted aria-modal on this panel needs updating."
8
+ ],
9
+ "deleteList": [
10
+ {
11
+ "id": "date-picker-touch-bypass-workaround",
12
+ "surface": [
13
+ "template",
14
+ "typescript"
15
+ ],
16
+ "find": [
17
+ "ds-date-picker",
18
+ "pointer: coarse",
19
+ "ontouchstart",
20
+ "matchMedia",
21
+ "type=\"date\""
22
+ ],
23
+ "why": "A branch that swapped ds-date-picker for a native input, or disabled its masked typing, on touch devices. It existed because segment-aware editing was wired to keydown, which soft keyboards do not report faithfully; the mobile path goes through beforeinput now, so the masked field works there.",
24
+ "replaceWith": "nothing - render ds-date-picker on touch as well"
25
+ }
8
26
  ]
9
27
  }
@@ -6,7 +6,9 @@
6
6
  "kind": "behavior",
7
7
  "old": "ds-bottom-sheet",
8
8
  "new": null,
9
- "note": "ds-bottom-sheet's Escape handler moved from the DOCUMENT to its own panel, matching ds-modal and ds-drawer. Why it changed: with stacked overlays a background sheet was swallowing the Escape meant for whatever sat on top. ACTION, and it is a real one: Escape now has to land on the panel, which the focus trap arranges by auto-capturing focus inside it - so a sheet whose body contains NOTHING FOCUSABLE can no longer be closed with Escape. If you have such a sheet (a purely informational one, say), give it a focusable element: the close button in its header is enough. CHECK: open each sheet, press Escape without clicking anything first.",
9
+ "action": "Open each sheet and press Escape without clicking anything first. If one does not close, give its body something focusable — the close button in its header is enough.",
10
+ "pitfall": "A sheet whose body contains NOTHING focusable can no longer be dismissed with Escape at all: the key has to land on the panel, and the focus trap only gets it there by capturing focus inside. A purely informational sheet is exactly the shape that has nothing to focus, and a keyboard user is then stuck in it.",
11
+ "note": "The Escape handler moved from the document to the panel, matching ds-modal and ds-drawer, because with stacked overlays a background sheet was swallowing the Escape meant for whatever sat on top.",
10
12
  "searchHints": [
11
13
  "ds-bottom-sheet",
12
14
  "bottom-sheet",
@@ -6,7 +6,9 @@
6
6
  "kind": "input-rename",
7
7
  "old": "ds-date-picker[defaultMonth]",
8
8
  "new": "defaultDate",
9
- "note": "Pure rename, behavior unchanged: the input always took a full Date and the calendar opens on its month with grid focus on its exact day (only when the value is empty; never written to the value). [defaultMonth] -> [defaultDate]. No other component has a defaultMonth input.",
9
+ "action": "Rename `[defaultMonth]` to `[defaultDate]` on ds-date-picker.",
10
+ "appliesWhen": "No other component has a defaultMonth input, so the rename is unambiguous.",
11
+ "note": "Behaviour is unchanged: the input always took a full Date, and the calendar still opens on its month with grid focus on its exact day — only while the value is empty, and never written into the value.",
10
12
  "searchHints": [
11
13
  "[defaultMonth]",
12
14
  "defaultMonth"
@@ -18,7 +20,10 @@
18
20
  "kind": "behavior",
19
21
  "old": null,
20
22
  "new": null,
21
- "note": "ds-table row hover tint is now rendered ONLY when rowInteractive is set (clickable rows also gain a pressed :active fill via --ds-table-row-pressed-bg-color). Was: every table tinted rows on hover. No code compiles differently — visual/behavior only. If a passive table must keep the old always-on hover, add consumer CSS: ds-table tbody tr:hover td { background-color: var(--surface-secondary); }. Tables that already set rowInteractive need no action.",
23
+ "action": "None, unless a passive table must keep its hover tint. To keep it: `ds-table tbody tr:hover td { background-color: var(--surface-secondary); }`.",
24
+ "appliesWhen": "Tables that already set `rowInteractive` need nothing — they keep the tint and gain a pressed fill.",
25
+ "pitfall": "Nothing compiles differently, so this only shows on screen. A table that reads as clickable because of the hover tint, without ever having been clickable, quietly loses the affordance it should not have had.",
26
+ "note": "The row hover tint is rendered only when `rowInteractive` is set; clickable rows also gain a pressed `:active` fill through `--ds-table-row-pressed-bg-color`.",
22
27
  "searchHints": [
23
28
  "<ds-table",
24
29
  "rowInteractive"
@@ -36,7 +41,10 @@
36
41
  "kind": "behavior",
37
42
  "old": null,
38
43
  "new": null,
39
- "note": "Only affects a consumer that EXTENDS the DS TableComponent class. Subclassing a DS component is unsupported (design-system.md - Components), but where it happens this release breaks the build: the new column API added ~76 members to TableComponent, so a subclass that already used one of those names no longer compiles — TS4114 requires an 'override' modifier, TS2416 fires where the signature differs. Collisions observed: zebra, columnOrder, orderedColumns, visibleColumns, toggleColumn, onColumnDrop, moveColumn, resetColumns, columnFilters, exportCsv, onResizeMove, onResizeEnd. Resolution per member: where the base member means the same thing, keep the name and add `override` with a base-compatible signature (zebra must adopt the base's booleanAttribute transform); otherwise RENAME the subclass's own member — the private/protected ones are internal to the component and its own template, so renaming is behaviour-preserving, but check the new name against the base's member list so it does not collide again. Build the consumer right after the bump: the compiler enumerates every collision. A consumer that only uses the <ds-table> element needs no action.",
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.",
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
+ "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
+ "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.",
40
48
  "searchHints": [
41
49
  "extends TableComponent",
42
50
  "extends "
@@ -73,5 +81,6 @@
73
81
  "New ds-app-shell — a slotted fixed-frame application shell ([sidenav]/[topbar]/default content slots) that pins to the viewport (100dvh, overflow: hidden) so only the content <main> scrolls (scrollbar-gutter: stable + automatic native-scrollbar-width padding compensation via the new --ds-scrollbar-width root variable); topbarSpan input ('content' default full-height rail | 'full' full-width topbar) switches the geometry; scroll-to-top on router navigation via the new exported ShellScrollService (also injectable from routed pages for manual scrollToTop()). Tokens: --ds-app-shell-pad-x/-pad-y/-content-max-width/-height — additive, no code change.",
74
82
  "New ds-sidenav-footer — a rail footer brick: Search row with a live grouped-results popover, Alerts row with an unread dot + feed popover, Collapse row, and a user card with an account menu; inputs userName/userRole/alerts/collapsed/searchProvider/alertItems/profileRoute, outputs collapseToggled/alertsOpened/signOutSelected; new exported types SidenavSearchProvider/SidenavSearchResult/SidenavAlertItem. Tokens: --ds-sidenav-footer-popover-width/-popover-max-width/-popover-max-height/-head-tracking/-dot-size — additive, no code change.",
75
83
  "ds-sidenav gains an optional logoLetter input (sets the brand-tile glyph when it differs from the brand's first letter) and a [dsBrandName] projection slot (exported marker directive BrandNameDirective) that renders custom wordmark markup inside .brand-name in place of the plain brand text — both optional, omitting them renders exactly as before, additive, no code change."
76
- ]
84
+ ],
85
+ "deleteList": []
77
86
  }
@@ -6,7 +6,8 @@
6
6
  "kind": "type-rename",
7
7
  "old": "IconButtonSize",
8
8
  "new": "DsSize",
9
- "note": "The per-component size scale is now the shared `DsSize` ('sm'|'md'|'lg'), exported from the package root. Rename this type BEFORE `ButtonSize` — this identifier contains it, so an unordered replace would corrupt it. Collapse any duplicate `DsSize` imports that result.",
9
+ "action": "Replace `IconButtonSize` with `DsSize`, imported from the package root. Apply this BEFORE `ButtonSize`.",
10
+ "pitfall": "`IconButtonSize` CONTAINS `ButtonSize`. Renaming the shorter one first leaves `IconDsSize`, an identifier that exists nowhere — and the two items are adjacent in this file, so the wrong order is the natural one.",
10
11
  "searchHints": [
11
12
  "IconButtonSize"
12
13
  ],
@@ -17,7 +18,8 @@
17
18
  "kind": "type-rename",
18
19
  "old": "ButtonSize",
19
20
  "new": "DsSize",
20
- "note": "Removed — use the shared `DsSize` from the package root. Rename `IconButtonSize` FIRST (it contains `ButtonSize`). Collapse any duplicate `DsSize` imports.",
21
+ "action": "Replace `ButtonSize` with `DsSize`, imported from the package root. Apply `IconButtonSize` first.",
22
+ "pitfall": "`IconButtonSize` contains this name — rename the longer identifier first, or match whole identifiers.",
21
23
  "searchHints": [
22
24
  "ButtonSize"
23
25
  ],
@@ -28,7 +30,7 @@
28
30
  "kind": "type-rename",
29
31
  "old": "InputSize",
30
32
  "new": "DsSize",
31
- "note": "Removed — use the shared `DsSize` from the package root; collapse any duplicate `DsSize` imports if you import several of these together.",
33
+ "action": "Replace `InputSize` with `DsSize`, imported from the package root.",
32
34
  "searchHints": [
33
35
  "InputSize"
34
36
  ],
@@ -39,7 +41,7 @@
39
41
  "kind": "type-rename",
40
42
  "old": "SelectSize",
41
43
  "new": "DsSize",
42
- "note": "Removed — use the shared `DsSize` from the package root; collapse any duplicate `DsSize` imports.",
44
+ "action": "Replace `SelectSize` with `DsSize`, imported from the package root.",
43
45
  "searchHints": [
44
46
  "SelectSize"
45
47
  ],
@@ -50,7 +52,7 @@
50
52
  "kind": "type-rename",
51
53
  "old": "SearchSize",
52
54
  "new": "DsSize",
53
- "note": "Removed — use the shared `DsSize` from the package root; collapse any duplicate `DsSize` imports.",
55
+ "action": "Replace `SearchSize` with `DsSize`, imported from the package root.",
54
56
  "searchHints": [
55
57
  "SearchSize"
56
58
  ],
@@ -61,7 +63,7 @@
61
63
  "kind": "type-rename",
62
64
  "old": "CheckboxSize",
63
65
  "new": "DsSize",
64
- "note": "Removed — use the shared `DsSize` from the package root; collapse any duplicate `DsSize` imports.",
66
+ "action": "Replace `CheckboxSize` with `DsSize`, imported from the package root.",
65
67
  "searchHints": [
66
68
  "CheckboxSize"
67
69
  ],
@@ -72,7 +74,7 @@
72
74
  "kind": "type-rename",
73
75
  "old": "RadioSize",
74
76
  "new": "DsSize",
75
- "note": "Removed — use the shared `DsSize` from the package root; collapse any duplicate `DsSize` imports.",
77
+ "action": "Replace `RadioSize` with `DsSize`, imported from the package root.",
76
78
  "searchHints": [
77
79
  "RadioSize"
78
80
  ],
@@ -83,7 +85,7 @@
83
85
  "kind": "type-rename",
84
86
  "old": "SwitchSize",
85
87
  "new": "DsSize",
86
- "note": "Removed — use the shared `DsSize` from the package root; collapse any duplicate `DsSize` imports.",
88
+ "action": "Replace `SwitchSize` with `DsSize`, imported from the package root.",
87
89
  "searchHints": [
88
90
  "SwitchSize"
89
91
  ],
@@ -94,7 +96,7 @@
94
96
  "kind": "type-rename",
95
97
  "old": "SpinnerSize",
96
98
  "new": "DsSize",
97
- "note": "Removed — use the shared `DsSize` from the package root; collapse any duplicate `DsSize` imports.",
99
+ "action": "Replace `SpinnerSize` with `DsSize`, imported from the package root.",
98
100
  "searchHints": [
99
101
  "SpinnerSize"
100
102
  ],
@@ -105,7 +107,7 @@
105
107
  "kind": "type-rename",
106
108
  "old": "TextareaSize",
107
109
  "new": "DsSize",
108
- "note": "Removed — use the shared `DsSize` from the package root; collapse any duplicate `DsSize` imports.",
110
+ "action": "Replace `TextareaSize` with `DsSize`, imported from the package root.",
109
111
  "searchHints": [
110
112
  "TextareaSize"
111
113
  ],
@@ -116,7 +118,7 @@
116
118
  "kind": "type-rename",
117
119
  "old": "NumberStepperSize",
118
120
  "new": "DsSize",
119
- "note": "Removed — use the shared `DsSize` from the package root; collapse any duplicate `DsSize` imports.",
121
+ "action": "Replace `NumberStepperSize` with `DsSize`, imported from the package root.",
120
122
  "searchHints": [
121
123
  "NumberStepperSize"
122
124
  ],
@@ -127,7 +129,7 @@
127
129
  "kind": "type-rename",
128
130
  "old": "DatePickerSize",
129
131
  "new": "DsSize",
130
- "note": "Removed — use the shared `DsSize` from the package root; collapse any duplicate `DsSize` imports.",
132
+ "action": "Replace `DatePickerSize` with `DsSize`, imported from the package root.",
131
133
  "searchHints": [
132
134
  "DatePickerSize"
133
135
  ],
@@ -138,7 +140,7 @@
138
140
  "kind": "type-rename",
139
141
  "old": "TimePickerSize",
140
142
  "new": "DsSize",
141
- "note": "Removed — use the shared `DsSize` from the package root; collapse any duplicate `DsSize` imports.",
143
+ "action": "Replace `TimePickerSize` with `DsSize`, imported from the package root.",
142
144
  "searchHints": [
143
145
  "TimePickerSize"
144
146
  ],
@@ -149,7 +151,7 @@
149
151
  "kind": "type-rename",
150
152
  "old": "DrawerSize",
151
153
  "new": "DsSize",
152
- "note": "Removed — use the shared `DsSize` from the package root; collapse any duplicate `DsSize` imports.",
154
+ "action": "Replace `DrawerSize` with `DsSize`, imported from the package root.",
153
155
  "searchHints": [
154
156
  "DrawerSize"
155
157
  ],
@@ -160,7 +162,7 @@
160
162
  "kind": "type-rename",
161
163
  "old": "AutocompleteSize",
162
164
  "new": "DsSize",
163
- "note": "Removed — use the shared `DsSize` from the package root; collapse any duplicate `DsSize` imports.",
165
+ "action": "Replace `AutocompleteSize` with `DsSize`, imported from the package root.",
164
166
  "searchHints": [
165
167
  "AutocompleteSize"
166
168
  ],
@@ -171,7 +173,9 @@
171
173
  "kind": "output-rename",
172
174
  "old": "ds-pagination[pageChange]",
173
175
  "new": "currentPageChange",
174
- "note": "The manual (pageChange) output is removed; the currentPage two-way model already emits (currentPageChange) on every page change (including the reset to page 1 after a size change). Rename (pageChange)=\"...\" to (currentPageChange)=\"...\" on ds-pagination. (pageSizeChange) is UNCHANGED — it is now the pageSize model's implicit output, same name and payload; [(currentPage)] / [(pageSize)] two-way bindings need no change.",
176
+ "action": "Rename `(pageChange)` to `(currentPageChange)` on ds-pagination.",
177
+ "appliesWhen": "`(pageSizeChange)` is unchanged — it is the pageSize model implicit output now, same name and payload. `[(currentPage)]` and `[(pageSize)]` two-way bindings need nothing.",
178
+ "note": "The manual output is gone: the `currentPage` model already emits on every page change, including the reset to page 1 after a size change.",
175
179
  "searchHints": [
176
180
  "(pageChange)",
177
181
  "pageChange"
@@ -183,7 +187,9 @@
183
187
  "kind": "removed-api",
184
188
  "old": "ds-input[withAddon]",
185
189
  "new": null,
186
- "note": "Removed (distinct from withAddonRight below — match the exact attribute; withAddon is a substring of withAddonRight). The flush-addon layout is now derived from the DOM: a boxed .addon projected into [dsInputPrefix] (<span dsInputPrefix class=\"addon\">…</span>) sits flush automatically via :has(), and a bare <ds-icon dsInputPrefix> keeps its inset. Delete the [withAddon] attribute — a boxed addon renders identically; a bare icon that used the flag regains its proper left inset (bugfix).",
190
+ "action": "Delete the `[withAddon]` attribute.",
191
+ "pitfall": "`withAddon` is a SUBSTRING of `withAddonRight`, so a loose match deletes both and the trailing item below never fires. Match the exact attribute. Separately, a bare `<ds-icon dsInputPrefix>` that carried the flag regains its proper left inset — that shift is the bugfix, not a regression.",
192
+ "note": "The flush-addon layout is derived from the DOM now: a boxed `.addon` projected into `[dsInputPrefix]` sits flush through `:has()`, and a bare icon keeps its inset.",
187
193
  "searchHints": [
188
194
  "[withAddon]"
189
195
  ],
@@ -195,7 +201,8 @@
195
201
  "kind": "removed-api",
196
202
  "old": "ds-input[withAddonRight]",
197
203
  "new": null,
198
- "note": "Removed — the trailing counterpart of withAddon. A boxed .addon.right projected into [dsInputSuffix] now sits flush automatically via :has(). Delete the [withAddonRight] attribute.",
204
+ "action": "Delete the `[withAddonRight]` attribute.",
205
+ "note": "The trailing counterpart: a boxed `.addon.right` in `[dsInputSuffix]` sits flush through `:has()` now.",
199
206
  "searchHints": [
200
207
  "[withAddonRight]"
201
208
  ],
@@ -207,7 +214,8 @@
207
214
  "kind": "selector-rename",
208
215
  "old": "ds-app-shell",
209
216
  "new": "ds-app-layout",
210
- "note": "Component renamed (shipped as ds-app-shell in the tagged 0.6.3 source). Behaviour unchanged — rename the element and its closing tag. Also rename the class, service and tokens (separate entries below).",
217
+ "action": "Rename the element and its closing tag from `ds-app-shell` to `ds-app-layout`, then apply the class, service and token items below.",
218
+ "note": "Behaviour is unchanged; the component shipped as ds-app-shell in the tagged 0.6.3 source.",
211
219
  "searchHints": [
212
220
  "ds-app-shell"
213
221
  ],
@@ -218,7 +226,7 @@
218
226
  "kind": "type-rename",
219
227
  "old": "AppShellComponent",
220
228
  "new": "AppLayoutComponent",
221
- "note": "The exported component class renamed alongside the ds-app-shell → ds-app-layout selector. Update imports / type references.",
229
+ "action": "Replace `AppShellComponent` with `AppLayoutComponent`.",
222
230
  "searchHints": [
223
231
  "AppShellComponent"
224
232
  ],
@@ -229,7 +237,7 @@
229
237
  "kind": "type-rename",
230
238
  "old": "ShellScrollService",
231
239
  "new": "LayoutScrollService",
232
- "note": "The exported scroll-to-top-on-navigation service renamed with the app-shell → app-layout rename. Update inject()/import references; the scrollToTop() API is unchanged.",
240
+ "action": "Replace `ShellScrollService` with `LayoutScrollService`.",
233
241
  "searchHints": [
234
242
  "ShellScrollService"
235
243
  ],
@@ -240,7 +248,8 @@
240
248
  "kind": "token-rename",
241
249
  "old": "--ds-app-shell-",
242
250
  "new": "--ds-app-layout-",
243
- "note": "Prefix rename for the four layout tokens: --ds-app-shell-pad-x / -pad-y / -content-max-width / -height → --ds-app-layout-*. DS-owned tokens only (no others ship under this prefix); a consumer's own --ds-app-shell-* variable is out of scope. Confirm the new name exists in the installed package.",
251
+ "action": "Replace the prefix `--ds-app-shell-` with `--ds-app-layout-` on the four layout tokens: `-pad-x`, `-pad-y`, `-content-max-width`, `-height`.",
252
+ "appliesWhen": "DS-owned tokens only — no others ship under this prefix, and a variable of your own is out of scope.",
244
253
  "searchHints": [
245
254
  "--ds-app-shell-"
246
255
  ],
@@ -251,7 +260,9 @@
251
260
  "kind": "behavior",
252
261
  "old": null,
253
262
  "new": null,
254
- "note": "ds-select's clear-x is now keyboard-operable: the trigger changed from <button role=\"combobox\"> to <div role=\"combobox\" tabindex=\"0\">, and the clear affordance from a mouse-only <span aria-hidden> to a real <button aria-label=\"Clear selection\">. Nothing stops compiling, but a consumer that targeted the old <button role=combobox> trigger or the <span> clear in CSS selectors or e2e/unit tests must retarget to the div / the button.",
263
+ "action": "Retarget any CSS selector or e2e/unit test that named the old trigger or clear element: the trigger is a `div role=\"combobox\" tabindex=\"0\"` now, and the clear is a real `button aria-label=\"Clear selection\"`.",
264
+ "pitfall": "Nothing stops compiling, so this lands green and fails later — a selector like `ds-select button[role=combobox]` simply matches nothing, and a test that clicked the old `<span>` clear now clicks air.",
265
+ "note": "The clear affordance became keyboard-operable, which meant the trigger could no longer be a button wrapping another button.",
255
266
  "searchHints": [
256
267
  "ds-select",
257
268
  "role=\"combobox\"",
@@ -274,7 +285,10 @@
274
285
  "kind": "behavior",
275
286
  "old": null,
276
287
  "new": null,
277
- "note": "Message-bearing fields (ds-input, ds-textarea, ds-select, ds-autocomplete, ds-multi-select, ds-checkbox, ds-radio, ds-radio-group, ds-switch, ds-slider, ds-otp-input, ds-date-picker, ds-time-picker, ds-color-picker) now reserve one message line of height by DEFAULT via the new reserveMessage input (default true). Was: the footer existed only when a hint/error/counter was present, so a field with no message was shorter and grew when a message first appeared. Purely visual — nothing stops compiling. To restore the old collapsing behaviour on a field, set [reserveMessage]=\"false\". Review form vertical rhythm: the reserved row sits ~23px under the control, so tightly-stacked field pairs may read as a gap. (ds-search and ds-number-stepper have no message row and are NOT affected.)",
288
+ "action": "Look at the vertical rhythm of your forms. To bring back the collapsing footer on a field, set `[reserveMessage]=\"false\"`.",
289
+ "appliesWhen": "The fourteen message-bearing fields only. ds-search and ds-number-stepper have no message row and are untouched.",
290
+ "pitfall": "Purely visual and nothing stops compiling, so it ships unless somebody looks: the reserved row sits about 23px under the control, and a tightly stacked pair of fields now reads as a deliberate gap between them.",
291
+ "note": "The footer used to exist only once a hint, error or counter was present, so a field with no message was shorter and grew when one first appeared. `reserveMessage` defaults to true now.",
278
292
  "searchHints": [
279
293
  "<ds-input",
280
294
  "<ds-textarea",
@@ -297,7 +311,10 @@
297
311
  "kind": "behavior",
298
312
  "old": null,
299
313
  "new": null,
300
- "note": "Only affects a consumer that EXTENDS a DS component class. Subclassing is unsupported (design-system.md - Components), but where it happens this release can break the build the same way 0.6.3 did: TableComponent gained total, sortingOrder, animateHeight and scrollToTopOnPageChange, and most other component classes changed too, so a subclass that already used one of those names no longer compiles — TS4114 requires an 'override' modifier, TS2416 fires where the signature differs. Resolution per member: where the base member means the same thing, keep the name and add `override` with a base-compatible signature; otherwise RENAME the subclass's own member, checking the new name against the base's member list first. Build the consumer right after the bump: the compiler enumerates every collision. A consumer that only uses the DS elements needs no action.",
314
+ "action": "Build the consumer immediately after the bump — the compiler enumerates every collision. Per member: keep the name and add `override` with a base-compatible signature where the base means the same thing, otherwise rename your own member. TableComponent gained `total`, `sortingOrder`, `animateHeight` and `scrollToTopOnPageChange`.",
315
+ "appliesWhen": "Only a consumer that EXTENDS a DS component class. Subclassing is unsupported (design-system.md § Components); anyone using the DS elements is unaffected.",
316
+ "pitfall": "It is not only the table this time — most component classes changed, so fixing the collisions the compiler names first can still leave others in files it has not reached. Check any renamed member against the base member list before settling on the new name.",
317
+ "note": "A subclass that already used one of the added names stops compiling: TS4114 wants an `override` modifier, TS2416 fires where the signature differs.",
301
318
  "searchHints": [
302
319
  "extends TableComponent",
303
320
  "extends "
@@ -312,6 +329,7 @@
312
329
  }
313
330
  ],
314
331
  "informational": [
332
+ "Fifteen per-component size types collapsed into one shared `DsSize` (`sm | md | lg`) exported from the package root - IconButtonSize, ButtonSize, InputSize, SelectSize, SearchSize, CheckboxSize, RadioSize, SwitchSize, SpinnerSize, TextareaSize, NumberStepperSize, DatePickerSize, TimePickerSize, DrawerSize and AutocompleteSize. Each has its own item above. After the renames a file that imported several of them holds several identical `DsSize` imports; collapse them.",
315
333
  "AvatarSize, ModalSize and ContainerSize are NOT removed — they remain and now extend DsSize ('xs' | DsSize, DsSize | 'xl' | 'fullscreen', DsSize | 'xl' | 'full'); no change needed for consumers using those three.",
316
334
  "ds-avatar gains deterministic seeded tinting: [seed]/[avoidHues] inputs derive a stable per-person OKLCH background + auto-contrast text; standalone exports avatarTint(seed, options), AvatarTintOptions and initialsFrom(first, last) (also accepts a full-name string), and [tint] now also accepts 'neutral' — additive, off by default, no code change.",
317
335
  "New override tokens --ds-sidenav-item-label-weight and --ds-modal-title-weight (previously baked into font: shorthands); defaults unchanged (--font-weight-semibold / --font-weight-bold) — additive, no code change.",
@@ -322,5 +340,6 @@
322
340
  "ds-sidenav-item gains an optional (activate) output — emits the click MouseEvent; preventDefault() intercepts navigation on an href item, but a routerLink item navigates regardless. Additive, no code change.",
323
341
  "BodyScrollLockService is now a public export — inject it to make a consumer's own full-screen overlay share the DS body-scroll lock (paired lock()/unlock()). Additive, no code change.",
324
342
  "ds-menu: a disabled ds-menu-item is now keyboard-focusable (aria-disabled, kept in the roving/arrow/type-ahead order) instead of being dropped from nav and rendered as a native disabled button; activation stays blocked and a [dsTooltip] on it now shows on focus. Behavior/a11y only, no code change — but an e2e/unit test asserting a disabled menu item is unfocusable/native-disabled must be updated."
325
- ]
343
+ ],
344
+ "deleteList": []
326
345
  }
@@ -4,9 +4,12 @@
4
4
  {
5
5
  "id": "surface-motion-partial-a-la-carte",
6
6
  "kind": "scss-api",
7
- "old": "@use 'styles/overlay-motion';",
8
- "new": "@use 'styles/surface-motion';\n@use 'styles/overlay-motion';",
9
- "note": "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 now names through --ds-<surface>-enter-keyframes. Consumers of the bundled entry (`@use 'styles/ds';`) need NO change — ds.scss forwards it. Only à-la-carte consumers that @use DS partials individually must add it, next to `styles/overlay-motion`: without it the keyframes do not exist and modal / drawer / bottom-sheet / toast / banner / alert / loading-overlay / overlay panels render with no entrance (silently — no error). Order does not matter; @use anywhere in the styles entry is enough. If a consumer's styles.scss has no `styles/overlay-motion` line, add `@use 'styles/surface-motion';` beside whatever DS partials it does @use.",
7
+ "old": "@use '@ids-group-ltd/ids-design-system/styles/overlay-motion';",
8
+ "new": "@use '@ids-group-ltd/ids-design-system/styles/surface-motion';\n@use '@ids-group-ltd/ids-design-system/styles/overlay-motion';",
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
+ "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.",
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`.",
10
13
  "searchHints": [
11
14
  "styles/overlay-motion",
12
15
  "styles/ds",
@@ -20,7 +23,10 @@
20
23
  "kind": "behavior",
21
24
  "old": "ds-table[sortKey]",
22
25
  "new": null,
23
- "note": "`ds-table` no longer nulls `sortKey` when the sort cycle reaches \"unsorted\" — the key keeps naming the column the user last touched and `sortDir === null` alone means unsorted. Fixes a header desync for hosts that map \"off\" back to their own default sort. ACTION: any host that treats a non-null `sortKey` as \"a sort is active\" must gate on `sortDir` instead — e.g. `if (sortKey())` becomes `if (sortDir())`, and a server query built as `orderBy: sortKey()` must skip the clause when `sortDir()` is null. Hosts that already read both, or that pass `sortingOrder: ['asc','desc']` (no unsorted state), need no change. The table's own rendering (icons, aria-sort) and its client-side sorting were already gated on `sortDir` and are unchanged. WHERE TO LOOK, because 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. mm-broker had three of them (2026-08-21), 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 its header showed no sort. Grep the consumer's `.ts` for the `detect` shapes, not their templates for `ds-table`.",
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
+ "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.",
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.",
24
30
  "searchHints": [
25
31
  "sortKey",
26
32
  "sortDir",
@@ -44,7 +50,10 @@
44
50
  "kind": "behavior",
45
51
  "old": "ds-input[reserveMessage]",
46
52
  "new": null,
47
- "note": "Every message-bearing field now defaults `reserveMessage` to FALSE (was true since 0.7.0). The resolution chain is unchanged - per-field input, then `DS_CONFIG.field.reserveMessage`, then the default - only the final fallback flipped. VISIBLE CONSEQUENCE: a field with no hint/error no longer holds a message line, so a form gets ~23px shorter per field and the controls below shift down the first time a hint or error appears. Affects all 14 fields: input, textarea, select, autocomplete, multi-select, checkbox, radio, radio-group, switch, slider, date-picker, time-picker, color-picker, otp-input. ACTION: a form that validates and must not reflow should turn it back on. App-wide in one line - `provideDsConfig({ field: { reserveMessage: true } })` - which is also how to restore 0.7.0 behaviour exactly; or per field with `[reserveMessage]=\"true\"`. Consumers that had written `[reserveMessage]=\"false\"` to opt OUT can delete those bindings, and any tighter sub-stack added to compensate for the reserved gap (e.g. a `var(--space-1)` wrapper) should be re-checked - with the row collapsed, a normal 16px stack is correct again.",
53
+ "action": "A form that validates and must not reflow turns it back on: `provideDsConfig({ field: { reserveMessage: true } })` app-wide, or `[reserveMessage]=\"true\"` per field. Bindings you wrote as `[reserveMessage]=\"false\"` to opt out can be deleted.",
54
+ "appliesWhen": "All fourteen message-bearing fields: input, textarea, select, autocomplete, multi-select, checkbox, radio, radio-group, switch, slider, date-picker, time-picker, color-picker, otp-input.",
55
+ "pitfall": "Two shifts, neither of which stops a build. A field with no hint gets about 23px shorter, so everything under it moves up — and then moves down again the first time a hint or error appears. And any tighter sub-stack you added to compensate for the old reserved gap now over-tightens: with the row collapsed, a normal 16px stack is correct again.",
56
+ "note": "Only the final fallback flipped, from true to false. The resolution chain is unchanged: per-field input, then `DS_CONFIG.field.reserveMessage`, then the default.",
48
57
  "searchHints": [
49
58
  "reserveMessage",
50
59
  "[reserveMessage]",
@@ -72,7 +81,9 @@
72
81
  "kind": "behavior",
73
82
  "old": "provideDsConfig",
74
83
  "new": null,
75
- "note": "A nested `provideDsConfig` (on a Route, component or directive) now MERGES with the config above it, section by section, instead of replacing it wholesale. Previously the provider used `useValue`, so a subtree that set one flag silently reset every unrelated section to its default. NO ACTION for the normal case - a single root-level `provideDsConfig` behaves exactly as before, and nested provision was neither documented nor safe to use. Only relevant if a consumer deliberately relied on a nested call to RESET a section back to defaults: that now needs the section spelled out explicitly, e.g. `provideDsConfig({ datePicker: { locale: 'en-US', dateFormat: undefined, firstDayOfWeek: 1 } })`. Enables the new `dsReserveMessages` directive to scope one field flag without disturbing the rest.",
84
+ "action": "None in the normal case. If you deliberately used a nested call to RESET a section to defaults, spell that section out: `provideDsConfig({ datePicker: { locale: 'en-US', dateFormat: undefined, firstDayOfWeek: 1 } })`.",
85
+ "appliesWhen": "A single root-level `provideDsConfig` behaves exactly as before. Nested provision was neither documented nor safe to use.",
86
+ "note": "A nested provider merges with the config above it section by section instead of replacing it wholesale — it used `useValue`, so a subtree setting one flag silently reset every unrelated section. The merge is what lets the new `dsReserveMessages` directive scope one field flag without disturbing the rest.",
76
87
  "searchHints": [
77
88
  "provideDsConfig",
78
89
  "DS_CONFIG",
@@ -89,7 +100,10 @@
89
100
  "kind": "behavior",
90
101
  "old": "extends TableComponent",
91
102
  "new": null,
92
- "note": "Several exported component classes CHANGED their member surface this range, which breaks a consumer that EXTENDS one (subclassing a DS component is unsupported - design-system.md section Components - but where it happens the names collide: TS4114 demands an `override` modifier, TS2415 fires on a redeclared private member, TS2416 where a signature differs). New members: all 14 message-bearing fields (ds-autocomplete, ds-checkbox, ds-color-picker, ds-date-picker, ds-input, ds-multi-select, ds-otp-input, ds-radio, ds-radio-group, ds-select, ds-slider, ds-switch, ds-textarea, ds-time-picker) gained `reserveMessageResolved`, and CheckboxComponent, SwitchComponent and RadioComponent also gained a protected `devMode`; InputComponent and TextareaComponent also gained `control` and `focus`; SearchComponent gained `focus`; TableComponent gained `rowId` and `rowKey`; PaginationComponent gained `showPageSize`; TimePickerComponent gained `label`, `required`, `optional`, `labelId`, `fullWidth`; DatePickerComponent gained `fullWidth`; AppLayoutComponent gained `railOpen`, `railLabel`, `compact`, `closeRail` plus the private `navigation`, `destroyRef`, `watchDesktopBreakpoint`. ONE REMOVAL: TooltipDirective (dsTooltip) dropped its protected `onOpen`, split into `onPointerEnter` / `onFocusIn` / `onFocusOut` plus a private `scheduleShow`, `describedElement`, `focusedTarget` - a subclass that overrode `onOpen` fails to compile because its `override` names a member the base no longer declares; move a mouse-path body to `onPointerEnter` and a keyboard-path body to `onFocusIn`. ACTION: rename the subclass's own member, or add `override` where the base's semantics genuinely match. Build after upgrading - the compiler enumerates every collision. Consumers who only use the <ds-...> elements need no change.",
103
+ "action": "Build right after upgrading — the compiler enumerates every collision. Per member: rename your own, or add `override` where the base semantics genuinely match.",
104
+ "appliesWhen": "Only a consumer that EXTENDS a DS component class. Subclassing is unsupported (design-system.md § Components); anyone using the `<ds-…>` elements needs nothing.",
105
+ "pitfall": "One change here is a REMOVAL, and it fails the other way round: TooltipDirective dropped its protected `onOpen`, split into `onPointerEnter` / `onFocusIn` / `onFocusOut`. A subclass that overrode `onOpen` fails because its `override` now names a member the base does not declare — move the mouse-path body to `onPointerEnter` and the keyboard-path body to `onFocusIn`.",
106
+ "note": "Additions: all fourteen message-bearing fields gained `reserveMessageResolved`; CheckboxComponent, SwitchComponent and RadioComponent a protected `devMode`; InputComponent and TextareaComponent `control` and `focus`; SearchComponent `focus`; TableComponent `rowId` and `rowKey`; PaginationComponent `showPageSize`; TimePickerComponent `label`, `required`, `optional`, `labelId`, `fullWidth`; DatePickerComponent `fullWidth`; AppLayoutComponent `railOpen`, `railLabel`, `compact`, `closeRail` and the private `navigation`, `destroyRef`, `watchDesktopBreakpoint`. TS4114 demands `override`, TS2415 fires on a redeclared private, TS2416 where a signature differs.",
93
107
  "searchHints": [
94
108
  "extends TableComponent",
95
109
  "extends InputComponent",
@@ -119,7 +133,9 @@
119
133
  "kind": "behavior",
120
134
  "old": "LayoutScrollService",
121
135
  "new": null,
122
- "note": "`ds-app-layout` no longer resets the content scroll on EVERY router NavigationEnd - only when the PATH changes (the part before `?` or `#`). A sort, page or filter change that rewrites just the query string or fragment now KEEPS the reader's scroll position. ACTION only if a screen relied on the old blanket reset: inject the still-public `LayoutScrollService` and call `scrollToTop()` from the handler that changes the filter, which is per-interaction and more precise than the old behaviour. No action for anyone who found the old reset disruptive.",
136
+ "action": "Only if a screen relied on the blanket reset: inject the still-public `LayoutScrollService` and call `scrollToTop()` from the handler that changes the filter.",
137
+ "appliesWhen": "Nothing to do for anyone who found the old reset disruptive — that is the case this change serves.",
138
+ "note": "The content scroll resets only when the PATH changes now, not on every NavigationEnd, so a sort, page or filter change that rewrites just the query string or fragment keeps the reader where they were.",
123
139
  "searchHints": [
124
140
  "LayoutScrollService",
125
141
  "scrollToTop",
@@ -136,25 +152,36 @@
136
152
  },
137
153
  {
138
154
  "id": "modal-title-flex-moved-to-heading",
139
- "kind": "class-rename",
140
- "old": "ds-modal-card .title",
141
- "new": ".heading",
142
- "note": "STYLING ONLY, and only for a consumer who styles the modal's internal DOM. The `[eyebrow]` slot wrapped `<h2 class=\"title\">` together with the eyebrow in a new `<div class=\"heading\">`, and the `flex: 1` that used to sit on the `<h2>` moved to that wrapper. A consumer rule that targeted `.modal-card .title` for the flex slot must retarget `.heading`; rules that target `.title` for typography or colour are unaffected. Scope strictly to selectors under ds-modal / ds-modal-card.",
155
+ "kind": "behavior",
156
+ "old": "ds-modal-card ::ng-deep .title { flex: … }",
157
+ "new": null,
158
+ "action": "Only if you set `flex`, `width` or `margin` on `.title` to control how the header row divides its space: move that declaration to `.heading`.",
159
+ "appliesWhen": "Only a consumer who styles the modal internal DOM. Everyone else is untouched.",
160
+ "pitfall": "`.title` is NOT renamed — it is still emitted, and a rule that only paints it (colour, font, letter-spacing) must NOT be re-pointed. Re-pointing it moves the paint onto a box that also wraps the eyebrow.",
161
+ "note": "The `[eyebrow]` slot wrapped `<h2 class=\"title\">` together with the eyebrow in a new `<div class=\"heading\">`, and the `flex: 1` that used to sit on `.title` moved to that wrapper.",
143
162
  "searchHints": [
144
- "ds-modal",
145
- "ds-modal-card",
146
- ".modal-card .title",
147
163
  ".title",
148
- "flex: 1"
164
+ ".heading",
165
+ "ds-modal-card",
166
+ "ds-modal"
149
167
  ],
150
- "surface": "style"
168
+ "surface": "style",
169
+ "verify": "Open a ds-modal-card that has both a title and an [eyebrow]: the title and eyebrow share one block that takes the free width, and the close button stays hard right. Any `.title` rule you kept still paints the heading text.",
170
+ "detect": [
171
+ "ds-modal-card ::ng-deep .title",
172
+ ".title { flex",
173
+ ".title{flex"
174
+ ]
151
175
  },
152
176
  {
153
177
  "id": "table-client-sort-blanks-last-and-numeric-collation",
154
178
  "kind": "behavior",
155
179
  "old": "ds-table[clientSort]",
156
180
  "new": null,
157
- "note": "`clientSort` changes how existing columns order in two ways, both applying with or without the new per-column `sortValue`. (1) BLANKS SINK: a cell reading as no-data - empty string, or one of the em dash, en dash, hyphen, 'n/a', 'never', 'none' matched case-insensitively - now sorts LAST in both ascending and descending order. Previously an empty string was just the smallest value, so it floated to the top on ascending. (2) NATURAL TEXT COLLATION: the text fallback now passes { numeric: true } to localeCompare, so 'item 9' precedes 'item 10' instead of following it. ACTION: none for most tables - both changes are what a reader expects. Only if a screen deliberately relied on blanks sorting first, or on the old pure-lexical order of strings containing digits, supply a per-column `sortValue` that maps the values the way that screen wants.",
181
+ "action": "None for most tables — both changes are what a reader expects. Only if a screen deliberately relied on blanks sorting first, or on the old pure-lexical order of strings containing digits, supply a per-column `sortValue` that maps the values the way that screen wants.",
182
+ "appliesWhen": "Both changes apply with or without the new per-column `sortValue`.",
183
+ "pitfall": "Two orderings move at once and neither announces itself. Blanks used to be the smallest value, so on ascending they floated to the TOP; they sink to the bottom in both directions now. And the text fallback passes `{ numeric: true }` to localeCompare, so `item 9` precedes `item 10` instead of following it — a list that looked deliberately ordered can come back reordered.",
184
+ "note": "A cell reads as no-data when it is an empty string or one of the em dash, en dash, hyphen, `n/a`, `never` or `none`, matched case-insensitively.",
158
185
  "searchHints": [
159
186
  "clientSort",
160
187
  "sortChange",
@@ -195,7 +222,7 @@
195
222
  "`ds-checkbox`, `ds-switch` and `ds-radio` log a dev-mode warning when a caption is projected (`<ds-checkbox>text</ds-checkbox>`) instead of passed via [label]; the text never rendered and failed silently. All three share the [label]-only contract. Dev only - the detection node is gated on isDevMode(), so production is unchanged. Projection itself is still unsupported. The directive doing the detection is internal (not exported from public-api).",
196
223
  "Known gap, not a regression: `--ds-overlay-enter-scale` is the one entrance token NOT forwarded onto a portaled overlay pane, so setting it per instance (`ds-select { --ds-overlay-enter-scale: 0.9 }`) has no effect on select / autocomplete / multi-select / date / time / colour picker / popover / tooltip / menu submenu panels. Scope it globally until it is forwarded; the other four (-enter-keyframes / -duration / -easing / -offset) do forward.",
197
224
  "Bugfix, no action: `dsTooltip` now puts `aria-describedby` on the element that actually took focus (recorded from the bubbling `focusin`) rather than unconditionally on its host, so a tooltip on a host that is not itself focusable — `ds-menu-item` carries `role=\"none\"` and holds the real button inside — finally reaches a screen reader. A pointer-only open still describes the host.",
198
- "Visual-only fixes: `ds-pagination` pins its internal rows-per-page select to `reserveMessage: false` (it inherited the app default and pushed the pager off the page buttons' baseline), and `ds-stat`'s card fills a stretched host so a KPI row with mixed captions paints equal-height tiles. Consumers can drop the global workarounds for both (`ds-pagination ds-field-message { display: none }` and `ds-stat { height: 100% }`)."
225
+ "Visual-only fixes: `ds-pagination` pins its internal rows-per-page select to `reserveMessage: false` (it inherited the app default and pushed the pager off the page buttons' baseline), and `ds-stat`'s card fills a stretched host so a KPI row with mixed captions paints equal-height tiles. Consumers can drop the global workarounds for both (`ds-pagination ds-field-message { display: none }` and `ds-stat { height: 100% }`). (delete list: pagination-inner-select-hidden)"
199
226
  ],
200
227
  "deleteList": [
201
228
  {
@@ -216,6 +243,17 @@
216
243
  ],
217
244
  "why": "A tighter sub-stack or a negative margin added to swallow the reserved message row is now over-tightening a form that no longer reserves it.",
218
245
  "replaceWith": "the normal 16px field stack"
246
+ },
247
+ {
248
+ "id": "pagination-inner-select-hidden",
249
+ "surface": "style",
250
+ "find": [
251
+ "ds-pagination",
252
+ "ds-field-message",
253
+ "display: none"
254
+ ],
255
+ "why": "A rule hiding the empty message row inside the pagination rows-per-page select. The component pins that select to its own compact shape now, so the row is gone at the source.",
256
+ "replaceWith": "nothing - delete the rule"
219
257
  }
220
258
  ]
221
259
  }