@ids-group-ltd/ids-design-system 0.10.0 → 0.10.2
This diff represents the content of publicly available package versions that have been released to one of the supported registries. The information contained in this diff is provided for informational purposes only and reflects changes between package versions as they appear in their respective public registries.
- package/CHANGELOG.md +622 -12
- package/components.md +68 -13
- package/fesm2022/ids-group-ltd-ids-design-system.mjs +748 -702
- package/fesm2022/ids-group-ltd-ids-design-system.mjs.map +1 -1
- package/migrations/0.10.0.json +420 -44
- package/migrations/0.10.1.json +223 -0
- package/migrations/0.10.2.json +482 -0
- package/migrations/0.2.0.json +32 -8
- package/migrations/0.3.0.json +19 -3
- package/migrations/0.4.0.json +50 -11
- package/migrations/0.5.0.json +93 -24
- package/migrations/0.5.1.json +106 -29
- package/migrations/0.6.0.json +2 -1
- package/migrations/0.6.2.json +33 -3
- package/migrations/0.6.3.json +19 -3
- package/migrations/0.7.0.json +77 -25
- package/migrations/0.7.1.json +84 -8
- package/migrations/0.8.0.json +46 -10
- package/migrations/0.9.0.json +284 -35
- package/migrations/AUTHORING.md +125 -12
- package/migrations/README.md +62 -5
- package/package.json +1 -1
- package/styles/_dropdown-overlay.scss +4 -3
- package/styles/_field-group-segment.scss +9 -0
- package/styles/_focus.scss +16 -0
- package/styles/_text-clip.scss +17 -0
- package/styles/_tokens.scss +0 -2
- package/themes/_semantic.scss +20 -3
- package/types/ids-group-ltd-ids-design-system.d.ts +296 -402
package/migrations/0.10.0.json
CHANGED
|
@@ -17,7 +17,14 @@
|
|
|
17
17
|
"chip-row",
|
|
18
18
|
"data-chip",
|
|
19
19
|
".field-trigger > ds-tag"
|
|
20
|
-
]
|
|
20
|
+
],
|
|
21
|
+
"surface": "style",
|
|
22
|
+
"detect": [
|
|
23
|
+
".autocomplete-trigger",
|
|
24
|
+
"ds-tag",
|
|
25
|
+
"::ng-deep"
|
|
26
|
+
],
|
|
27
|
+
"verify": "No consumer rule targets a `ds-tag` as a direct child of a multi-value trigger; a chip rule names the tag itself or the `.chip-row` wrapper."
|
|
21
28
|
},
|
|
22
29
|
{
|
|
23
30
|
"id": "exported-class-members-grew",
|
|
@@ -42,7 +49,14 @@
|
|
|
42
49
|
"partPicked",
|
|
43
50
|
"onPartPicked",
|
|
44
51
|
"pickedParts"
|
|
45
|
-
]
|
|
52
|
+
],
|
|
53
|
+
"surface": "typescript",
|
|
54
|
+
"detect": [
|
|
55
|
+
"extends AutocompleteComponent",
|
|
56
|
+
"extends ",
|
|
57
|
+
"override "
|
|
58
|
+
],
|
|
59
|
+
"verify": "A typecheck reports no TS4114 / TS2415 / TS2416 on any class extending a DS component."
|
|
46
60
|
},
|
|
47
61
|
{
|
|
48
62
|
"id": "auth-layout-brand-slot-drops-width-auto",
|
|
@@ -56,7 +70,10 @@
|
|
|
56
70
|
"ds-auth-layout",
|
|
57
71
|
"brand slot",
|
|
58
72
|
"logo width"
|
|
59
|
-
]
|
|
73
|
+
],
|
|
74
|
+
"surface": "style",
|
|
75
|
+
"restore": null,
|
|
76
|
+
"verify": "A logo projected into [brand] renders at the width the app sets - the slot no longer out-ranks it with `width: auto`."
|
|
60
77
|
},
|
|
61
78
|
{
|
|
62
79
|
"id": "tabs-url-param-slugs-the-label",
|
|
@@ -70,7 +87,17 @@
|
|
|
70
87
|
"?tab=",
|
|
71
88
|
"tabClosed",
|
|
72
89
|
"ds-tab"
|
|
73
|
-
]
|
|
90
|
+
],
|
|
91
|
+
"surface": [
|
|
92
|
+
"template",
|
|
93
|
+
"typescript"
|
|
94
|
+
],
|
|
95
|
+
"detect": [
|
|
96
|
+
"urlParam",
|
|
97
|
+
"queryParamMap",
|
|
98
|
+
"tab="
|
|
99
|
+
],
|
|
100
|
+
"verify": "Every tab in a urlParam strip declares a `value`, or the screen accepts that its link carries the label's slug; anything that READS the parameter reads the slug form."
|
|
74
101
|
},
|
|
75
102
|
{
|
|
76
103
|
"id": "modal-error-boolean-to-status",
|
|
@@ -85,7 +112,8 @@
|
|
|
85
112
|
"error=\"true\"",
|
|
86
113
|
"ModalComponent",
|
|
87
114
|
"dialogRole"
|
|
88
|
-
]
|
|
115
|
+
],
|
|
116
|
+
"surface": "template"
|
|
89
117
|
},
|
|
90
118
|
{
|
|
91
119
|
"id": "chips-cap-by-width-by-default",
|
|
@@ -98,7 +126,10 @@
|
|
|
98
126
|
"ds-multi-select",
|
|
99
127
|
"ds-autocomplete",
|
|
100
128
|
"chips"
|
|
101
|
-
]
|
|
129
|
+
],
|
|
130
|
+
"surface": "template",
|
|
131
|
+
"restore": "[maxVisibleChips]=\"null\"",
|
|
132
|
+
"verify": "Every multi-value trigger either accepts the measured \"fit\" default or says what it wants; no screen assumes the trigger grows a line per selection."
|
|
102
133
|
},
|
|
103
134
|
{
|
|
104
135
|
"id": "ultra-compact-compresses-container-pad",
|
|
@@ -112,7 +143,17 @@
|
|
|
112
143
|
"--ds-container-pad",
|
|
113
144
|
"--ds-card-pad",
|
|
114
145
|
"--ds-stat-pad"
|
|
115
|
-
]
|
|
146
|
+
],
|
|
147
|
+
"surface": [
|
|
148
|
+
"template",
|
|
149
|
+
"style"
|
|
150
|
+
],
|
|
151
|
+
"detect": [
|
|
152
|
+
"data-density=\"ultra-compact\"",
|
|
153
|
+
"ultra-compact"
|
|
154
|
+
],
|
|
155
|
+
"restore": "--ds-container-pad: var(--space-6)",
|
|
156
|
+
"verify": "Every container set to ultra-compact that holds a ds-card or ds-stat still has the inner padding the screen wants."
|
|
116
157
|
},
|
|
117
158
|
{
|
|
118
159
|
"id": "control-size-input-becomes-nullable",
|
|
@@ -126,7 +167,15 @@
|
|
|
126
167
|
"DsFieldGroupContext",
|
|
127
168
|
"ds-field-group",
|
|
128
169
|
"viewChild"
|
|
129
|
-
]
|
|
170
|
+
],
|
|
171
|
+
"surface": "typescript",
|
|
172
|
+
"detect": [
|
|
173
|
+
".size()",
|
|
174
|
+
"size()",
|
|
175
|
+
"sizeResolved"
|
|
176
|
+
],
|
|
177
|
+
"verify": "No host reads a DS control's `size()` expecting a value - an unbound size reads null, and the resolved one comes from `sizeResolved()`.",
|
|
178
|
+
"restore": "size=\"md\" on the element, or provideDsConfig({ control: { size: 'md' } }) app-wide"
|
|
130
179
|
},
|
|
131
180
|
{
|
|
132
181
|
"id": "table-sort-inputs-no-longer-a-model",
|
|
@@ -141,7 +190,15 @@
|
|
|
141
190
|
"sortDirChange",
|
|
142
191
|
"ds-table",
|
|
143
192
|
"sortChange"
|
|
144
|
-
]
|
|
193
|
+
],
|
|
194
|
+
"surface": "typescript",
|
|
195
|
+
"detect": [
|
|
196
|
+
"sortKey.set(",
|
|
197
|
+
"sortDir.set(",
|
|
198
|
+
"viewChild",
|
|
199
|
+
"TableComponent"
|
|
200
|
+
],
|
|
201
|
+
"verify": "Nothing calls `.set()` on a ds-table `sortKey` / `sortDir` through a viewChild; the host writes the input and listens to the matching output."
|
|
145
202
|
},
|
|
146
203
|
{
|
|
147
204
|
"id": "outline-button-fill-becomes-transparent",
|
|
@@ -155,7 +212,10 @@
|
|
|
155
212
|
"--ds-button-bg-color",
|
|
156
213
|
"ds-split-button",
|
|
157
214
|
"--ds-split-button-outline-bg-color"
|
|
158
|
-
]
|
|
215
|
+
],
|
|
216
|
+
"surface": "style",
|
|
217
|
+
"restore": "--ds-button-bg-color: var(--surface-default) (and the icon-button / split-button equivalents)",
|
|
218
|
+
"verify": "Every outlined control on a coloured ground either pins its own fill or is meant to show that ground through."
|
|
159
219
|
},
|
|
160
220
|
{
|
|
161
221
|
"id": "input-floating-removed",
|
|
@@ -174,7 +234,9 @@
|
|
|
174
234
|
"--field-floating-label-lh",
|
|
175
235
|
"--field-floating-label-top",
|
|
176
236
|
"--field-floating-pad-t"
|
|
177
|
-
]
|
|
237
|
+
],
|
|
238
|
+
"surface": "template",
|
|
239
|
+
"verify": "No ds-input carries a `floating` attribute or binding."
|
|
178
240
|
},
|
|
179
241
|
{
|
|
180
242
|
"id": "field-invalid-class-to-data-field-state",
|
|
@@ -190,7 +252,8 @@
|
|
|
190
252
|
"invalid]",
|
|
191
253
|
"data-field-state",
|
|
192
254
|
"ds-slider"
|
|
193
|
-
]
|
|
255
|
+
],
|
|
256
|
+
"surface": "style"
|
|
194
257
|
},
|
|
195
258
|
{
|
|
196
259
|
"id": "max-visible-chips-number-is-a-ceiling",
|
|
@@ -203,7 +266,9 @@
|
|
|
203
266
|
"ds-autocomplete",
|
|
204
267
|
"ds-multi-select",
|
|
205
268
|
"chips"
|
|
206
|
-
]
|
|
269
|
+
],
|
|
270
|
+
"surface": "template",
|
|
271
|
+
"verify": "No screen depends on exactly N chips being visible - a number is a ceiling that the trigger width can lower."
|
|
207
272
|
},
|
|
208
273
|
{
|
|
209
274
|
"id": "max-visible-chips-zero-inverted",
|
|
@@ -218,7 +283,16 @@
|
|
|
218
283
|
"ds-autocomplete",
|
|
219
284
|
"ds-multi-select",
|
|
220
285
|
"?? 0"
|
|
221
|
-
]
|
|
286
|
+
],
|
|
287
|
+
"surface": [
|
|
288
|
+
"template",
|
|
289
|
+
"typescript"
|
|
290
|
+
],
|
|
291
|
+
"detect": [
|
|
292
|
+
"[maxVisibleChips]=\"0\"",
|
|
293
|
+
"maxVisibleChips"
|
|
294
|
+
],
|
|
295
|
+
"verify": "No binding passes 0 to maxVisibleChips meaning \"show everything\" - 0 now hides every chip behind the +N marker."
|
|
222
296
|
},
|
|
223
297
|
{
|
|
224
298
|
"id": "nullable-boolean-inputs-treat-null-as-unset",
|
|
@@ -233,7 +307,19 @@
|
|
|
233
307
|
"[withDot]",
|
|
234
308
|
"?.",
|
|
235
309
|
"| async"
|
|
236
|
-
]
|
|
310
|
+
],
|
|
311
|
+
"surface": [
|
|
312
|
+
"template",
|
|
313
|
+
"typescript"
|
|
314
|
+
],
|
|
315
|
+
"detect": [
|
|
316
|
+
"[bordered]",
|
|
317
|
+
"[stickyScrollbar]",
|
|
318
|
+
"[withDot]",
|
|
319
|
+
"[dividers]",
|
|
320
|
+
"?? false"
|
|
321
|
+
],
|
|
322
|
+
"verify": "Each of those five bindings passes a real boolean, or is absent so the config decides - no expression hands it null expecting `false`."
|
|
237
323
|
},
|
|
238
324
|
{
|
|
239
325
|
"id": "bottom-sheet-stops-swallowing-inside-clicks",
|
|
@@ -247,7 +333,13 @@
|
|
|
247
333
|
"stopPropagation",
|
|
248
334
|
"BottomSheetComponent",
|
|
249
335
|
"stop("
|
|
250
|
-
]
|
|
336
|
+
],
|
|
337
|
+
"surface": "typescript",
|
|
338
|
+
"detect": [
|
|
339
|
+
"stopPropagation",
|
|
340
|
+
"ds-bottom-sheet"
|
|
341
|
+
],
|
|
342
|
+
"verify": "Nothing relied on the sheet swallowing an inside click: a click inside now reaches document-level listeners."
|
|
251
343
|
},
|
|
252
344
|
{
|
|
253
345
|
"id": "error-string-alone-now-paints-the-control",
|
|
@@ -263,21 +355,36 @@
|
|
|
263
355
|
"ds-date-picker",
|
|
264
356
|
"warning=\"",
|
|
265
357
|
"[success]"
|
|
266
|
-
]
|
|
358
|
+
],
|
|
359
|
+
"surface": "template",
|
|
360
|
+
"detect": [
|
|
361
|
+
"error=",
|
|
362
|
+
"[error]"
|
|
363
|
+
],
|
|
364
|
+
"verify": "Every `error` string on a field is a real error - none is used as a neutral message, because it now paints the control and sets aria-invalid."
|
|
267
365
|
},
|
|
268
366
|
{
|
|
269
367
|
"id": "universal-focus-ring-base-rule",
|
|
270
368
|
"kind": "behavior",
|
|
271
369
|
"old": ":focus-visible",
|
|
272
370
|
"new": null,
|
|
273
|
-
"note": "A single zero-specificity base rule - :where(:focus-visible) { outline: none; box-shadow: var(--ds-control-focus-shadow) } - now gives the DS focus ring to ANY focusable element that does not style focus itself, including an app's own bare <button>, a link in projected content, and the close buttons inside ds-alert / ds-banner / ds-drawer. Before, those fell through to the browser default. ACTION only if you deliberately relied on an element having NO focus indicator: give it box-shadow: none explicitly. Note the rule also sets outline: none, so an element that was relying on the BROWSER's outline loses it - declare your own outline if that is what you wanted. Written with :where() so every component rule and every app rule still out-ranks it, and the data-focus switch is unaffected.",
|
|
371
|
+
"note": "A single zero-specificity base rule - :where(:focus-visible) { outline: none; box-shadow: var(--ds-control-focus-shadow) } - now gives the DS focus ring to ANY focusable element that does not style focus itself, including an app's own bare <button>, a link in projected content, and the close buttons inside ds-alert / ds-banner / ds-drawer. Before, those fell through to the browser default. ACTION only if you deliberately relied on an element having NO focus indicator: give it box-shadow: none explicitly. Note the rule also sets outline: none, so an element that was relying on the BROWSER's outline loses it - declare your own outline if that is what you wanted. Written with :where() so every component rule and every app rule still out-ranks it, and the data-focus switch is unaffected. THE CASE THAT ACTUALLY BITES, added retroactively 2026-08-21 after a consumer hit it fourteen times and neither the build nor a grep saw it: an app rule that styles :focus-visible with an OUTLINE ONLY. It keeps winning on outline, but it says nothing about box-shadow, so the base rule still supplies one and the element renders BOTH - a second ring in the app's colour around the DS ring. The app rule looks untouched because it is. FIND IT by grepping your styles for ':focus-visible' and reading each rule's declarations: a rule that sets outline (or outline-color / outline-offset) and no box-shadow is a hit. ACTION: add `box-shadow: none` to that rule, or - better, and what this release is for - delete the rule and retint the DS ring through --ds-control-focus-shadow.",
|
|
274
372
|
"searchHints": [
|
|
275
373
|
":focus-visible",
|
|
276
374
|
":focus",
|
|
277
375
|
"outline: none",
|
|
278
376
|
"box-shadow: none",
|
|
279
|
-
"--ds-control-focus-shadow"
|
|
280
|
-
|
|
377
|
+
"--ds-control-focus-shadow",
|
|
378
|
+
"outline-color",
|
|
379
|
+
"outline-offset"
|
|
380
|
+
],
|
|
381
|
+
"surface": "style",
|
|
382
|
+
"detect": [
|
|
383
|
+
":focus-visible",
|
|
384
|
+
"outline:",
|
|
385
|
+
"box-shadow"
|
|
386
|
+
],
|
|
387
|
+
"verify": "The app's own focusable elements either take the DS ring or style focus themselves, and no `overflow: hidden` ancestor leaves one with no visible indicator."
|
|
281
388
|
},
|
|
282
389
|
{
|
|
283
390
|
"id": "backdrop-dismissal-needs-press-and-release",
|
|
@@ -293,7 +400,14 @@
|
|
|
293
400
|
"pointerup",
|
|
294
401
|
"ds-modal",
|
|
295
402
|
"ds-bottom-sheet"
|
|
296
|
-
]
|
|
403
|
+
],
|
|
404
|
+
"surface": "typescript",
|
|
405
|
+
"detect": [
|
|
406
|
+
"dispatchEvent",
|
|
407
|
+
"backdrop",
|
|
408
|
+
".click("
|
|
409
|
+
],
|
|
410
|
+
"verify": "No test dismisses a modal or sheet with a click synthesised without a matching press on the backdrop."
|
|
297
411
|
},
|
|
298
412
|
{
|
|
299
413
|
"id": "modal-card-dialog-role-default-becomes-null",
|
|
@@ -306,7 +420,17 @@
|
|
|
306
420
|
"ds-modal-card",
|
|
307
421
|
"alertdialog",
|
|
308
422
|
"role=\"dialog\""
|
|
309
|
-
]
|
|
423
|
+
],
|
|
424
|
+
"surface": [
|
|
425
|
+
"template",
|
|
426
|
+
"typescript"
|
|
427
|
+
],
|
|
428
|
+
"detect": [
|
|
429
|
+
"dialogRole",
|
|
430
|
+
"alertdialog"
|
|
431
|
+
],
|
|
432
|
+
"verify": "Any code reading `dialogRole()` treats null as \"unset\", which still renders role=\"dialog\".",
|
|
433
|
+
"restore": "dialogRole=\"dialog\", stated explicitly"
|
|
310
434
|
},
|
|
311
435
|
{
|
|
312
436
|
"id": "avatar-tint-chroma-to-saturation",
|
|
@@ -322,7 +446,14 @@
|
|
|
322
446
|
"avoidHues",
|
|
323
447
|
"lightness",
|
|
324
448
|
"foreground"
|
|
325
|
-
]
|
|
449
|
+
],
|
|
450
|
+
"surface": "typescript",
|
|
451
|
+
"detect": [
|
|
452
|
+
"avatarTint",
|
|
453
|
+
"chroma"
|
|
454
|
+
],
|
|
455
|
+
"verify": "No avatarTint call passes `chroma` - a leftover one is silently ignored.",
|
|
456
|
+
"restore": null
|
|
326
457
|
},
|
|
327
458
|
{
|
|
328
459
|
"id": "radio-group-stops-handling-enter",
|
|
@@ -336,53 +467,87 @@
|
|
|
336
467
|
"'Enter'",
|
|
337
468
|
"radio",
|
|
338
469
|
"submit"
|
|
339
|
-
]
|
|
470
|
+
],
|
|
471
|
+
"surface": "typescript",
|
|
472
|
+
"detect": [
|
|
473
|
+
"'Enter'",
|
|
474
|
+
"keydown.enter",
|
|
475
|
+
"ds-radio-group"
|
|
476
|
+
],
|
|
477
|
+
"verify": "No screen depended on Enter selecting the focused radio; inside a form Enter now reaches the submit."
|
|
478
|
+
},
|
|
479
|
+
{
|
|
480
|
+
"id": "table-column-width-type-widened-for-readers",
|
|
481
|
+
"kind": "behavior",
|
|
482
|
+
"old": "TableColumn",
|
|
483
|
+
"new": null,
|
|
484
|
+
"note": "TYPE WIDENING, breaking for READERS of the field and invisible to writers: TableColumn.width went `width?: number` to `width?: number | 'content'`. Assigning a value INTO the column definition compiles exactly as before, but code that reads col.width back into a number position stops compiling: `sum += col.width` (TS2365), `fixed[col.key] = col.width` where the target is number (TS2322), a helper parameter typed `width: number`. ACTION: handle the new union member at the read site - `typeof col.width === 'number'` before arithmetic - or widen your own type to `number | 'content'`. Writers who never read the field back need no change; the capability itself is additive and described in this version's informational list. Added retroactively 2026-08-20 after a consumer's build was the first finder.",
|
|
485
|
+
"searchHints": [
|
|
486
|
+
"TableColumn",
|
|
487
|
+
".width"
|
|
488
|
+
],
|
|
489
|
+
"surface": "typescript",
|
|
490
|
+
"detect": [
|
|
491
|
+
"col.width",
|
|
492
|
+
".width",
|
|
493
|
+
"TableColumn"
|
|
494
|
+
],
|
|
495
|
+
"verify": "Every place that reads TableColumn.width back into a number handles 'content'."
|
|
496
|
+
},
|
|
497
|
+
{
|
|
498
|
+
"id": "input-signal-types-widened-for-explicit-typings",
|
|
499
|
+
"kind": "behavior",
|
|
500
|
+
"old": "InputSignal",
|
|
501
|
+
"new": null,
|
|
502
|
+
"note": "TYPE-LEVEL counterpart of control-size-input-becomes-nullable and nullable-boolean-inputs-treat-null-as-unset: those two carry the VALUE semantics (what null means, what reads back); this entry carries the declarations TYPED against the old signal types, which stop compiling even where the values are compatible, because the equal type-parameter position of InputSignal / InputSignalWithTransform is invariant - TS2416 on a subclass override, TS2322 on an assignment to an explicitly typed variable, viewChild target or helper parameter. WIDENED THIS RELEASE (per npm run class-surface v0.9.1..v0.10.0): size DsSize -> DsSize | null on ds-button, ds-icon-button, ds-input, ds-textarea, ds-select, ds-autocomplete, ds-search, ds-date-picker, ds-time-picker, ds-number-stepper, ds-checkbox, ds-radio, ds-switch, ds-field-group; ds-icon size number -> number | null; bordered and stickyScrollbar on ds-table, withDot on ds-badge, dividers on ds-modal and ds-modal-card: boolean -> boolean | null (transform now nullable); ds-table loading false | 'skeleton' | 'overlay' -> boolean | 'skeleton' | 'overlay'; ds-card elevation CardElevation -> CardElevation | null; ds-modal-card dialogRole 'dialog' | 'alertdialog' -> nullable; brand / logoLetter / tagline on ds-auth-layout and ds-sidenav string -> string | null; maxVisibleChips on ds-autocomplete and ds-multi-select number | null -> number | 'fit' | null. ACTION: retype the declaration to the widened union, or drop the explicit annotation and let inference carry it; a subclass override is the unsupported case - rename the member or retype it to match. Templates and plain bindings are unaffected. Added retroactively 2026-08-20.",
|
|
503
|
+
"searchHints": [
|
|
504
|
+
"InputSignal",
|
|
505
|
+
"InputSignalWithTransform",
|
|
506
|
+
"extends "
|
|
507
|
+
],
|
|
508
|
+
"surface": "typescript",
|
|
509
|
+
"detect": [
|
|
510
|
+
"InputSignal<",
|
|
511
|
+
"InputSignalWithTransform",
|
|
512
|
+
"viewChild"
|
|
513
|
+
],
|
|
514
|
+
"verify": "No explicit declaration types a DS input signal with the old non-nullable parameters."
|
|
340
515
|
}
|
|
341
516
|
],
|
|
342
517
|
"informational": [
|
|
343
518
|
"ds-autocomplete and ds-multi-select cap their chips by MEASURED width: one line holds as many as the trigger is wide and the rest collapse into '+N more', re-split whenever the trigger resizes. This is now the DEFAULT (see the chips-cap-by-width-by-default item) - [maxVisibleChips]=\"null\" restores \"show everything\", and a NUMBER adds an upper bound on top of the same measuring rather than pinning an exact count. Choose by what has to stay predictable: \"fit\" lets the count follow the width, a number caps it as well, and null is the only mode that shows every chip and the only one that never measures.",
|
|
344
519
|
"The measurement behind maxVisibleChips=\"fit\" reads the TRIGGER's width, never the chip row's own - a row cannot measure a box whose size the cut changes. Widths are cached per selection and a geometry guard skips re-measuring when neither width nor count moved, so a page of pickers measures once, not once per chip. [maxVisibleChips]=\"null\" opts out of measuring entirely.",
|
|
345
|
-
"DELETE-LIST: if you wrote a ResizeObserver, a container query or a hand-tuned per-breakpoint maxVisibleChips number to keep a chip trigger on one line -> maxVisibleChips=\"fit\" replaces it, and it re-splits on any width change rather than at the breakpoints you listed.",
|
|
346
|
-
"DELETE-LIST: if you capped a chip trigger's height with max-height plus overflow:hidden to stop it growing a line per selection -> that clips a chip mid-glyph and hides the count; maxVisibleChips (a number, or \"fit\") drops whole chips and reports how many are hidden.",
|
|
347
520
|
"ds-sidenav's brand row fixes, none of which need action: an astral first character (emoji, rarer CJK) no longer paints as tofu in the letter-mark; the mark is aria-hidden, so a screen reader reads the wordmark once instead of announcing the glyph then the name; and a logoLetter set WITHOUT a brand string now renders its tile at all, where an outer gate used to drop the whole lockup.",
|
|
348
|
-
"DELETE-LIST: if you constrained a logo projected into ds-sidenav's [brand] slot with your own max-height (or a wrapper sized to hold it) -> --ds-sidenav-brand-max-height now does it, defaulting to none so nothing changes until you set it.",
|
|
349
521
|
"env(safe-area-inset-*) reads 0 unless YOUR index.html sets viewport-fit=cover in its viewport meta — a notched device alone is not enough, and this library cannot set it for you. ds-auth-layout pads by all four insets and ds-bottom-sheet by the bottom one, so both are plain-padded until you opt in; the docs site now sets it and both component pages state it. ds-bottom-sheet's env() also gained the `, 0px` fallback its siblings had: an unknown env() variable invalidates the entire declaration, which would have taken that sheet's horizontal padding with it.",
|
|
350
522
|
"The ds-select and ds-autocomplete panels now resolve --ds-dropdown-panel-radius, defaulting to the --ds-radius-panel role so nothing moves until you set it. TWO panels, not three: ds-multi-select's panel hardcodes border-radius: var(--radius-md) on its own .panel element, which is not the .dropdown-panel the shared rule targets, so neither this token nor --ds-radius-panel reaches it - it stays at 8px whatever you set, and that is a gap rather than a decision. This is the lever 0.9.0 notes promised as --ds-select-panel-radius, which never existed - that note is corrected in migrations/0.9.0.json. Deliberately panel-level rather than per-component: retuning ONE picker is not a thing the library encourages, and --ds-radius-panel moves modal, popover and date-picker with it. Scope it with a selector - ds-select { --ds-dropdown-panel-radius: 8px } - and only that panel moves, since the token is forwarded onto the portaled pane.",
|
|
351
|
-
"DELETE-LIST: if you wrote a global rule against .ds-dropdown-panel or .cdk-overlay-pane to change a dropdown corner -> --ds-dropdown-panel-radius does it, and scopes to one picker when written under a component selector.",
|
|
352
523
|
"A single-select ds-autocomplete no longer keeps the text typed to filter. Since 0.9.0 that text was also INVISIBLE - the filter input collapses to zero width once a chosen label is on show - while it still narrowed the list, so reopening a settled picker offered one option of four with nothing on screen to explain it. Cleared now whenever the panel closes over a displayed label, which covers both picking and dismissing after typing over a settled value. Multi-select is unchanged on purpose: its input never collapses, so the text stays visible and useful for the next pick. No action - query was component-private and could not be reset from an app.",
|
|
353
|
-
"DELETE-LIST: if you queried a ds-autocomplete inner <input> and dispatched a synthetic input event to clear leftover filter text after a pick -> the component clears it itself now, and clear() has been public since 0.9.0 for emptying value and text together.",
|
|
354
524
|
"The global .link class now resets a <button>: appearance, padding, border, background, font-family, font-size, line-height and text-align. It was written for anchors and touched none of them, yet ds-button warns variant=\"text\" off in favour of .link and an action that is not navigation has to be a button - so a button.link rendered at 13.3px inside 14px text with 1px 6px of padding and an outset border. font-weight is untouched so .quiet/.standalone still decide it, and display stays inline-block. Scoped with :where(), so the reset sits at .link specificity and a consumer rule still wins on source order.",
|
|
355
|
-
"DELETE-LIST: if you have a local .link-button class, or a padding/border/background/font reset on button.link in your overrides -> .link ships it now. mm-broker carried exactly those four lines after replacing three near-duplicate local classes with \"link sm standalone\".",
|
|
356
525
|
"ds-stat gained --ds-stat-value-white-space and --ds-stat-value-font-size, both defaulting to what the tile already rendered (nowrap, and h2/h4/h1 by size), so no existing tile moves. They exist because a value that is a PHRASE - a date range, a status - spilled straight past the tile edge under the nowrap that suits a number - the card sets no overflow, so it is not clipped, it escapes. The size hook now applies at every size input: the sm and lg variants move this token instead of restating font-size on .value, where they out-ranked any override and made such a hook work at md only.",
|
|
357
|
-
"DELETE-LIST: if you projected into ds-stat [dsStatValue] only to set white-space: normal or a smaller font-size on a text value -> the two hooks do it on the ordinary value input, and the tile keeps its geometry either way. Keep the slot for a value that is genuinely another component, like a badge.",
|
|
358
526
|
"ds-search takes [debounce] (milliseconds, default 0). At 0 it writes value on every keystroke exactly as before, so nothing changes until you ask. THREE things deliberately skip the timer, which is what a wrapped debounceTime usually gets wrong: emptying the field, the Clear button, and Enter - the last flushing a keystroke still in flight so `submitted` carries what the reader can see. Emptying also cancels a pending keystroke, so a fast type-then-clear cannot land the stale query afterwards. What the input SHOWS is never delayed at any setting, and a host writing value mid-typing wins and cancels the timer.",
|
|
359
|
-
"DELETE-LIST: if you wrapped ds-search to add a debounce - typically 200ms on typing with an immediate path when the field empties -> [debounce] does both, plus the Enter flush. mm-broker carried exactly that wrapper for exactly those two behaviours.",
|
|
360
527
|
"ds-filter-bar no longer clips the focus ring of its first and last inline filter. The measured row was overflow: hidden with each slot sized to exactly its declared width, so the row box started flush with the first control while the ring is an OUTSET shadow (3px on fields, 4px on controls) - interior filters were fine in the 12px gap, the outer two were cut off as you tabbed onto them. Now overflow: clip with a 4px clip margin; clip still forbids scrolling, so the width the collapse arithmetic reads is unchanged. Nothing to do, and it was not fixable from an app: the row is internal and padding it from outside would have changed that measured width.",
|
|
361
|
-
"ds-filter-bar takes triggerSize (sm|md|lg, default md) for its own \"+N\" trigger. The bar cannot infer it: dsFilterItem carries a WIDTH and the filters are arbitrary projected controls whose size it never sees, so a row of sm filters got an md trigger standing 8px taller under align-items: flex-end.
|
|
528
|
+
"ds-filter-bar takes triggerSize (sm|md|lg, default md) for its own \"+N\" trigger. The bar cannot infer it: dsFilterItem carries a WIDTH and the filters are arbitrary projected controls whose size it never sees, so a row of sm filters got an md trigger standing 8px taller under align-items: flex-end.",
|
|
362
529
|
"If you must hold two trailing controls in ONE component, the Filter bar page now shows the three declarations its :host owes (display: flex; align-items: flex-end; gap: var(--ds-filter-bar-gap, var(--space-3))) - the bar's own trailing rule, with the gap read from the existing public token so the copy cannot drift. The usual REASON for pairing them is also gone: a bar-level Clear no longer has to share a component with the search to cancel an armed debounce, because ds-search cancels its own pending keystroke when the host writes value.",
|
|
363
530
|
"DS_CONFIG gained a modal section: provideDsConfig({ modal: { dividers: false } }) sets the default for ds-modal and ds-modal-card app-wide, or on a route or subtree for the ELEMENTS, with an explicit [dividers] still winning. ONE LIMIT: ModalService is providedIn root and builds the confirm injector from the root, so only a ROOT-level provideDsConfig reaches a ModalService confirm - a route- or component-scoped one does not. It reaches where an attribute cannot - a ModalService confirm renders a ds-modal-card with no ds-modal ancestor to bind - which is why a per-element input was not enough. Internally [dividers] is now boolean | null so \"unset\" stays distinguishable from an explicit false; existing bindings are unaffected.",
|
|
364
|
-
"
|
|
365
|
-
"ds-tabs takes rememberLastTab (off by default), which reopens the tab a screen was last left on. Stored per path in sessionStorage under ds-tabs:{path}:{param}; inert without urlParam, which supplies the names because a remembered INDEX would repoint the moment a tab is inserted. A link always wins - the query parameter is read first and memory only fills the gap the first tab deliberately leaves. Every storage access is guarded, so Safari private mode simply means the strip stops remembering. DELETE-LIST: a helper that kept the last tab per path in sessionStorage can go.",
|
|
531
|
+
"ds-tabs takes rememberLastTab (off by default), which reopens the tab a screen was last left on. Stored per path in sessionStorage under ds-tabs:{path}:{param}; inert without urlParam, which supplies the names because a remembered INDEX would repoint the moment a tab is inserted. A link always wins - the query parameter is read first and memory only fills the gap the first tab deliberately leaves. Every storage access is guarded, so Safari private mode simply means the strip stops remembering.",
|
|
366
532
|
"DS_CONFIG gained a brand section: provideDsConfig({ brand: { name, logoLetter, tagline } }) answers ds-sidenav and ds-auth-layout together, since both take the same three and an app answers them identically on every screen. Each field resolves independently - an element input beats the config per FIELD, so overriding the name does not mean restating the letter, and brand=\"\" drops the wordmark while a logoLetter in the config still paints its tile (clear both for no brand row). The two-tone wordmark is deliberately NOT in the config: [dsBrandName] stays the accent's home, because a config string would have to be split apart to find the accent, and the projection wins over both. Shape: brand, logoLetter and tagline are now string | null with a null default so \"unset\" is distinguishable from an explicit empty; the input names did not change and template bindings are unaffected.",
|
|
367
|
-
"DELETE-LIST: if you wrote an adapter component that injects a brand object and fans it out into brand/logoLetter/tagline bindings on each auth screen -> provideDsConfig({ brand: … }) does it, and the accent stays a [dsBrandName] projection instead of a brandAccent string plus an indexOf split.",
|
|
368
533
|
"ds-avatar takes a `name`, which replaces the two bindings a caller used to wire by hand: it derives the initials AND seeds the tint. The tint hashes the NAME rather than the initials - two letters collide wholesale, so Alice Brown and Adam Bell would otherwise share a colour (measured: same \"AB\", hues 198 and 356). An explicit `initials` still wins, and `seed` still overrides the hash input when identity is an id or an email rather than the display name.",
|
|
369
|
-
"The rule turning a name into initials is REPLACEABLE rather than configurable by mode: [initialsRule] on one avatar or table, provideDsConfig({ avatar: { initials } }) for the app. The built-in stays initialsFrom - first two words - and is documented as a Latin-script guess, because reading a name is a cultural convention rather than a UI decision: a Spanish reader wants MG from \"Maria Jose Garcia Lopez\", an insurer wants BC from \"Blue Cross Blue Shield\". A library that shipped person/organisation modes would be claiming to know both, and would be wrong in ways it cannot see.
|
|
534
|
+
"The rule turning a name into initials is REPLACEABLE rather than configurable by mode: [initialsRule] on one avatar or table, provideDsConfig({ avatar: { initials } }) for the app. The built-in stays initialsFrom - first two words - and is documented as a Latin-script guess, because reading a name is a cultural convention rather than a UI decision: a Spanish reader wants MG from \"Maria Jose Garcia Lopez\", an insurer wants BC from \"Blue Cross Blue Shield\". A library that shipped person/organisation modes would be claiming to know both, and would be wrong in ways it cannot see.",
|
|
370
535
|
"ds-multi-select and ds-autocomplete render an option's `icon` before its label at 16px, which previously only ds-select did. The three option types now extend one exported DsOption<T> - they were three near-identical interfaces, which is why the icon field existed on one picker for a release - and each keeps its own exported name, so no import changes. Nothing to do: options without an icon render as before. Only ds-select repeats the icon in its TRIGGER, because its trigger is a button showing one label; the autocomplete trigger is a text input whose leading slot belongs to [dsAutocompletePrefix], and multi-select chips stay text-only so the label keeps the width.",
|
|
371
|
-
"provideDsConfig gained five sections, so an app can state a whole-app opinion once instead of on every element: control.size (button, icon-button, input, textarea, select, autocomplete, search, date/time picker, number stepper, checkbox, radio, switch, field-group), card.elevation, card.padding, table.stickyScrollbar, table.bordered, icon.size and badge.withDot. Precedence is input -> config -> built-in, and NO built-in default moved: an app that provides nothing renders exactly as it did.
|
|
536
|
+
"provideDsConfig gained five sections, so an app can state a whole-app opinion once instead of on every element: control.size (button, icon-button, input, textarea, select, autocomplete, search, date/time picker, number stepper, checkbox, radio, switch, field-group), card.elevation, card.padding, table.stickyScrollbar, table.bordered, icon.size and badge.withDot. Precedence is input -> config -> built-in, and NO built-in default moved: an app that provides nothing renders exactly as it did.",
|
|
372
537
|
"DS_CONFIG.control.size is NOT the same axis as [data-density]. The density tier rewrites hit targets and padding in CSS for a route subtree; control.size picks which of the three declared sizes (sm/md/lg) a control renders at. An app can set both, and they compose.",
|
|
373
538
|
"MEASURED IN A CONSUMER, worth checking on your own side: 46 of its ds-icon elements bind [size]=\"16\", which is already the ds-icon default - dead bindings, not a gap. Config or no config, those can go.",
|
|
374
539
|
"ds-modal and ds-bottom-sheet no longer dismiss when the mouse is RELEASED on the backdrop after a press that started inside the dialog (selecting text and letting go past the edge, or overshooting a slider). Their backdrop wraps the dialog, so the browser fires click at the nearest common ancestor - the backdrop itself - which the target===currentTarget guard could not tell apart. Dismissal now requires the press AND the release to land on the backdrop. Nothing to do on adoption. ONE EXCEPTION: a test that dismisses a dialog with backdropElement.click() must now dispatch pointerdown + pointerup on the backdrop; a real mouse or touch always sends both. ds-drawer and the ModalService confirm were never affected - their scrim is a sibling of the panel - and are unchanged.",
|
|
375
540
|
"ds-table gained one projection slot, [toolbar], for controls that act on THAT table (a search box, a status filter, a refresh) — the row the export button already lived in, which until now existed only while exportButton was on. Project several controls and the row lays them out (flex, wrap, 8px gap); project a single element of your own and it takes the full row width, so your own layout is the only one in play. Visually additive: the row COLLAPSES when nothing filled it and exportButton is off, so a table that uses neither is pixel-identical. It is not DOM-identical - <div class=\"table-toolbar\"><div class=\"toolbar-slot\"> is now rendered unconditionally and hidden with display:none, so a ds-table > :first-child selector or a DOM snapshot sees it. Page-level filters still belong in a ds-filter-bar above the table.",
|
|
376
|
-
"ds-table now exposes runExport(), exporting() and exportStatus() publicly, so an Export button placed anywhere (page header, filter bar, the new toolbar slot) runs the same path as the built-in one: the exportFetcher call, the download, the in-flight state and the live-region announcement.
|
|
541
|
+
"ds-table now exposes runExport(), exporting() and exportStatus() publicly, so an Export button placed anywhere (page header, filter bar, the new toolbar slot) runs the same path as the built-in one: the exportFetcher call, the download, the in-flight state and the live-region announcement.",
|
|
377
542
|
"ds-table no longer renders its empty row while loading is anything but false. Previously only loading=\"skeleton\" suppressed it, so an overlay reload with zero rows painted the empty state under the spinner. Nothing to do on adoption, and you can delete the @if(!loading) guard around your own empty template — worth checking whether you have one at all: of one consumer 14 overlay-loading tables, 9 shipped \"no rows\" copy during a load.",
|
|
378
543
|
"ds-table no longer loses its sort indicator when a host answers a cleared sort with its own default. Angular writes an input only when the bound expression changed (it diffs against the last value it wrote, which an internal .set() never updates), so whichever half of the host default equalled the last bound value was skipped: a host defaulting to desc had its desc dropped and the header marked nothing over sorted rows, while a host defaulting to asc was restored — the reason the same three clicks worked on one screen and not another. The marked state is now a linkedSignal over BOTH inputs. Nothing to do on adoption; you can delete any workaround that re-bound the sort after a clear.",
|
|
379
|
-
"ds-table accepts [loading]=\"true\" and resolves the treatment itself: skeleton rows while filteredData is empty, overlay once rows are on screen. The existing values are untouched — false, 'skeleton' and 'overlay' behave exactly as before, so nothing changes on adoption.
|
|
380
|
-
"Disabled rows and triggers are no longer dimmed twice. ds-select, ds-date-picker, ds-time-picker, ds-menu-item and the shared dropdown row each applied --text-disabled AND opacity 0.6 on top of it, which measured 1.68:1 against the surface where the colour alone gives 2.53:1 (an enabled control is 17.32:1). The opacity is gone from those five and the colour carries the state. A disabled calendar day and ds-toggle-button, where opacity is the ONLY signal, moved from --opacity-muted (0.6) to --opacity-disabled (0.5).
|
|
381
|
-
"ds-button and ds-icon-button use ONE disabled-label recipe for every variant now: oklch(from accent 70% 0.035 h), replacing the 58% base plus the 52% overrides that tonal and outline carried. Reason, measured across the full variant x colour x state matrix: the old lightness sat where a saturated accent already is, so on primary and error the disabled label differed from the live one by 1.16-1.60:1 on four of the five variants (neutral was fine because its enabled label is nearly black). It is now 2.40-2.71:1 on the coloured variants, and up to 6.46:1 on neutral. The disabled label is FAINTER against its own background than before (2.1-2.7:1 where it was 3.4-5.2) - that is the intended trade, and disabled text is exempt from the WCAG contrast floor. Nothing to do on adoption; --ds-button-label-color-disabled and --ds-icon-button-icon-color-disabled still override per component.
|
|
544
|
+
"ds-table accepts [loading]=\"true\" and resolves the treatment itself: skeleton rows while filteredData is empty, overlay once rows are on screen. The existing values are untouched — false, 'skeleton' and 'overlay' behave exactly as before, so nothing changes on adoption.",
|
|
545
|
+
"Disabled rows and triggers are no longer dimmed twice. ds-select, ds-date-picker, ds-time-picker, ds-menu-item and the shared dropdown row each applied --text-disabled AND opacity 0.6 on top of it, which measured 1.68:1 against the surface where the colour alone gives 2.53:1 (an enabled control is 17.32:1). The opacity is gone from those five and the colour carries the state. A disabled calendar day and ds-toggle-button, where opacity is the ONLY signal, moved from --opacity-muted (0.6) to --opacity-disabled (0.5).",
|
|
546
|
+
"ds-button and ds-icon-button use ONE disabled-label recipe for every variant now: oklch(from accent 70% 0.035 h), replacing the 58% base plus the 52% overrides that tonal and outline carried. Reason, measured across the full variant x colour x state matrix: the old lightness sat where a saturated accent already is, so on primary and error the disabled label differed from the live one by 1.16-1.60:1 on four of the five variants (neutral was fine because its enabled label is nearly black). It is now 2.40-2.71:1 on the coloured variants, and up to 6.46:1 on neutral. The disabled label is FAINTER against its own background than before (2.1-2.7:1 where it was 3.4-5.2) - that is the intended trade, and disabled text is exempt from the WCAG contrast floor. Nothing to do on adoption; --ds-button-label-color-disabled and --ds-icon-button-icon-color-disabled still override per component.",
|
|
382
547
|
"components.md — the API digest copied into dist/ds for a consumer's agents — was two renames behind: 46 of the 92 --ds-* tokens it named no longer existed (the bg->bg-color and fg->text/label/icon-color renames, plus --ds-pagehdr-* -> --ds-page-header-*), ds-button was documented with its pre-2026-06 single `variant` axis rather than color x variant, and the topbar section described a --ds-topbar-margin-b that has never existed in the shipped component. All names now verified against src/lib. If your agents or your notes were built from an older copy of this file, re-read it after the bump: token names you may have copied from it are dead.",
|
|
383
548
|
"Focus indicators are now universal: a single base rule, :where(:focus-visible) { outline: none; box-shadow: var(--ds-control-focus-shadow) }, gives the DS ring to anything focusable that does not style focus itself — the close buttons in ds-alert / ds-banner / ds-drawer, links in projected content, and an app's own bare <button>. Before this they fell through to the browser default (a black outline: auto in Chrome). Zero specificity via :where(), so every component rule and every app rule still wins, and the data-focus switch (ring / field / edge / outline) behaves exactly as before. ACTION only if you relied on an element having NO focus indicator: set box-shadow: none on it explicitly.",
|
|
384
549
|
"AutocompleteOption now extends the shared DsOption shape, so it gains `disabled?: boolean`, which it never had before — and ds-autocomplete acts on it: the row carries the .is-disabled class and aria-disabled, ignores the click, and the arrow keys skip it (as does the initial active row when the panel opens or the filter re-runs). Behaviourally this matches ds-select and ds-multi-select, which already honoured the flag. The row greys out as well - measured in the open panel at rgb(155,163,180) against rgb(22,26,40) for an enabled row.",
|
|
385
|
-
"TableColumn.width now accepts the literal 'content' in addition to a pixel number: the column sizes to its widest cell and stops wrapping, leaving the remaining width to the other columns. Purely additive — a numeric width and an unset width behave exactly as before.
|
|
550
|
+
"TableColumn.width now accepts the literal 'content' in addition to a pixel number: the column sizes to its widest cell and stops wrapping, leaving the remaining width to the other columns. Purely additive — a numeric width and an unset width behave exactly as before.",
|
|
386
551
|
"maxVisibleChips as a NUMBER is now a ceiling rather than an exact count on ds-autocomplete and ds-multi-select: at most N chips, and fewer when the trigger is too narrow to hold them beside the '+N more' marker and whatever follows (the text input, the chevron). Reported from a phone: [maxVisibleChips]=\"2\" showed two chips, ran out of width and wrapped the text input onto a second line — the growth the cap exists to prevent. Nothing to change on adoption; a wide trigger still shows exactly N. null is untouched and remains the only mode that does not measure. If you relied on a numeric cap to guarantee a fixed chip COUNT regardless of width, that guarantee is gone by design — the trigger's height is the thing being guaranteed instead.",
|
|
387
552
|
"ds-field-group segments now centre their value vertically. Every segment except ds-button pinned its value to the top of the row: the group stretches the segment, but the host is a block, so the height: 100% each control set on its bordered box resolved against `auto` and the box kept its own content height (a 19.6px line box inside a 40px row at md). Nothing to change on adoption. ACTION only if you had a ::ng-deep override compensating for it -- e.g. ds-field-group ds-input .control { align-items: center } or a padding-top nudge -- which is now double-applied; delete it.",
|
|
388
553
|
"An `error` string now marks the field invalid on its own, across all 14 field components that route through resolveFieldMessage (ds-input, ds-textarea, ds-select, ds-autocomplete, ds-multi-select, ds-date-picker, ds-time-picker, ds-color-picker, ds-otp-input, ds-slider, ds-checkbox, ds-radio, ds-radio-group, ds-switch). Before, error=\"...\" coloured only the message and left the control neutral; it now drives the error border, fill, focus ring and aria-invalid, which is what the input always documented. Nothing to do if you bound [invalid] alongside it. ACTION only if you bound `error` on its own and WANTED a neutral box: move that text to `warning` (advisory) or to `hint`.",
|
|
@@ -401,7 +566,218 @@
|
|
|
401
566
|
"ds-timeline-item now pulls its node column up by half the difference between the heading's line box and the node size, so the marker's centre lands on the heading's rather than 4.2px below it. Each item is that much shorter at the top. Nothing to change on adoption. ACTION only if you compensated for the old offset with your own margin on ds-timeline-item or its node -- that override now double-applies (DELETE-LIST).",
|
|
402
567
|
"Two follow-ups to the shared field-state work, both fixed before release. (1) A field carrying its own error/warning/success state inside a ds-field-group repainted its background, tinting one segment mid-row; the three state rules now carry :not(.in-group), so the group keeps drawing the row's single treatment. (2) ds-field-group's own [invalid] read var(--border-error), a token that has never been declared, so it fell through to currentColor and drew a near-black border; it now resolves through a new public --ds-field-group-border-color-error (default --error). Nothing to change on adoption. ACTION only if you had a ::ng-deep override forcing the group's invalid border back to red, or suppressing a segment's fill inside a group -- both are now redundant (DELETE-LIST).",
|
|
403
568
|
"ds-card no longer cancels Enter and Space for everything inside it. The card bound (keydown.enter)/(keydown.space) with an unconditional preventDefault() on its <article>, and keydown bubbles, so EVERY card - not just elevation=\"interactive\" ones - killed both keys for its whole subtree: Enter in a password field submitted nothing, Space did not toggle a checkbox, Enter on a link did not follow it, and a space could not be typed into a text field. Both handlers now run only on an interactive card and only when the key landed on the card itself. Nothing to do; screens built inside a ds-card simply start working.",
|
|
404
|
-
"ds-table's onRowKey no longer consumes Enter and Space for every target inside an interactive row, so a row's own select checkbox toggles with Space and a cell's button activates with Enter.
|
|
569
|
+
"ds-table's onRowKey no longer consumes Enter and Space for every target inside an interactive row, so a row's own select checkbox toggles with Space and a cell's button activates with Enter.",
|
|
405
570
|
"ds-menu's type-ahead no longer swallows printable characters coming from a text-entry control, so a search or filter input projected into a menu can be typed into. Keys from ordinary menu items still drive the type-ahead. Nothing to do."
|
|
571
|
+
],
|
|
572
|
+
"deleteList": [
|
|
573
|
+
{
|
|
574
|
+
"id": "chip-trigger-line-keeper",
|
|
575
|
+
"surface": [
|
|
576
|
+
"typescript",
|
|
577
|
+
"style"
|
|
578
|
+
],
|
|
579
|
+
"find": [
|
|
580
|
+
"ResizeObserver",
|
|
581
|
+
"@container",
|
|
582
|
+
"maxVisibleChips"
|
|
583
|
+
],
|
|
584
|
+
"why": "A `ResizeObserver`, a container query or a hand-tuned per-breakpoint `maxVisibleChips` number, keeping a chip trigger on one line.",
|
|
585
|
+
"replaceWith": "`maxVisibleChips=\"fit\"`, which re-splits on any width change rather than at the breakpoints you listed"
|
|
586
|
+
},
|
|
587
|
+
{
|
|
588
|
+
"id": "chip-trigger-height-cap",
|
|
589
|
+
"surface": "style",
|
|
590
|
+
"find": [
|
|
591
|
+
"max-height",
|
|
592
|
+
"overflow: hidden"
|
|
593
|
+
],
|
|
594
|
+
"why": "A `max-height` plus `overflow: hidden` on a chip trigger, stopping it growing a line per selection - it clips a chip mid-glyph and hides the count.",
|
|
595
|
+
"replaceWith": "`maxVisibleChips` (a number, or `\"fit\"`), which drops whole chips and reports how many are hidden"
|
|
596
|
+
},
|
|
597
|
+
{
|
|
598
|
+
"id": "sidenav-brand-logo-max-height",
|
|
599
|
+
"surface": "style",
|
|
600
|
+
"find": [
|
|
601
|
+
"max-height",
|
|
602
|
+
"[brand]"
|
|
603
|
+
],
|
|
604
|
+
"why": "Your own `max-height` on a logo projected into `ds-sidenav`'s `[brand]` slot, or a wrapper sized to hold it.",
|
|
605
|
+
"replaceWith": "`--ds-sidenav-brand-max-height` (default `none`, so nothing changes until you set it)"
|
|
606
|
+
},
|
|
607
|
+
{
|
|
608
|
+
"id": "dropdown-panel-corner-global-rule",
|
|
609
|
+
"surface": "style",
|
|
610
|
+
"find": [
|
|
611
|
+
".ds-dropdown-panel",
|
|
612
|
+
".cdk-overlay-pane"
|
|
613
|
+
],
|
|
614
|
+
"why": "A global rule against `.ds-dropdown-panel` or `.cdk-overlay-pane` to change a dropdown corner.",
|
|
615
|
+
"replaceWith": "`--ds-dropdown-panel-radius`, which scopes to one picker when written under a component selector"
|
|
616
|
+
},
|
|
617
|
+
{
|
|
618
|
+
"id": "autocomplete-synthetic-input-clear",
|
|
619
|
+
"surface": "typescript",
|
|
620
|
+
"find": [
|
|
621
|
+
"new Event('input'",
|
|
622
|
+
"dispatchEvent",
|
|
623
|
+
"querySelector"
|
|
624
|
+
],
|
|
625
|
+
"why": "A query for `ds-autocomplete`'s inner `<input>` plus a synthetic `input` event, clearing leftover filter text after a pick.",
|
|
626
|
+
"replaceWith": "`clear()` - and the component clears that text itself now"
|
|
627
|
+
},
|
|
628
|
+
{
|
|
629
|
+
"id": "link-button-local-reset",
|
|
630
|
+
"surface": [
|
|
631
|
+
"template",
|
|
632
|
+
"style"
|
|
633
|
+
],
|
|
634
|
+
"find": [
|
|
635
|
+
".link-button",
|
|
636
|
+
"button.link",
|
|
637
|
+
"appearance: none"
|
|
638
|
+
],
|
|
639
|
+
"why": "A local `.link-button` class, or a padding / border / background / font reset on `button.link` in your overrides.",
|
|
640
|
+
"replaceWith": "the global `.link` class with `.inline` / `.standalone` / `.sm` / `.xs`"
|
|
641
|
+
},
|
|
642
|
+
{
|
|
643
|
+
"id": "stat-value-slot-for-plain-text",
|
|
644
|
+
"surface": [
|
|
645
|
+
"template",
|
|
646
|
+
"style"
|
|
647
|
+
],
|
|
648
|
+
"find": [
|
|
649
|
+
"dsStatValue",
|
|
650
|
+
"white-space: normal"
|
|
651
|
+
],
|
|
652
|
+
"why": "A `[dsStatValue]` projection used only to set `white-space: normal` or a smaller font size on a TEXT value.",
|
|
653
|
+
"replaceWith": "the two hooks on the ordinary `value` input - keep the slot for a value that is genuinely another component, like a badge"
|
|
654
|
+
},
|
|
655
|
+
{
|
|
656
|
+
"id": "search-debounce-wrapper",
|
|
657
|
+
"surface": "typescript",
|
|
658
|
+
"find": [
|
|
659
|
+
"debounceTime",
|
|
660
|
+
"ds-search"
|
|
661
|
+
],
|
|
662
|
+
"why": "A wrapper around `ds-search` adding a typing debounce (typically 200ms) with an immediate path when the field empties.",
|
|
663
|
+
"replaceWith": "`[debounce]`, which does both plus the Enter flush"
|
|
664
|
+
},
|
|
665
|
+
{
|
|
666
|
+
"id": "filter-bar-trigger-size-pins",
|
|
667
|
+
"surface": "style",
|
|
668
|
+
"find": [
|
|
669
|
+
"--ds-button-height",
|
|
670
|
+
"--ds-button-font-size",
|
|
671
|
+
"--ds-button-pad-x"
|
|
672
|
+
],
|
|
673
|
+
"why": "`--ds-button-height` / `--ds-button-font-size` / `--ds-button-pad-x` pinned under `ds-filter-bar` to force its trigger smaller.",
|
|
674
|
+
"replaceWith": "`triggerSize=\"sm\"`"
|
|
675
|
+
},
|
|
676
|
+
{
|
|
677
|
+
"id": "modal-dividers-repeated-and-padding-hacks",
|
|
678
|
+
"surface": [
|
|
679
|
+
"template",
|
|
680
|
+
"style"
|
|
681
|
+
],
|
|
682
|
+
"find": [
|
|
683
|
+
"[dividers]=\"false\"",
|
|
684
|
+
".modal > .header",
|
|
685
|
+
"!important"
|
|
686
|
+
],
|
|
687
|
+
"why": "`[dividers]=\"false\"` repeated on every modal (one consumer had 41), or a reach into `.modal > .header` / `.body` / `.actions` with `!important` because hiding the rules left the padding stacked.",
|
|
688
|
+
"replaceWith": "`provideDsConfig({ modal: { dividers: false } })`, which drops the rules AND the padding that existed to clear them"
|
|
689
|
+
},
|
|
690
|
+
{
|
|
691
|
+
"id": "tab-last-visited-helper",
|
|
692
|
+
"surface": "typescript",
|
|
693
|
+
"find": [
|
|
694
|
+
"sessionStorage",
|
|
695
|
+
"tab"
|
|
696
|
+
],
|
|
697
|
+
"why": "A helper keeping the last visited tab per path in `sessionStorage`.",
|
|
698
|
+
"replaceWith": "`rememberLastTab` on `ds-tabs` (needs `urlParam`, which supplies the names)"
|
|
699
|
+
},
|
|
700
|
+
{
|
|
701
|
+
"id": "auth-brand-adapter",
|
|
702
|
+
"surface": "typescript",
|
|
703
|
+
"find": [
|
|
704
|
+
"logoLetter",
|
|
705
|
+
"brandAccent",
|
|
706
|
+
"indexOf"
|
|
707
|
+
],
|
|
708
|
+
"why": "An adapter component that injects a brand object and fans it out into `brand` / `logoLetter` / `tagline` bindings on each auth screen.",
|
|
709
|
+
"replaceWith": "`provideDsConfig({ brand: … })`; the accent stays a `[dsBrandName]` projection instead of a `brandAccent` string plus an `indexOf` split"
|
|
710
|
+
},
|
|
711
|
+
{
|
|
712
|
+
"id": "avatar-initials-wiring",
|
|
713
|
+
"surface": [
|
|
714
|
+
"template",
|
|
715
|
+
"typescript"
|
|
716
|
+
],
|
|
717
|
+
"find": [
|
|
718
|
+
"initials",
|
|
719
|
+
"ds-avatar"
|
|
720
|
+
],
|
|
721
|
+
"why": "The `ds-avatar` wiring around your own initials helper (the helper itself stays yours).",
|
|
722
|
+
"replaceWith": "`[name]` plus one `[initialsRule]`"
|
|
723
|
+
},
|
|
724
|
+
{
|
|
725
|
+
"id": "per-element-repeated-attribute",
|
|
726
|
+
"surface": "template",
|
|
727
|
+
"find": [
|
|
728
|
+
"[stickyScrollbar]=\"true\"",
|
|
729
|
+
"size=\"sm\""
|
|
730
|
+
],
|
|
731
|
+
"why": "An attribute repeated identically on every element - one consumer binds `[stickyScrollbar]=\"true\"` on all 35 of its tables and `size=\"sm\"` on 146 buttons.",
|
|
732
|
+
"replaceWith": "`provideDsConfig` with the matching section (`table`, `control.size`, …)"
|
|
733
|
+
},
|
|
734
|
+
{
|
|
735
|
+
"id": "export-csv-on-server-paged-table",
|
|
736
|
+
"surface": "typescript",
|
|
737
|
+
"find": [
|
|
738
|
+
"exportCsv("
|
|
739
|
+
],
|
|
740
|
+
"why": "A button wired to `exportCsv()` on a SERVER-PAGED table - it serialises the rows the table holds, so the file is one page.",
|
|
741
|
+
"replaceWith": "`runExport()` with an `exportFetcher`"
|
|
742
|
+
},
|
|
743
|
+
{
|
|
744
|
+
"id": "table-loading-treatment-computed",
|
|
745
|
+
"surface": "typescript",
|
|
746
|
+
"find": [
|
|
747
|
+
"? 'overlay' : 'skeleton'",
|
|
748
|
+
"'skeleton'",
|
|
749
|
+
"'overlay'"
|
|
750
|
+
],
|
|
751
|
+
"why": "The computed beside every list table - `items().length > 0 ? 'overlay' : 'skeleton'` - one consumer feature carried three copies of it.",
|
|
752
|
+
"replaceWith": "`[loading]=\"true\"`, which resolves the treatment itself; pin a value only where you mean to override the rule"
|
|
753
|
+
},
|
|
754
|
+
{
|
|
755
|
+
"id": "opacity-muted-disabled-retune",
|
|
756
|
+
"surface": "style",
|
|
757
|
+
"find": [
|
|
758
|
+
"--opacity-muted"
|
|
759
|
+
],
|
|
760
|
+
"why": "An override retuning `--opacity-muted` to compensate for a washed-out disabled state. That token is a de-emphasis level for hints and secondary text and carries no disabled state at all - and on `ds-button` / `ds-icon-button` it was always inert, because neither ever read it.",
|
|
761
|
+
"replaceWith": "`--ds-button-label-color-disabled` / `--ds-icon-button-icon-color-disabled`"
|
|
762
|
+
},
|
|
763
|
+
{
|
|
764
|
+
"id": "table-fit-content-deep-rule",
|
|
765
|
+
"surface": "style",
|
|
766
|
+
"find": [
|
|
767
|
+
"width: 1%",
|
|
768
|
+
"white-space: nowrap"
|
|
769
|
+
],
|
|
770
|
+
"why": "A `::ng-deep ds-table { .table th, .table td { width: 1%; white-space: nowrap } }` override - the shrink-to-content idiom.",
|
|
771
|
+
"replaceWith": "`TableColumn.width: 'content'`"
|
|
772
|
+
},
|
|
773
|
+
{
|
|
774
|
+
"id": "row-control-stop-propagation-for-keys",
|
|
775
|
+
"surface": "template",
|
|
776
|
+
"find": [
|
|
777
|
+
"stopPropagation"
|
|
778
|
+
],
|
|
779
|
+
"why": "A `stopPropagation()` on a control inside a clickable row, added so the row would not steal the control's KEY. Read each hit before deleting: a CLICK still bubbles (`onRowClick` only skips a target inside an `<input>`), so a click-path guard stays.",
|
|
780
|
+
"replaceWith": "nothing on the key path - `onRowKey` now requires `target === currentTarget`"
|
|
781
|
+
}
|
|
406
782
|
]
|
|
407
783
|
}
|