@ids-group-ltd/ids-design-system 0.12.1 → 0.12.3

This diff represents the content of publicly available package versions that have been released to one of the supported registries. The information contained in this diff is provided for informational purposes only and reflects changes between package versions as they appear in their respective public registries.
Files changed (90) hide show
  1. package/CHANGELOG.md +394 -0
  2. package/components.md +3 -1
  3. package/docs/agent/forms/ds-button.md +3 -1
  4. package/fesm2022/ids-group-ltd-ids-design-system-components-auth-layout.mjs +2 -2
  5. package/fesm2022/ids-group-ltd-ids-design-system-components-auth-layout.mjs.map +1 -1
  6. package/fesm2022/ids-group-ltd-ids-design-system-components-autocomplete.mjs +10 -13
  7. package/fesm2022/ids-group-ltd-ids-design-system-components-autocomplete.mjs.map +1 -1
  8. package/fesm2022/ids-group-ltd-ids-design-system-components-breadcrumbs.mjs +20 -21
  9. package/fesm2022/ids-group-ltd-ids-design-system-components-breadcrumbs.mjs.map +1 -1
  10. package/fesm2022/ids-group-ltd-ids-design-system-components-button.mjs +57 -40
  11. package/fesm2022/ids-group-ltd-ids-design-system-components-button.mjs.map +1 -1
  12. package/fesm2022/ids-group-ltd-ids-design-system-components-checkbox.mjs +9 -4
  13. package/fesm2022/ids-group-ltd-ids-design-system-components-checkbox.mjs.map +1 -1
  14. package/fesm2022/ids-group-ltd-ids-design-system-components-color-picker.mjs +10 -7
  15. package/fesm2022/ids-group-ltd-ids-design-system-components-color-picker.mjs.map +1 -1
  16. package/fesm2022/ids-group-ltd-ids-design-system-components-date-picker.mjs +13 -9
  17. package/fesm2022/ids-group-ltd-ids-design-system-components-date-picker.mjs.map +1 -1
  18. package/fesm2022/ids-group-ltd-ids-design-system-components-dropzone.mjs +2 -2
  19. package/fesm2022/ids-group-ltd-ids-design-system-components-dropzone.mjs.map +1 -1
  20. package/fesm2022/ids-group-ltd-ids-design-system-components-field-group.mjs +2 -2
  21. package/fesm2022/ids-group-ltd-ids-design-system-components-field-group.mjs.map +1 -1
  22. package/fesm2022/ids-group-ltd-ids-design-system-components-filter-bar.mjs +2 -2
  23. package/fesm2022/ids-group-ltd-ids-design-system-components-filter-bar.mjs.map +1 -1
  24. package/fesm2022/ids-group-ltd-ids-design-system-components-input.mjs +2 -2
  25. package/fesm2022/ids-group-ltd-ids-design-system-components-input.mjs.map +1 -1
  26. package/fesm2022/ids-group-ltd-ids-design-system-components-list.mjs +2 -2
  27. package/fesm2022/ids-group-ltd-ids-design-system-components-list.mjs.map +1 -1
  28. package/fesm2022/ids-group-ltd-ids-design-system-components-modal.mjs +5 -5
  29. package/fesm2022/ids-group-ltd-ids-design-system-components-modal.mjs.map +1 -1
  30. package/fesm2022/ids-group-ltd-ids-design-system-components-multi-select.mjs +10 -13
  31. package/fesm2022/ids-group-ltd-ids-design-system-components-multi-select.mjs.map +1 -1
  32. package/fesm2022/ids-group-ltd-ids-design-system-components-otp-input.mjs +2 -2
  33. package/fesm2022/ids-group-ltd-ids-design-system-components-otp-input.mjs.map +1 -1
  34. package/fesm2022/ids-group-ltd-ids-design-system-components-popover.mjs +13 -5
  35. package/fesm2022/ids-group-ltd-ids-design-system-components-popover.mjs.map +1 -1
  36. package/fesm2022/ids-group-ltd-ids-design-system-components-progress.mjs +2 -2
  37. package/fesm2022/ids-group-ltd-ids-design-system-components-progress.mjs.map +1 -1
  38. package/fesm2022/ids-group-ltd-ids-design-system-components-radio-group.mjs +12 -12
  39. package/fesm2022/ids-group-ltd-ids-design-system-components-radio-group.mjs.map +1 -1
  40. package/fesm2022/ids-group-ltd-ids-design-system-components-select.mjs +10 -13
  41. package/fesm2022/ids-group-ltd-ids-design-system-components-select.mjs.map +1 -1
  42. package/fesm2022/ids-group-ltd-ids-design-system-components-sidenav-footer.mjs +2 -2
  43. package/fesm2022/ids-group-ltd-ids-design-system-components-sidenav-footer.mjs.map +1 -1
  44. package/fesm2022/ids-group-ltd-ids-design-system-components-sidenav.mjs +11 -4
  45. package/fesm2022/ids-group-ltd-ids-design-system-components-sidenav.mjs.map +1 -1
  46. package/fesm2022/ids-group-ltd-ids-design-system-components-skeleton.mjs +2 -2
  47. package/fesm2022/ids-group-ltd-ids-design-system-components-skeleton.mjs.map +1 -1
  48. package/fesm2022/ids-group-ltd-ids-design-system-components-stat.mjs +2 -2
  49. package/fesm2022/ids-group-ltd-ids-design-system-components-stat.mjs.map +1 -1
  50. package/fesm2022/ids-group-ltd-ids-design-system-components-switch.mjs +9 -4
  51. package/fesm2022/ids-group-ltd-ids-design-system-components-switch.mjs.map +1 -1
  52. package/fesm2022/ids-group-ltd-ids-design-system-components-table-columns.mjs +8 -20
  53. package/fesm2022/ids-group-ltd-ids-design-system-components-table-columns.mjs.map +1 -1
  54. package/fesm2022/ids-group-ltd-ids-design-system-components-table-export.mjs +1 -1
  55. package/fesm2022/ids-group-ltd-ids-design-system-components-table-export.mjs.map +1 -1
  56. package/fesm2022/ids-group-ltd-ids-design-system-components-table.mjs +85 -9
  57. package/fesm2022/ids-group-ltd-ids-design-system-components-table.mjs.map +1 -1
  58. package/fesm2022/ids-group-ltd-ids-design-system-components-tabs.mjs +2 -2
  59. package/fesm2022/ids-group-ltd-ids-design-system-components-tabs.mjs.map +1 -1
  60. package/fesm2022/ids-group-ltd-ids-design-system-components-textarea.mjs +2 -2
  61. package/fesm2022/ids-group-ltd-ids-design-system-components-textarea.mjs.map +1 -1
  62. package/fesm2022/ids-group-ltd-ids-design-system-components-time-picker.mjs +10 -7
  63. package/fesm2022/ids-group-ltd-ids-design-system-components-time-picker.mjs.map +1 -1
  64. package/fesm2022/ids-group-ltd-ids-design-system-components-tree.mjs +2 -2
  65. package/fesm2022/ids-group-ltd-ids-design-system-components-tree.mjs.map +1 -1
  66. package/fesm2022/ids-group-ltd-ids-design-system-components.mjs +43 -1
  67. package/fesm2022/ids-group-ltd-ids-design-system-components.mjs.map +1 -1
  68. package/fesm2022/ids-group-ltd-ids-design-system-core.mjs.map +1 -1
  69. package/migrations/0.12.0.json +30 -2
  70. package/migrations/0.12.1.json +132 -6
  71. package/migrations/0.12.2.json +291 -0
  72. package/migrations/0.12.3.json +83 -0
  73. package/package.json +1 -1
  74. package/styles/_check-box.scss +7 -0
  75. package/styles/_clear-button.scss +28 -0
  76. package/styles/_control-line.scss +45 -0
  77. package/styles/_field-state.scss +14 -15
  78. package/styles/_focus.scss +31 -60
  79. package/styles/_table-controls.scss +66 -0
  80. package/styles/_tokens.scss +22 -31
  81. package/types/ids-group-ltd-ids-design-system-components-auth-layout.d.ts +2 -2
  82. package/types/ids-group-ltd-ids-design-system-components-breadcrumbs.d.ts +8 -17
  83. package/types/ids-group-ltd-ids-design-system-components-button.d.ts +26 -29
  84. package/types/ids-group-ltd-ids-design-system-components-checkbox.d.ts +6 -1
  85. package/types/ids-group-ltd-ids-design-system-components-radio-group.d.ts +10 -10
  86. package/types/ids-group-ltd-ids-design-system-components-sidenav.d.ts +9 -2
  87. package/types/ids-group-ltd-ids-design-system-components-switch.d.ts +6 -1
  88. package/types/ids-group-ltd-ids-design-system-components-table.d.ts +18 -1
  89. package/types/ids-group-ltd-ids-design-system-components.d.ts +37 -2
  90. package/types/ids-group-ltd-ids-design-system-core.d.ts +5 -0
@@ -0,0 +1,291 @@
1
+ {
2
+ "version": "0.12.2",
3
+ "items": [
4
+ {
5
+ "id": "subclass-members-grew",
6
+ "kind": "behavior",
7
+ "surface": "typescript",
8
+ "old": "class MyThing extends TableComponent | SidenavGroupComponent",
9
+ "new": null,
10
+ "action": "Build after upgrading, then rename or mark `override` any member the compiler reports as colliding.",
11
+ "appliesWhen": "Only a class that extends TableComponent or SidenavGroupComponent. A consumer who uses the elements in a template needs nothing — no existing input, output, token or class changed name or type in this release.",
12
+ "pitfall": "Three of the four members are not public API, which is no protection: a redeclared private or protected member fails with TS2415 exactly as a public collision does, and a same-named method whose signature differs fails with TS2416 instead.",
13
+ "note": "TableComponent gained `showsLoadingSpace`, which keeps a body open while the table loads with no rows; `publishHeadHeight`, which measures the header for the scrim to inset against; `scrollAncestor`, which finds the scrollport a sticky offset resolves against; `hasAnyColumnFilter`, which decides whether the column-filter panel renders; `isFilterPanelOpen`, which tells a header button whether the open panel is its own; and the new `stickyScrollbarOffset` input with its `stickyScrollbarOffsetResolved`. SidenavGroupComponent gained the new `routerLink` input and `headerNavigates`, which decides whether the header splits into a link and its own caret. Named here so a subclass collision is greppable from the release that introduced them.",
14
+ "verify": "The app builds with no TS2415 or TS2416 naming TableComponent or SidenavGroupComponent, and no member of your subclass is called showsLoadingSpace, publishHeadHeight, scrollAncestor, hasAnyColumnFilter, isFilterPanelOpen, stickyScrollbarOffset, stickyScrollbarOffsetResolved, routerLink or headerNavigates.",
15
+ "searchHints": [
16
+ "extends TableComponent",
17
+ "extends SidenavGroupComponent",
18
+ "showsLoadingSpace",
19
+ "publishHeadHeight",
20
+ "scrollAncestor",
21
+ "hasAnyColumnFilter",
22
+ "isFilterPanelOpen",
23
+ "stickyScrollbarOffset",
24
+ "stickyScrollbarOffsetResolved",
25
+ "headerNavigates",
26
+ "TS2415",
27
+ "TS2416"
28
+ ],
29
+ "detect": [
30
+ "extends TableComponent",
31
+ "extends SidenavGroupComponent",
32
+ "override showsLoadingSpace",
33
+ "override publishHeadHeight",
34
+ "override scrollAncestor",
35
+ "override hasAnyColumnFilter",
36
+ "override isFilterPanelOpen",
37
+ "override stickyScrollbarOffset",
38
+ "override routerLink",
39
+ "override headerNavigates"
40
+ ],
41
+ "restore": null
42
+ },
43
+ {
44
+ "id": "modal-fullscreen-height-is-a-target",
45
+ "kind": "behavior",
46
+ "surface": "style",
47
+ "old": "--modal-h-fullscreen",
48
+ "new": null,
49
+ "action": "Where you set `--modal-h-fullscreen`, decide whether you meant a ceiling or a height, and lower the value below 90dvh if you want the panel shorter than the screen.",
50
+ "appliesWhen": "Only a modal opened fullscreen, and only where you set `--modal-h-fullscreen` yourself or relied on a short body keeping the panel small. A modal opened at any other size is untouched, and the token keeps its name and its own value.",
51
+ "pitfall": "Setting the token above 90dvh looks like it does nothing: the modal's own ceiling still clips the panel, so the used height stays 90dvh and no warning says the value was ignored.",
52
+ "note": "The fullscreen class fed the token to `max-height`, so a short body shrank the panel and a tall one stopped at the token. It feeds `height` now, so the panel is that tall whatever the body holds, still clipped by the modal's 90dvh ceiling. The panel already lays out as a column with a scrolling body, so the room a short body no longer reclaims goes to the body and the footer sits at the bottom of the screen.",
53
+ "verify": "A fullscreen modal with two lines of content is as tall as a fullscreen modal with fifty, and one you sized through the token is `min(your value, 90dvh)` tall.",
54
+ "searchHints": [
55
+ "--modal-h-fullscreen",
56
+ "fullscreen"
57
+ ],
58
+ "restore": null
59
+ },
60
+ {
61
+ "id": "date-picker-focus-resolves-the-field-family",
62
+ "kind": "behavior",
63
+ "surface": "style",
64
+ "old": "--ds-date-picker-focus-shadow",
65
+ "new": null,
66
+ "action": "Retune the date picker's focus indicator through `--ds-field-focus-shadow`, or set `--ds-date-picker-focus-shadow` outright.",
67
+ "appliesWhen": "Only a brand that retunes focus through the control family — `--ds-control-focus-shadow` or the per-control tokens. An explicit `--ds-date-picker-focus-shadow` override still wins and needs nothing. `ds-time-picker` still resolves the control family, so the two pickers focus differently until you set both.",
68
+ "pitfall": "A control-family override is a custom property like any other: it still sets, it still cascades, and the date picker simply no longer reads it. Nothing errors, and the field draws the default halo.",
69
+ "note": "The trigger is field-shaped and was drawing the two-band control ring, so it read as a button beside inputs that draw one soft halo. It resolves the field family now, which also means it follows the `data-focus` switch — `ring`, `edge` and `inset` reach it, and they did not before.",
70
+ "verify": "Focusing the date field draws the same indicator as focusing a text input beside it, and switching `data-focus` changes both together.",
71
+ "searchHints": [
72
+ "--ds-date-picker-focus-shadow",
73
+ "--ds-control-focus-shadow",
74
+ "--ds-field-focus-shadow",
75
+ "focus-shadow"
76
+ ],
77
+ "restore": "--ds-date-picker-focus-shadow: var(--ds-control-focus-shadow);"
78
+ },
79
+ {
80
+ "id": "progress-warning-bar-resolves-a-palette-yellow",
81
+ "kind": "behavior",
82
+ "surface": "style",
83
+ "old": "--ds-progress-bar-color-warning",
84
+ "new": null,
85
+ "action": "Recolour the warning bar through `--ds-progress-bar-color-warning` rather than through `--warning-hover`.",
86
+ "appliesWhen": "Only a brand that recoloured the bar by way of `--warning-hover`. An explicit `--ds-progress-bar-color-warning` override still wins. `--warning-hover` keeps its name and value and is still read elsewhere.",
87
+ "pitfall": "The bar moves in opposite directions per theme, so a screenshot check on one theme proves nothing about the other: the light bar gets more saturated and the dark bar gets darker.",
88
+ "note": "The fallback resolved to a hover derivation of the warning hue, which mixes toward black in the light theme and toward white in the dark one — so the light bar read olive and the dark bar read washed out, and neither matched the warning colour anywhere else. Both themes resolve the same palette yellow now.",
89
+ "verify": "The warning progress bar is the same colour in both themes, and matches the warning hue used by the other status surfaces.",
90
+ "searchHints": [
91
+ "--ds-progress-bar-color-warning",
92
+ "--warning-hover"
93
+ ],
94
+ "restore": "--ds-progress-bar-color-warning: var(--warning-hover);"
95
+ },
96
+ {
97
+ "id": "skeleton-shimmer-reads-its-own-duration-token",
98
+ "kind": "behavior",
99
+ "surface": "style",
100
+ "old": "--duration-loop-slow",
101
+ "new": null,
102
+ "action": "Set `--ds-skeleton-wave-duration` wherever you were retuning the skeleton through `--duration-loop-slow`.",
103
+ "appliesWhen": "Only a brand that set `--duration-loop-slow` and expected the skeleton to follow. That token keeps its name and value and still drives everything else that reads it; the skeleton is what stopped reading it.",
104
+ "pitfall": "The shimmer keeps animating either way, so an override that no longer lands looks like a value that was simply too small to notice rather than one nothing reads.",
105
+ "note": "The wave now tiles by construction and travels exactly one period per loop, so its duration is a property of the wave rather than of the shared loop family. The loop runs 3400ms where the shared token gave it 1400ms, and passes no longer rest between crossings. `--ds-skeleton-wave-angle` turns the gradient only — the tile size and the travel are pinned to the 45° diagonal, so an angle far from the default tiles visibly.",
106
+ "verify": "Setting `--ds-skeleton-wave-duration` changes how fast the shimmer crosses, and setting `--duration-loop-slow` alone leaves it unchanged.",
107
+ "searchHints": [
108
+ "--duration-loop-slow",
109
+ "--ds-skeleton-wave-duration",
110
+ "ds-skeleton"
111
+ ],
112
+ "restore": "--ds-skeleton-wave-duration: var(--duration-loop-slow);"
113
+ },
114
+ {
115
+ "id": "autocomplete-trigger-open-class-removed",
116
+ "kind": "behavior",
117
+ "surface": "style",
118
+ "old": "ds-autocomplete .autocomplete-trigger.open",
119
+ "new": null,
120
+ "action": "Rewrite any rule keyed off `.autocomplete-trigger.open` to key off the input's expanded state: `.autocomplete-trigger:has(input[aria-expanded=\"true\"])`.",
121
+ "appliesWhen": "Only a stylesheet of yours that selected the open state by class. Nothing in a template or in TypeScript changes — `isOpen()` and the panel are untouched, and this library never styled `.open`, so no look of ours moves.",
122
+ "pitfall": "The rule stops matching with no error anywhere: the class is simply absent, so the open state renders as the resting state and nothing reports it. A build passes, a test that asserts on computed style is the only thing that catches it.",
123
+ "note": "The class reported a state it never painted. `aria-expanded` was already on the input for assistive technology, so the state stayed reachable without a second copy of it in the class list.",
124
+ "verify": "No stylesheet selects `.autocomplete-trigger.open`, and every rule that dressed the open state now selects it through `aria-expanded`.",
125
+ "searchHints": [
126
+ "autocomplete-trigger.open",
127
+ ".open",
128
+ "aria-expanded"
129
+ ],
130
+ "detect": [
131
+ "autocomplete-trigger.open",
132
+ "ds-autocomplete .open",
133
+ "::ng-deep .open"
134
+ ]
135
+ },
136
+ {
137
+ "id": "autocomplete-trigger-error-class-removed",
138
+ "kind": "behavior",
139
+ "surface": "style",
140
+ "old": "ds-autocomplete .autocomplete-trigger.error",
141
+ "new": null,
142
+ "action": "Rewrite any rule keyed off `.autocomplete-trigger.error` to key off the host attribute: `ds-autocomplete[data-field-state=\"error\"] .autocomplete-trigger`.",
143
+ "appliesWhen": "Only a stylesheet of yours that selected the error state by class on the trigger. The field family's own error paint has always come from `data-field-state` on the host and is unchanged.",
144
+ "pitfall": "An invalid field keeps rendering as a valid one in your own styling, with nothing raised — and it is the state a reader most needs to see, so the silence costs more here than on a cosmetic class.",
145
+ "note": "`data-field-state` carries `error`, `warning` and `success`, which one boolean class could not, and it is where this library reads the state itself — so a rule written against it also follows a warning.",
146
+ "verify": "No stylesheet selects `.autocomplete-trigger.error`, and the rules that dressed the error state select `[data-field-state=\"error\"]` on the host.",
147
+ "searchHints": [
148
+ "autocomplete-trigger.error",
149
+ ".error",
150
+ "data-field-state"
151
+ ],
152
+ "detect": [
153
+ "autocomplete-trigger.error",
154
+ "ds-autocomplete .error",
155
+ "::ng-deep .error"
156
+ ]
157
+ },
158
+ {
159
+ "id": "multi-select-trigger-readonly-class-removed",
160
+ "kind": "behavior",
161
+ "surface": "style",
162
+ "old": "ds-multi-select .field-trigger.readonly",
163
+ "new": null,
164
+ "action": "Rewrite any rule keyed off `.field-trigger.readonly` to key off the attribute already on that element: `.field-trigger[aria-readonly=\"true\"]`.",
165
+ "appliesWhen": "Only a stylesheet of yours that selected the read-only trigger by class. `readOnly` itself, and everything it does to focus and opening, is unchanged. `ds-select`'s trigger never carried the class, so a rule shared between the two was already only half working.",
166
+ "pitfall": "A read-only trigger renders as an editable one under your own styling, which invites a click that then does nothing — and no tool reports the dead selector.",
167
+ "note": "`aria-readonly` sits on the same element and says the same thing to assistive technology, so the state needed no class beside it.",
168
+ "verify": "No stylesheet selects `.field-trigger.readonly`, and the read-only styling selects `aria-readonly` instead.",
169
+ "searchHints": [
170
+ "field-trigger.readonly",
171
+ ".readonly",
172
+ "aria-readonly"
173
+ ],
174
+ "detect": [
175
+ "field-trigger.readonly",
176
+ "ds-multi-select .readonly",
177
+ "::ng-deep .readonly"
178
+ ]
179
+ },
180
+ {
181
+ "id": "tabs-badge-tone-classes-removed",
182
+ "kind": "behavior",
183
+ "surface": "style",
184
+ "old": "ds-tabs .badge.neutral",
185
+ "new": null,
186
+ "action": "Drop `.neutral` and `.count` from any rule selecting the tab count badge and select `.badge` on its own.",
187
+ "appliesWhen": "Only a stylesheet of yours that qualified the tab badge with either word. The badge's own look is unchanged — it always came from `.badge` alone, and `.neutral` and `.count` never carried a declaration.",
188
+ "pitfall": "A rule qualified with either word stops matching entirely rather than partly, so a recoloured badge returns to the library's grey pill and reads as intentional.",
189
+ "note": "Both were tone and role markers copied from `ds-badge`'s vocabulary, where they do carry styling. On a tab they never did, and keeping them implied a tone the component does not offer.",
190
+ "verify": "No stylesheet selects `.badge.neutral` or `.badge.count` under `ds-tabs`, and the badge rules select `.badge`.",
191
+ "searchHints": [
192
+ "badge.neutral",
193
+ "badge.count",
194
+ "badge neutral count"
195
+ ],
196
+ "detect": [
197
+ "badge.neutral",
198
+ "badge.count",
199
+ "ds-tabs .neutral",
200
+ "ds-tabs .count"
201
+ ]
202
+ },
203
+ {
204
+ "id": "table-hscroll-bottom-token-renamed",
205
+ "kind": "token-rename",
206
+ "surface": "style",
207
+ "old": "--ds-table-hscroll-bottom",
208
+ "new": "--ds-table-sticky-scrollbar-offset",
209
+ "action": "Rename `--ds-table-hscroll-bottom` to `--ds-table-sticky-scrollbar-offset`, keeping the value — unless the value is a negative offset equal to your scroll container's bottom padding, which is deleted instead (delete list: table-hscroll-bottom-workaround).",
210
+ "appliesWhen": "Only a stylesheet of yours that sets the token. Nothing in a template or in TypeScript changes, and `stickyScrollbar` itself, the bar's behaviour and every other `--ds-table-*` token are untouched.",
211
+ "pitfall": "The old name is inert rather than invalid, so a declaration left behind is not an error anywhere — the bar simply stops taking your offset and falls back to the measured one, which on most pages looks almost right.",
212
+ "note": "The knob now carries the name of the feature it belongs to, beside `stickyScrollbar` and the new `[stickyScrollbarOffset]` input, so the three greppable spellings of one idea agree. The same value is also reachable per table through that input and app-wide through `DS_CONFIG.table.stickyScrollbarOffset`; the token still out-ranks both.",
213
+ "verify": "No stylesheet declares `--ds-table-hscroll-bottom`, and every offset the sticky scrollbar takes comes from `--ds-table-sticky-scrollbar-offset`, `[stickyScrollbarOffset]` or `DS_CONFIG.table.stickyScrollbarOffset`.",
214
+ "searchHints": [
215
+ "--ds-table-hscroll-bottom",
216
+ "hscroll-bottom",
217
+ "hscroll"
218
+ ],
219
+ "detect": [
220
+ "--ds-table-hscroll-bottom"
221
+ ]
222
+ },
223
+ {
224
+ "id": "table-expand-panel-inner-wrapper",
225
+ "kind": "behavior",
226
+ "surface": "style",
227
+ "old": "ds-table .expand-panel-cell",
228
+ "new": null,
229
+ "action": "Re-point a rule that selected the expanded row’s content as a direct child of `.expand-panel-cell` at `.expand-panel-inner`, or drop the child combinator.",
230
+ "appliesWhen": "Only a stylesheet of yours that reaches inside the expanded row of a `ds-table` with a child combinator. A rule using a descendant selector already matches through the new wrapper and needs nothing, and nothing changes for the template you project — its own root element is untouched.",
231
+ "pitfall": "The selector simply stops matching: the panel keeps the library’s own layout and your rule is silently inert. No build error, and the row still opens, so the difference is only visible in the expanded content’s own spacing or width.",
232
+ "note": "The expanded row now animates open by interpolating its cell’s `grid-template-rows` from `0fr` to `1fr`, which a height of `auto` cannot do. A grid track can only clip one child, so the projected template is wrapped in `.expand-panel-inner`, which carries the `overflow: hidden` the reveal needs. That wrapper is the only structural change; class names on the cell itself are unchanged.",
233
+ "verify": "Every rule that styled the expanded row’s content matches an element again — inspect an open row and confirm your declarations appear on it rather than being overridden or absent.",
234
+ "searchHints": [
235
+ "expand-panel-cell",
236
+ "expand-panel",
237
+ "expandTemplate",
238
+ "rowExpandable"
239
+ ],
240
+ "restore": null
241
+ }
242
+ ],
243
+ "informational": [
244
+ "The `ds-skeleton` shimmer travels diagonally now and crosses as two waves per period, one quiet and one main, with no seam anywhere in the loop. Four new hooks with defaults — `--ds-skeleton-wave-period`, `--ds-skeleton-wave-duration`, `--ds-skeleton-wave-angle`, `--ds-skeleton-wave-echo-color`. The tone is unchanged; a skeleton you never tuned simply reads calmer. Only the duration hook needs an edit, and only if you were retuning it through the shared loop token.",
245
+ "A `ds-table` loading in `overlay` mode with no rows now holds one `aria-hidden` spacer row's worth of height instead of collapsing onto its header. Nothing to change unless a test asserts an empty tbody during an overlay load. `skeleton` loading is unaffected.",
246
+ "The `ds-table` loading scrim measures the header after render and re-measures on resize, so it starts below the header on the first frame rather than at a 40px fallback. `--ds-table-head-h` still overrides the measurement.",
247
+ "The `ds-table` selection checkbox is centred against the line box instead of sitting on the text baseline, so the header row no longer changes height when the select-all mark swaps between its tick and its indeterminate bar. `ds-checkbox` lays its own box out as a flex item and never showed this.",
248
+ "`ds-date-picker`'s calendar glyph is two pixels smaller so it matches the cap height of the value beside it, and its text input now spans the field's height so a click above or below the digits places the caret rather than opening the calendar.",
249
+ "`ds-dropzone` shows the hand cursor once files are listed. The zone was always clickable; only the cursor said otherwise.",
250
+ "`ds-sidenav-group` takes a new optional `routerLink`. Unset, which is the default and what every existing group has, the header only expands and nothing changed. Set together with `expandable`, the header navigates and the caret becomes its own button, so the group's own DOM gains a `.group-header-row` wrapper and a `.group-caret-button`, and `.group-header` becomes an `a` rather than a `button`. `routerLink` without `expandable` is ignored.",
251
+ "The `ds-table` column panel and the header button that opens it, both rendered by `dsTableColumns`, draw with their own styles instead of the browser's native checkbox, buttons and link. Markup, class names and API are unchanged; a stylesheet of yours that reached `.col-picker`, `.col-picker-row`, `.col-picker-option`, `.col-drag`, `.col-move`, `.col-move-btn`, `.col-reset` or `.col-picker-btn` by a bare class name now competes with a scoped rule, so qualify the selector where your override stopped landing.",
252
+ "A `ds-table` sticky horizontal scrollbar rests on the scroll container's visible bottom edge rather than one padding-bottom above it, measured off the scroll ancestor and re-measured on resize. `--ds-table-hscroll-bottom` still overrides outright; a negative value equal to your own container's padding is now a second offset (delete list: table-hscroll-bottom-workaround).",
253
+ "`clearable` on `ds-autocomplete` and `ds-multi-select` now draws the same clear button as `ds-select`, where both previously rendered the markup with no rule able to reach it and the × came out as the browser's default button. Nothing to change; `ds-select` is untouched and `ds-input` keeps its own filled-disc variant (delete list: picker-clear-button-workaround).",
254
+ "A `ds-table` column filter opens on the first click; the first click used to only build the panel. Nothing to change — `filterMode`, `filter: 'set'` and a projected `dsHeaderFilter` all keep their behaviour, and a table with no filterable column renders no panel at all.",
255
+ "A `ds-table` column filter button now carries `aria-expanded` beside its `aria-haspopup=\"dialog\"`, true only on the column whose panel is showing. Nothing to change unless a test of yours asserts the attribute's absence.",
256
+ "A panel re-opened inside the exit animation of a dismissed one can be closed again: the old panel's disposal no longer clears the state of the one that replaced it, which used to leave a panel that neither Escape nor an outside click would dismiss and that reported itself collapsed. Reaches `ds-date-picker`, `ds-color-picker`, `ds-time-picker` and everything `ds-popover` carries — `ds-table`'s filter, row menu and clipped-cell text, `ds-split-button`, `ds-filter-bar`'s overflow panel, `ds-sidenav-footer`'s search. `ds-select`, `ds-autocomplete` and `ds-multi-select` behave exactly as before.",
257
+ "A `ds-table` bulk-action bar now rests `--bulk-bar-offset` above the scroll container's visible bottom edge rather than that offset plus the container's padding. Nothing to change, and `--bulk-bar-offset` keeps its meaning and its default; only a table with row selection inside a padded scroll container looks different.",
258
+ "An expanded `ds-table` row opens with a reveal — its cell interpolates `grid-template-rows` from `0fr` to `1fr` over `--duration-base` at `--ease-standard`, and `prefers-reduced-motion: reduce` shows the panel fully open with no animation. Retune it through those two tokens. The one structural change, a `.expand-panel-inner` wrapper inside the cell, is an item of its own."
259
+ ],
260
+ "deleteList": [
261
+ {
262
+ "id": "table-checkbox-baseline-nudge",
263
+ "surface": "style",
264
+ "find": [
265
+ "ds-table .check",
266
+ "::ng-deep .check"
267
+ ],
268
+ "why": "The table's selection box no longer sits on the text baseline, so a nudge added to lift it off is now an offset in its own right — the header row moves by whatever the nudge was.",
269
+ "replaceWith": "nothing"
270
+ },
271
+ {
272
+ "id": "table-hscroll-bottom-workaround",
273
+ "surface": "style",
274
+ "find": [
275
+ "--ds-table-hscroll-bottom: -"
276
+ ],
277
+ "why": "The table measures its scroll container's bottom padding and cancels it itself, so a negative offset written to do that job moves the sticky scrollbar a second time. The token stays legitimate for a scrollport whose reachable edge is not its padding edge — only the value that duplicates the measurement is dead.",
278
+ "replaceWith": "nothing"
279
+ },
280
+ {
281
+ "id": "picker-clear-button-workaround",
282
+ "surface": "style",
283
+ "find": [
284
+ "ds-autocomplete .clear-btn",
285
+ "ds-multi-select .clear-btn"
286
+ ],
287
+ "why": "Both components render ds-select's clear button themselves now, so a rule written to give that button a border, background, radius or size fights the library's own instead of standing in for it.",
288
+ "replaceWith": "nothing"
289
+ }
290
+ ]
291
+ }
@@ -0,0 +1,83 @@
1
+ {
2
+ "version": "0.12.3",
3
+ "items": [
4
+ {
5
+ "id": "button-ref-renamed-and-widened",
6
+ "kind": "removed-api",
7
+ "surface": "typescript",
8
+ "old": "buttonRef",
9
+ "new": "controlRef",
10
+ "action": "Rename `buttonRef()` to `controlRef()` on every ds-button template reference, and narrow `.nativeElement` yourself where you read a button-only property off it.",
11
+ "appliesWhen": "Only code that reads the reference — a template ref used to position or refocus an overlay, or a component that calls it. Nothing changes for a consumer who only uses the element and its inputs, and the property behind the name is the same view child.",
12
+ "pitfall": "The rename is a compile error and announces itself; the type change may not. `.nativeElement.disabled`, `.form` and `.type` were reachable on `HTMLButtonElement` and are gone from `HTMLElement`, so a read of one fails to compile — but a cast written to silence it then lies at runtime whenever the button carries a destination and really is an anchor.",
13
+ "note": "The element ds-button renders now follows its destination: an `<a>` when `routerLink` or `href` is set, the `<button>` otherwise. One name and one type had to cover all three, so both were wrong before. Overlay triggers pass `.nativeElement` for positioning and focus, which `HTMLElement` answers.",
14
+ "verify": "No `buttonRef` remains anywhere in the consumer tree, and every read of `controlRef().nativeElement` either uses only HTMLElement members or narrows with an `instanceof HTMLButtonElement` check.",
15
+ "searchHints": [
16
+ "buttonRef",
17
+ "buttonRef()",
18
+ ".nativeElement",
19
+ "ds-button"
20
+ ],
21
+ "detect": [
22
+ "buttonRef(",
23
+ "buttonRef().nativeElement",
24
+ "TS2339",
25
+ "Property 'disabled' does not exist"
26
+ ],
27
+ "restore": null
28
+ },
29
+ {
30
+ "id": "exported-class-members-grew",
31
+ "kind": "behavior",
32
+ "surface": "typescript",
33
+ "old": "class MyControl extends CheckboxComponent",
34
+ "new": null,
35
+ "action": "Build after upgrading, then rename or mark `override` any member the compiler reports as colliding.",
36
+ "appliesWhen": "Only a class that extends ButtonComponent, CheckboxComponent, RadioComponent or SwitchComponent. A consumer who uses the elements in a template needs nothing from this item.",
37
+ "pitfall": "Two of the four are not public API, which is no protection: a redeclared private or protected member fails with TS2415 exactly as a public collision does, and a same-named method whose signature differs fails with TS2416 instead.",
38
+ "note": "ButtonComponent gained `routerLink` and `href`, the two destination inputs; `controlRef`, the view child that replaces `buttonRef`; and `destination`, the computed that decides which of the three elements renders. It also LOST `buttonRef`, so a subclass that overrode that one now overrides nothing and its member is dead rather than broken. CheckboxComponent, RadioComponent and SwitchComponent each gained `ariaLabel` and `resolvedAriaLabel`.",
39
+ "verify": "The app builds with no TS2415 or TS2416 naming ButtonComponent, CheckboxComponent, RadioComponent or SwitchComponent, and no member of your subclass is called routerLink, href, controlRef, destination, ariaLabel or resolvedAriaLabel.",
40
+ "searchHints": [
41
+ "extends ButtonComponent",
42
+ "extends CheckboxComponent",
43
+ "extends RadioComponent",
44
+ "extends SwitchComponent",
45
+ "routerLink",
46
+ "href",
47
+ "controlRef",
48
+ "destination",
49
+ "ariaLabel",
50
+ "TS2415",
51
+ "TS2416"
52
+ ],
53
+ "detect": [
54
+ "extends ButtonComponent",
55
+ "extends CheckboxComponent",
56
+ "extends RadioComponent",
57
+ "extends SwitchComponent",
58
+ "override routerLink",
59
+ "override href",
60
+ "override controlRef",
61
+ "override destination",
62
+ "override buttonRef",
63
+ "override ariaLabel",
64
+ "override resolvedAriaLabel"
65
+ ],
66
+ "restore": null
67
+ }
68
+ ],
69
+ "informational": [
70
+ "`ds-button` takes two new optional inputs, `routerLink` and `href`. Unset, which is the default and what every existing button has, it renders the same `<button type=\"button\">` as before. Set either and it renders an `<a>` instead, with identical styling — the rules are class-based, so nothing keyed to `.button` moves. `type` and `loading` are ignored on a link and say so in dev mode.",
71
+ "A `ds-multi-select` panel filter row now carries `--ds-radius-inner`, so its focus ring is rounded instead of a full-width rectangle. Nothing to change — an `outline` follows the radius of the box it is drawn on, and that row simply had none.",
72
+ "A focus ring is now shaped by its host: the new `--focus-ring-radius` token gives a box that exists only to carry the ring a radius, because an outline follows the `border-radius` of the box it is drawn on and has none of its own. It follows `--ds-radius-inner`, 4px, so a theme that retunes the inner radius moves these rings with it. `ds-checkbox`, `ds-radio` and `ds-switch` pick it up, so their keyboard focus ring is rounded instead of square. Nothing to change — the resting state of all three is untouched, and a host with its own radius keeps it.",
73
+ "A clickable `ds-table` row, a `ds-tree` row and a `ds-list` activator now carry `--focus-ring-radius`, so their keyboard focus ring is rounded instead of square. Nothing to change: none of the three paints a background of its own, so the radius shapes only the ring, and their resting appearance is unchanged.",
74
+ "A field marked `disabled` no longer paints its `data-field-state`. An `error`, `warning` or `success` state used to out-rank the disabled look in `ds-input`, `ds-textarea`, `ds-select`, `ds-multi-select`, `ds-autocomplete`, `ds-date-picker`, `ds-time-picker`, `ds-color-picker` and `ds-otp-input`, on specificity alone, so a field left invalid and then disabled kept a red border and fill it could not act on. Nothing to change — `data-field-state` is set the same way and means the same thing, and a read-only field still paints it, because `readonly` is submitted where `disabled` is not.",
75
+ "`ds-field-group[invalid]` keeps its error border while hovered and while holding focus. Both `:hover` and `:focus-within` used to out-rank `.invalid` on specificity and repaint the border, which is the group's only error affordance because a segment's own label and message are hidden. Its focus halo now takes the error tint, through the new `--ds-field-group-focus-shadow-error` (default `--ds-field-focus-shadow-error`). Nothing to change — a valid group hovers and focuses as before, and a stylesheet that set `--ds-field-group-focus-shadow` still gets it on the valid state.",
76
+ "`ds-stat variant=\"error\"` now actually recolours the value. `:host(.error) .value` tied `.stat .value` on specificity and lost on source order, so the variant painted nothing; error now moves the `--_stat-value-color` resolver. Nothing to change, and a stylesheet setting `--ds-stat-value-color` still wins over it, exactly as before.",
77
+ "`ds-breadcrumbs`: `BreadcrumbItem` takes an optional `ariaLabel`, and a crumb with an `icon` and no `label` needs it: that shape rendered a link with no accessible name. Add `ariaLabel` to any icon-only crumb — the usual home crumb — and the component dev-warns while one is missing. Nothing derives from `icon`, because a glyph id is not a word for the user.",
78
+ "`ds-sidenav-footer`'s collapse button carries an `aria-label`, and its label reads `Expand` while the rail is collapsed rather than always `Collapse`. Nothing to change; a stylesheet that keyed off the text content of `.row .label` is the one exception, and none is expected.",
79
+ "`--focus-ring` is a two-shadow LIST for `box-shadow`, not a value for `outline` — worth knowing because putting it in an `outline` fails silently and takes the ring with it. A `var()` that cannot substitute is invalid at computed-value time, so the property computes back to its initial value instead of being dropped, and it still out-ranks the library's own `:where(:focus-visible)` ring by specificity: the element ends up with no indicator at all. For an outline use `--focus-ring-width`, `--focus-ring-color` and `--focus-ring-offset`, or just let the global ring do it. Nothing in the package was affected; this is the shape to avoid in consumer stylesheets.",
80
+ "`ds-checkbox`, `ds-radio` and `ds-switch` take an optional `ariaLabel`, for the case where the control renders no visible label — no `label` and nothing projected. Until now such a control had no accessible name and no way to be given one; `ds-select` and `ds-number-stepper` already took the same input. Nothing to change unless you have a label-less one, and setting it ALONGSIDE a label overrides what the label says, which is the ARIA rule and rarely what you want."
81
+ ],
82
+ "deleteList": []
83
+ }
package/package.json CHANGED
@@ -1,6 +1,6 @@
1
1
  {
2
2
  "name": "@ids-group-ltd/ids-design-system",
3
- "version": "0.12.1",
3
+ "version": "0.12.3",
4
4
  "description": "IDS Group Angular design system: components, tokens, themes",
5
5
  "license": "MIT",
6
6
  "homepage": "https://ids-ds.proto.ids-group.co.uk/",
@@ -38,6 +38,13 @@
38
38
  cursor: pointer;
39
39
  display: inline-grid;
40
40
  place-items: center;
41
+
42
+ /* Inline-level, so without this the box sits on the text baseline — and the baseline of an
43
+ inline-grid is its first item's, which moves when the mark swaps between the 12px tick and the
44
+ 10x2 bar. Measured in ds-table: the header row was 45.50px with the box indeterminate and
45
+ 45.30px with it checked, a 0.2px twitch on every selection change. `middle` takes the box off
46
+ the baseline entirely. ds-checkbox never showed it — there the input is a flex item. */
47
+ vertical-align: middle;
41
48
  flex-shrink: 0;
42
49
  margin: 0;
43
50
  border-radius: var(--_checkbox-radius, var(--ds-checkbox-radius, var(--ds-radius-inner)));
@@ -0,0 +1,28 @@
1
+ @use 'press' as press;
2
+
3
+ // The `×` that clears a trigger-shaped field — ds-select, ds-autocomplete, ds-multi-select all
4
+ // render the same `.clear-btn` markup behind `clearable`. Shared because two of the three had the
5
+ // markup and no rule, so the button came out as the browser's default: include it inside whichever
6
+ // selector holds the trigger's own layout.
7
+ //
8
+ // ds-input's clear button is deliberately NOT this one — it paints a filled disc so the glyph
9
+ // still reads on a blurred field, and keeps its rule with the input.
10
+ @mixin button {
11
+ border: 0;
12
+ background: transparent;
13
+ display: inline-flex;
14
+ align-items: center;
15
+ justify-content: center;
16
+ color: var(--icon-default);
17
+ border-radius: var(--ds-radius-inner);
18
+ padding: var(--space-0-5);
19
+ cursor: pointer;
20
+ flex: 0 0 auto;
21
+
22
+ &:hover {
23
+ color: var(--text-primary);
24
+ background: var(--surface-secondary);
25
+ }
26
+
27
+ @include press.feedback;
28
+ }
@@ -0,0 +1,45 @@
1
+ @use 'focus' as focus;
2
+ @use 'control-label' as control-label;
3
+
4
+ // The ring goes on the ROW and $control's own is suppressed: a checked box already draws a brand
5
+ // box, so a ring around the glyph lands concentric with it and reads as a target rather than as two
6
+ // states. ds-table adds its own ring because it has no row to speak for it.
7
+ @mixin line($control, $label-font, $label-color) {
8
+ @include focus.ring-for($control);
9
+
10
+ // The row paints nothing, so this shapes the ring and nothing else.
11
+ border-radius: var(--focus-ring-radius);
12
+
13
+ // No label: the row IS the glyph, so the concentric read comes back and the ring stands off.
14
+ &:has(.control-text:empty) {
15
+ --focus-ring-offset: var(--space-1-5);
16
+ }
17
+
18
+ display: inline-flex;
19
+ align-items: center;
20
+
21
+ .control-text {
22
+ @include control-label.hit-area;
23
+
24
+ font: $label-font;
25
+ color: $label-color;
26
+ cursor: pointer;
27
+ user-select: none;
28
+
29
+ /* Collapse, or the empty caption still takes the row gap and offsets the control. */
30
+ &:empty {
31
+ display: none;
32
+ }
33
+
34
+ .req {
35
+ color: var(--error);
36
+ font-weight: var(--font-weight-semibold);
37
+ margin-inline-start: var(--space-1);
38
+ }
39
+ }
40
+
41
+ &.is-disabled .control-text {
42
+ color: var(--text-disabled);
43
+ cursor: not-allowed;
44
+ }
45
+ }
@@ -1,11 +1,10 @@
1
- // Keyed off `data-field-state` on the host, which each field binds from
2
- // `resolveFieldMessage`'s `controlState`. Only error carries a fill: a warning or
3
- // success tint measures 1.05:1 against a white field, too faint to do the
4
- // findability job a fill exists for, so neither carries one.
1
+ // Keyed off `data-field-state` on the host. Only error carries a fill: a warning or success tint
2
+ // measures 1.05:1 against a white field, too faint to be findable.
5
3
  //
6
- // The colour arguments exist so a component can pass its own `--ds-<name>-*-error`
7
- // resolver: hardcoding the family token here would silently drop overrides
8
- // published since 0.7.x.
4
+ // Disabled takes no state paint — it is neither submitted nor validated, so an error border
5
+ // promises a correction that cannot be made. Read-only keeps it, because it IS submitted.
6
+ //
7
+ // The colour arguments let a component pass its own `--ds-<name>-*-error` resolver.
9
8
  @mixin field-state(
10
9
  $box,
11
10
  $error-border: var(--error),
@@ -14,9 +13,10 @@
14
13
  $warning-border: var(--warning-text),
15
14
  $success-border: var(--success)
16
15
  ) {
17
- // `:not(.in-group)` on all three: a segment ties `.in-group` at (0,3,0) and this
18
- // mixin is included last, so without it the fill repaints one segment mid-row.
19
- :host([data-field-state='error']:not(.in-group)) #{$box} {
16
+ // `:not(.in-group)`: a segment ties `.in-group` at (0,3,0) and this mixin is included last, so
17
+ // without it the fill repaints one segment mid-row. `:not(.disabled)`: state is (0,3,0) against
18
+ // (0,2,0), so it out-ranks every disabled rule unless it stops matching.
19
+ :host([data-field-state='error']:not(.in-group)) #{$box}:not(.disabled):not(:disabled) {
20
20
  border-color: #{$error-border};
21
21
  background-color: #{$error-bg};
22
22
 
@@ -26,14 +26,13 @@
26
26
  }
27
27
  }
28
28
 
29
- // --warning is yellow-400, 1.47:1 against a white field — invisible as a
30
- // boundary, where WCAG 1.4.11 asks 3:1. --warning-text (yellow-700) is the
31
- // first rung of the ramp that clears it, at 4.59:1.
32
- :host([data-field-state='warning']:not(.in-group)) #{$box} {
29
+ // --warning is 1.47:1 against a white field, where WCAG 1.4.11 asks 3:1 for a boundary.
30
+ // --warning-text is the first rung of the ramp that clears it, at 4.59:1.
31
+ :host([data-field-state='warning']:not(.in-group)) #{$box}:not(.disabled):not(:disabled) {
33
32
  border-color: #{$warning-border};
34
33
  }
35
34
 
36
- :host([data-field-state='success']:not(.in-group)) #{$box} {
35
+ :host([data-field-state='success']:not(.in-group)) #{$box}:not(.disabled):not(:disabled) {
37
36
  border-color: #{$success-border};
38
37
  }
39
38
  }