@ids-group-ltd/ids-design-system 1.1.2 → 1.2.0

This diff represents the content of publicly available package versions that have been released to one of the supported registries. The information contained in this diff is provided for informational purposes only and reflects changes between package versions as they appear in their respective public registries.
Files changed (221) hide show
  1. package/CHANGELOG.md +755 -0
  2. package/agent/INDEX.md +8 -7
  3. package/agent/charts/ds-scatter-chart.md +1 -1
  4. package/agent/feedback/ds-badge.md +2 -2
  5. package/agent/feedback/ds-chat-message.md +1 -1
  6. package/agent/feedback/ds-chat-step.md +2 -2
  7. package/agent/feedback/ds-chat-thread.md +1 -1
  8. package/agent/feedback/ds-stat.md +1 -1
  9. package/agent/feedback/ds-toast.md +2 -2
  10. package/agent/feedback/ds-tree.md +1 -1
  11. package/agent/forms/ds-button.md +3 -3
  12. package/agent/forms/ds-dropzone.md +1 -1
  13. package/agent/forms/ds-icon-button.md +3 -3
  14. package/agent/forms/ds-number-stepper.md +3 -3
  15. package/agent/forms/ds-search.md +1 -1
  16. package/agent/forms/ds-split-button.md +1 -1
  17. package/agent/foundations/tokens.md +4 -3
  18. package/agent/navigation/ds-app-layout.md +1 -1
  19. package/agent/navigation/ds-nav-divider.md +6 -0
  20. package/agent/navigation/{ds-sidenav-footer.md → ds-nav-footer.md} +3 -3
  21. package/agent/navigation/{ds-sidenav-group.md → ds-nav-group.md} +2 -2
  22. package/agent/navigation/{ds-sidenav-item.md → ds-nav-item.md} +6 -6
  23. package/agent/navigation/ds-nav.md +15 -0
  24. package/agent/overlays/ds-drawer.md +1 -1
  25. package/agent/platform/toast-service.md +1 -1
  26. package/components/README.md +24 -24
  27. package/components.md +51 -45
  28. package/design-system.md +8 -7
  29. package/eslint/deprecated-api.json +108 -7
  30. package/fesm2022/ids-group-ltd-ids-design-system-components-accordion.mjs +2 -2
  31. package/fesm2022/ids-group-ltd-ids-design-system-components-accordion.mjs.map +1 -1
  32. package/fesm2022/ids-group-ltd-ids-design-system-components-alert.mjs +2 -2
  33. package/fesm2022/ids-group-ltd-ids-design-system-components-alert.mjs.map +1 -1
  34. package/fesm2022/ids-group-ltd-ids-design-system-components-app-layout.mjs +4 -4
  35. package/fesm2022/ids-group-ltd-ids-design-system-components-app-layout.mjs.map +1 -1
  36. package/fesm2022/ids-group-ltd-ids-design-system-components-auth-layout.mjs +4 -4
  37. package/fesm2022/ids-group-ltd-ids-design-system-components-auth-layout.mjs.map +1 -1
  38. package/fesm2022/ids-group-ltd-ids-design-system-components-autocomplete.mjs +2 -2
  39. package/fesm2022/ids-group-ltd-ids-design-system-components-autocomplete.mjs.map +1 -1
  40. package/fesm2022/ids-group-ltd-ids-design-system-components-avatar.mjs +2 -2
  41. package/fesm2022/ids-group-ltd-ids-design-system-components-avatar.mjs.map +1 -1
  42. package/fesm2022/ids-group-ltd-ids-design-system-components-badge-badge-count-roll.component-BDNXADJZ.mjs +182 -0
  43. package/fesm2022/ids-group-ltd-ids-design-system-components-badge-badge-count-roll.component-BDNXADJZ.mjs.map +1 -0
  44. package/fesm2022/ids-group-ltd-ids-design-system-components-badge.mjs +37 -8
  45. package/fesm2022/ids-group-ltd-ids-design-system-components-badge.mjs.map +1 -1
  46. package/fesm2022/ids-group-ltd-ids-design-system-components-banner.mjs +2 -2
  47. package/fesm2022/ids-group-ltd-ids-design-system-components-banner.mjs.map +1 -1
  48. package/fesm2022/ids-group-ltd-ids-design-system-components-breadcrumbs.mjs +5 -2
  49. package/fesm2022/ids-group-ltd-ids-design-system-components-breadcrumbs.mjs.map +1 -1
  50. package/fesm2022/ids-group-ltd-ids-design-system-components-button-group.mjs +2 -2
  51. package/fesm2022/ids-group-ltd-ids-design-system-components-button-group.mjs.map +1 -1
  52. package/fesm2022/ids-group-ltd-ids-design-system-components-button.mjs +76 -5
  53. package/fesm2022/ids-group-ltd-ids-design-system-components-button.mjs.map +1 -1
  54. package/fesm2022/ids-group-ltd-ids-design-system-components-calendar-day.mjs +2 -2
  55. package/fesm2022/ids-group-ltd-ids-design-system-components-chart-legend.mjs +2 -2
  56. package/fesm2022/ids-group-ltd-ids-design-system-components-chart-legend.mjs.map +1 -1
  57. package/fesm2022/ids-group-ltd-ids-design-system-components-chart-tooltip.mjs +2 -2
  58. package/fesm2022/ids-group-ltd-ids-design-system-components-chart-tooltip.mjs.map +1 -1
  59. package/fesm2022/ids-group-ltd-ids-design-system-components-chat.mjs +77 -18
  60. package/fesm2022/ids-group-ltd-ids-design-system-components-chat.mjs.map +1 -1
  61. package/fesm2022/ids-group-ltd-ids-design-system-components-checkbox.mjs +2 -2
  62. package/fesm2022/ids-group-ltd-ids-design-system-components-checkbox.mjs.map +1 -1
  63. package/fesm2022/ids-group-ltd-ids-design-system-components-color-picker.mjs +2 -2
  64. package/fesm2022/ids-group-ltd-ids-design-system-components-color-picker.mjs.map +1 -1
  65. package/fesm2022/ids-group-ltd-ids-design-system-components-date-picker.mjs +2 -2
  66. package/fesm2022/ids-group-ltd-ids-design-system-components-date-picker.mjs.map +1 -1
  67. package/fesm2022/ids-group-ltd-ids-design-system-components-definition-term.mjs +2 -2
  68. package/fesm2022/ids-group-ltd-ids-design-system-components-definition-term.mjs.map +1 -1
  69. package/fesm2022/ids-group-ltd-ids-design-system-components-description-list.mjs +2 -2
  70. package/fesm2022/ids-group-ltd-ids-design-system-components-description-list.mjs.map +1 -1
  71. package/fesm2022/ids-group-ltd-ids-design-system-components-drawer.mjs +65 -4
  72. package/fesm2022/ids-group-ltd-ids-design-system-components-drawer.mjs.map +1 -1
  73. package/fesm2022/ids-group-ltd-ids-design-system-components-dropzone.mjs +76 -9
  74. package/fesm2022/ids-group-ltd-ids-design-system-components-dropzone.mjs.map +1 -1
  75. package/fesm2022/ids-group-ltd-ids-design-system-components-field-group.mjs +2 -2
  76. package/fesm2022/ids-group-ltd-ids-design-system-components-field-group.mjs.map +1 -1
  77. package/fesm2022/ids-group-ltd-ids-design-system-components-funnel-chart.mjs +2 -2
  78. package/fesm2022/ids-group-ltd-ids-design-system-components-heatmap-chart.mjs +2 -2
  79. package/fesm2022/ids-group-ltd-ids-design-system-components-heatmap-chart.mjs.map +1 -1
  80. package/fesm2022/ids-group-ltd-ids-design-system-components-icon-button.mjs +6 -4
  81. package/fesm2022/ids-group-ltd-ids-design-system-components-icon-button.mjs.map +1 -1
  82. package/fesm2022/ids-group-ltd-ids-design-system-components-info-hint.mjs +2 -2
  83. package/fesm2022/ids-group-ltd-ids-design-system-components-info-hint.mjs.map +1 -1
  84. package/fesm2022/ids-group-ltd-ids-design-system-components-inline-edit.mjs +2 -2
  85. package/fesm2022/ids-group-ltd-ids-design-system-components-inline-edit.mjs.map +1 -1
  86. package/fesm2022/ids-group-ltd-ids-design-system-components-input.mjs +2 -2
  87. package/fesm2022/ids-group-ltd-ids-design-system-components-input.mjs.map +1 -1
  88. package/fesm2022/ids-group-ltd-ids-design-system-components-list.mjs +2 -2
  89. package/fesm2022/ids-group-ltd-ids-design-system-components-menu.mjs +4 -4
  90. package/fesm2022/ids-group-ltd-ids-design-system-components-menu.mjs.map +1 -1
  91. package/fesm2022/ids-group-ltd-ids-design-system-components-modal.mjs +2 -2
  92. package/fesm2022/ids-group-ltd-ids-design-system-components-modal.mjs.map +1 -1
  93. package/fesm2022/ids-group-ltd-ids-design-system-components-multi-select.mjs +2 -2
  94. package/fesm2022/ids-group-ltd-ids-design-system-components-multi-select.mjs.map +1 -1
  95. package/fesm2022/ids-group-ltd-ids-design-system-components-nav-footer.mjs +113 -0
  96. package/fesm2022/ids-group-ltd-ids-design-system-components-nav-footer.mjs.map +1 -0
  97. package/fesm2022/ids-group-ltd-ids-design-system-components-nav.mjs +228 -0
  98. package/fesm2022/ids-group-ltd-ids-design-system-components-nav.mjs.map +1 -0
  99. package/fesm2022/ids-group-ltd-ids-design-system-components-number-stepper.mjs +61 -10
  100. package/fesm2022/ids-group-ltd-ids-design-system-components-number-stepper.mjs.map +1 -1
  101. package/fesm2022/ids-group-ltd-ids-design-system-components-otp-input.mjs +2 -2
  102. package/fesm2022/ids-group-ltd-ids-design-system-components-otp-input.mjs.map +1 -1
  103. package/fesm2022/ids-group-ltd-ids-design-system-components-pagination.mjs +36 -4
  104. package/fesm2022/ids-group-ltd-ids-design-system-components-pagination.mjs.map +1 -1
  105. package/fesm2022/ids-group-ltd-ids-design-system-components-pie-chart.mjs +2 -2
  106. package/fesm2022/ids-group-ltd-ids-design-system-components-radio-group.mjs +2 -2
  107. package/fesm2022/ids-group-ltd-ids-design-system-components-radio-group.mjs.map +1 -1
  108. package/fesm2022/ids-group-ltd-ids-design-system-components-reveal.mjs +56 -0
  109. package/fesm2022/ids-group-ltd-ids-design-system-components-reveal.mjs.map +1 -0
  110. package/fesm2022/ids-group-ltd-ids-design-system-components-scatter-chart.mjs +10 -39
  111. package/fesm2022/ids-group-ltd-ids-design-system-components-scatter-chart.mjs.map +1 -1
  112. package/fesm2022/ids-group-ltd-ids-design-system-components-search.mjs +7 -4
  113. package/fesm2022/ids-group-ltd-ids-design-system-components-search.mjs.map +1 -1
  114. package/fesm2022/ids-group-ltd-ids-design-system-components-segmented.mjs +33 -6
  115. package/fesm2022/ids-group-ltd-ids-design-system-components-segmented.mjs.map +1 -1
  116. package/fesm2022/ids-group-ltd-ids-design-system-components-select.mjs +2 -2
  117. package/fesm2022/ids-group-ltd-ids-design-system-components-select.mjs.map +1 -1
  118. package/fesm2022/ids-group-ltd-ids-design-system-components-sidenav-footer.mjs +4 -98
  119. package/fesm2022/ids-group-ltd-ids-design-system-components-sidenav-footer.mjs.map +1 -1
  120. package/fesm2022/ids-group-ltd-ids-design-system-components-sidenav.mjs +11 -179
  121. package/fesm2022/ids-group-ltd-ids-design-system-components-sidenav.mjs.map +1 -1
  122. package/fesm2022/ids-group-ltd-ids-design-system-components-skeleton.mjs +2 -2
  123. package/fesm2022/ids-group-ltd-ids-design-system-components-skeleton.mjs.map +1 -1
  124. package/fesm2022/ids-group-ltd-ids-design-system-components-slider.mjs +2 -2
  125. package/fesm2022/ids-group-ltd-ids-design-system-components-slider.mjs.map +1 -1
  126. package/fesm2022/ids-group-ltd-ids-design-system-components-split-button.mjs +3 -2
  127. package/fesm2022/ids-group-ltd-ids-design-system-components-split-button.mjs.map +1 -1
  128. package/fesm2022/ids-group-ltd-ids-design-system-components-stat.mjs +68 -5
  129. package/fesm2022/ids-group-ltd-ids-design-system-components-stat.mjs.map +1 -1
  130. package/fesm2022/ids-group-ltd-ids-design-system-components-stepper.mjs +2 -2
  131. package/fesm2022/ids-group-ltd-ids-design-system-components-stepper.mjs.map +1 -1
  132. package/fesm2022/ids-group-ltd-ids-design-system-components-switch.mjs +2 -2
  133. package/fesm2022/ids-group-ltd-ids-design-system-components-switch.mjs.map +1 -1
  134. package/fesm2022/ids-group-ltd-ids-design-system-components-table-columns.mjs +2 -2
  135. package/fesm2022/ids-group-ltd-ids-design-system-components-table-columns.mjs.map +1 -1
  136. package/fesm2022/ids-group-ltd-ids-design-system-components-table.mjs +2 -2
  137. package/fesm2022/ids-group-ltd-ids-design-system-components-table.mjs.map +1 -1
  138. package/fesm2022/ids-group-ltd-ids-design-system-components-tabs.mjs +41 -3
  139. package/fesm2022/ids-group-ltd-ids-design-system-components-tabs.mjs.map +1 -1
  140. package/fesm2022/ids-group-ltd-ids-design-system-components-tag.mjs +2 -2
  141. package/fesm2022/ids-group-ltd-ids-design-system-components-tag.mjs.map +1 -1
  142. package/fesm2022/ids-group-ltd-ids-design-system-components-textarea.mjs +6 -4
  143. package/fesm2022/ids-group-ltd-ids-design-system-components-textarea.mjs.map +1 -1
  144. package/fesm2022/ids-group-ltd-ids-design-system-components-time-picker.mjs +4 -4
  145. package/fesm2022/ids-group-ltd-ids-design-system-components-time-picker.mjs.map +1 -1
  146. package/fesm2022/ids-group-ltd-ids-design-system-components-timeline.mjs +27 -7
  147. package/fesm2022/ids-group-ltd-ids-design-system-components-timeline.mjs.map +1 -1
  148. package/fesm2022/ids-group-ltd-ids-design-system-components-toast.mjs +54 -19
  149. package/fesm2022/ids-group-ltd-ids-design-system-components-toast.mjs.map +1 -1
  150. package/fesm2022/ids-group-ltd-ids-design-system-components-toggle-button.mjs +2 -2
  151. package/fesm2022/ids-group-ltd-ids-design-system-components-toggle-button.mjs.map +1 -1
  152. package/fesm2022/ids-group-ltd-ids-design-system-components-tooltip.mjs +8 -7
  153. package/fesm2022/ids-group-ltd-ids-design-system-components-tooltip.mjs.map +1 -1
  154. package/fesm2022/ids-group-ltd-ids-design-system-components-tree.mjs +21 -11
  155. package/fesm2022/ids-group-ltd-ids-design-system-components-tree.mjs.map +1 -1
  156. package/fesm2022/ids-group-ltd-ids-design-system-components-w3w.mjs +2 -2
  157. package/fesm2022/ids-group-ltd-ids-design-system-components-w3w.mjs.map +1 -1
  158. package/fesm2022/ids-group-ltd-ids-design-system-components.mjs +153 -1
  159. package/fesm2022/ids-group-ltd-ids-design-system-components.mjs.map +1 -1
  160. package/fesm2022/ids-group-ltd-ids-design-system-core.mjs +11 -0
  161. package/fesm2022/ids-group-ltd-ids-design-system-core.mjs.map +1 -1
  162. package/fesm2022/ids-group-ltd-ids-design-system.mjs +4 -1
  163. package/fesm2022/ids-group-ltd-ids-design-system.mjs.map +1 -1
  164. package/migrations/1.1.1.json +14 -4
  165. package/migrations/1.1.2.json +11 -3
  166. package/migrations/1.2.0.json +1433 -0
  167. package/migrations/README.md +8 -1
  168. package/package.json +25 -1
  169. package/schematics/check-overrides/index.cjs +28 -3
  170. package/schematics/check-overrides/scan.cjs +151 -2
  171. package/schematics/check-overrides/schema.json +4 -0
  172. package/schematics/check-overrides/surface.json +389 -74
  173. package/schematics/collection.json +1 -1
  174. package/stylelint/deprecated-tokens.json +7 -0
  175. package/styles/_check-box.scss +4 -3
  176. package/styles/_dropdown-overlay.scss +6 -8
  177. package/styles/_ds-color.scss +7 -2
  178. package/styles/_field-state.scss +4 -2
  179. package/styles/_focus.scss +12 -5
  180. package/styles/_link.scss +4 -4
  181. package/styles/_optical-center.scss +29 -0
  182. package/styles/_reveal.scss +8 -0
  183. package/styles/_status.scss +17 -7
  184. package/styles/_step-marker.scss +192 -6
  185. package/styles/_surface-level.scss +16 -0
  186. package/styles/_text-shimmer.scss +21 -0
  187. package/styles/_theme-activation.scss +17 -4
  188. package/styles/_tokens.scss +26 -7
  189. package/styles/ds.scss +1 -0
  190. package/themes/README.md +16 -21
  191. package/themes/_semantic.scss +129 -64
  192. package/themes/dark/_theme.scss +17 -25
  193. package/types/ids-group-ltd-ids-design-system-components-app-layout.d.ts +3 -3
  194. package/types/ids-group-ltd-ids-design-system-components-auth-layout.d.ts +2 -2
  195. package/types/ids-group-ltd-ids-design-system-components-badge.d.ts +20 -1
  196. package/types/ids-group-ltd-ids-design-system-components-button.d.ts +14 -3
  197. package/types/ids-group-ltd-ids-design-system-components-chat.d.ts +49 -4
  198. package/types/ids-group-ltd-ids-design-system-components-drawer.d.ts +9 -1
  199. package/types/ids-group-ltd-ids-design-system-components-dropzone.d.ts +28 -2
  200. package/types/ids-group-ltd-ids-design-system-components-icon-button.d.ts +8 -5
  201. package/types/ids-group-ltd-ids-design-system-components-nav-footer.d.ts +88 -0
  202. package/types/ids-group-ltd-ids-design-system-components-nav.d.ts +152 -0
  203. package/types/ids-group-ltd-ids-design-system-components-number-stepper.d.ts +21 -3
  204. package/types/ids-group-ltd-ids-design-system-components-pagination.d.ts +1 -0
  205. package/types/ids-group-ltd-ids-design-system-components-reveal.d.ts +31 -0
  206. package/types/ids-group-ltd-ids-design-system-components-scatter-chart.d.ts +2 -8
  207. package/types/ids-group-ltd-ids-design-system-components-search.d.ts +4 -1
  208. package/types/ids-group-ltd-ids-design-system-components-segmented.d.ts +3 -0
  209. package/types/ids-group-ltd-ids-design-system-components-sidenav-footer.d.ts +12 -83
  210. package/types/ids-group-ltd-ids-design-system-components-sidenav.d.ts +21 -131
  211. package/types/ids-group-ltd-ids-design-system-components-split-button.d.ts +1 -1
  212. package/types/ids-group-ltd-ids-design-system-components-stat.d.ts +10 -1
  213. package/types/ids-group-ltd-ids-design-system-components-tabs.d.ts +1 -0
  214. package/types/ids-group-ltd-ids-design-system-components-textarea.d.ts +1 -1
  215. package/types/ids-group-ltd-ids-design-system-components-timeline.d.ts +3 -1
  216. package/types/ids-group-ltd-ids-design-system-components-toast.d.ts +27 -6
  217. package/types/ids-group-ltd-ids-design-system-components-tree.d.ts +9 -5
  218. package/types/ids-group-ltd-ids-design-system-components.d.ts +26 -1
  219. package/types/ids-group-ltd-ids-design-system-core.d.ts +19 -1
  220. package/types/ids-group-ltd-ids-design-system.d.ts +7 -4
  221. package/agent/navigation/ds-sidenav.md +0 -13
package/CHANGELOG.md CHANGED
@@ -1,5 +1,760 @@
1
1
  ## Unreleased
2
2
 
3
+ ## 1.2.0 — 2026-11-17
4
+
5
+ ### Added
6
+
7
+ - **`dsReveal` fades the items of a list in one after another.** Put it on each item with
8
+ `[dsRevealIndex]="$index"`: an item fades in over `--duration-base` with `--ease-standard` as it is
9
+ created, `--stagger-step` (40ms) after the item before it, and items past `--stagger-max` (7)
10
+ start with the last one. Only the value of `dsReveal` when the item is created counts, so bind
11
+ `false` once the list has filled in and an item added later appears at once. Under
12
+ `prefers-reduced-motion: reduce` and on the server it does nothing. `RevealDirective` is exported
13
+ from the package root and `@ids-group-ltd/ids-design-system/components/reveal`; `--stagger-step`
14
+ and `--stagger-max` are new tokens. The directive writes the item's index to `--ds-reveal-index`
15
+ on the item while it fades in; a value set there by hand is overwritten.
16
+ - **A toast takes a second action, an icon button, with `iconAction`.** `ToastService.show()` and
17
+ `ds-toast` accept `iconAction: { icon, label, handler, keepOpen?, successLabel? }`
18
+ (`ToastIconAction`, exported from the package root). It draws as an 18×18 button with a 14 px icon
19
+ between the text `action` and the close button, the same size as the close button; `label` is its
20
+ accessible name and its tooltip. Pressing it runs `handler` and closes the toast, unless
21
+ `keepOpen` is set. With `successLabel` the toast stays and the button confirms in place: once
22
+ `handler` has finished (a promise it returns has resolved; a rejected one shows nothing) the icon
23
+ fades out over `--duration-fast`, a `--success-text` check grows in from 80% over
24
+ `--duration-base`, and after 1.2 s they swap back; `successLabel` is announced through a polite
25
+ live region. Under `prefers-reduced-motion: reduce` the icons swap at once. Tab order is the text
26
+ action, the icon action, the close button. A toast with an `iconAction` never auto-dismisses and
27
+ is always dismissible, as one with an `action` is.
28
+ - **`ds-drawer` leaves the scrim clear over one element, with `scrimCutout`.** Bind an element
29
+ and the scrim draws around it, so the item the drawer is about stays at full brightness; the hole
30
+ takes the element's corner radius and follows it through resize and scroll. A `DOMRect` in
31
+ viewport coordinates makes a fixed, square-cornered hole. A click on the hole closes the drawer
32
+ like any other scrim click. A hole that moves to another element jumps there at once. A target
33
+ cleared as the drawer closes keeps its hole until the scrim has faded out. Without `scrimCutout`
34
+ the scrim draws as before.
35
+ - **`ds-nav` is the vertical menu, for the application's side menu and for a section menu in a
36
+ page.** `ds-nav`, `ds-nav-group`, `ds-nav-item` and `ds-nav-footer` are `ds-sidenav`,
37
+ `ds-sidenav-group`, `ds-sidenav-item` and `ds-sidenav-footer` under new names, with the same
38
+ inputs, outputs and slots. `NavComponent`, `NavGroupComponent`, `NavItemComponent`,
39
+ `NavFooterComponent`, `NAV`, `NavContract`, `NavItemModel`, `NavAlertItem`, `NavSearchProvider`
40
+ and `NavSearchResult` are exported from the package root,
41
+ `@ids-group-ltd/ids-design-system/components/nav` and
42
+ `@ids-group-ltd/ids-design-system/components/nav-footer`. The hooks are `--ds-nav-*`, and
43
+ `ds-app-layout` takes the menu in a `[nav]` slot.
44
+ - **`ds-nav` takes a `label`, which makes it a named navigation landmark.** With `label` set the
45
+ host carries `role="navigation"` and that `aria-label`; give each menu its own when a page has
46
+ more than one. Unset, the host carries no role, as before.
47
+ - **`ds-nav-divider` draws a line between the items or groups of a `ds-nav`.** The component,
48
+ `NavDividerComponent`, carries `role="separator"` and takes its colour from
49
+ `--ds-nav-divider-color`, `--border-divider` by default.
50
+ - **`ds-nav-item` shows a short text at its end, with `trailingText`.** It is for a status or a
51
+ shortcut that is not a count, and sits before the badge; `badge` stays for numbers. It hides
52
+ while the rail is collapsed.
53
+ - **A vertical `ds-tabs` with more than 7 tabs warns in the console in development.** Past 7 the
54
+ strip is a menu: use `ds-nav`, with groups for the sections.
55
+ - **`ds-nav` sets a section menu inside a page, with `variant="page"`.** The menu draws as a card: a
56
+ border on all four sides with `--radius-lg`, `--space-2` inside, rows `--hit-min` high with
57
+ `--space-1-5` `--space-2-5` padding and `--space-0-5` between them, items in line with their group
58
+ heading, group headings closer to their items and a line between groups. An item with no icon
59
+ takes no icon room. The brand row does not show, even with `DS_CONFIG.brand` set. Without
60
+ `variant` the menu draws as before. A page that holds it next to the application's menu gives each
61
+ menu its own `label`.
62
+ - **`ds-chat-step` holds the way out of a failed step, in an `[actions]` slot and with
63
+ `retryable`.** Buttons projected with `actions` sit in a row under the `[details]`, inside the
64
+ open card with `--space-3` to its bottom edge, and the chevron shows for them as it does for
65
+ details. `retryable` on a step with `status="error"` ends the row in an outline Retry button that
66
+ emits `retry`; its label is the new `DsIntl` key `chat.stepRetry`, `'Retry'` by default. A step
67
+ with neither draws as before.
68
+ - **`ds-stat` counts to a new value, with `animateValue`.** When a numeric `value` changes to
69
+ another number, the shown number counts up or down to it over `--duration-slowest` on a
70
+ decelerating curve, in `tabular-nums` digits so the line keeps its width. Every step shows the new
71
+ value's own decimals, so a whole number counts in whole numbers. A value that lands mid-count
72
+ continues from the number on screen. The first value, a text value and a projected
73
+ `[dsStatValue]` show at once, and under `prefers-reduced-motion: reduce` the duration is zero, so
74
+ the new number shows at once. `provideDsConfig({ stat: { animateValue: true } })` turns it on for
75
+ the whole app (`DsConfig.stat.animateValue`, default `false`); `animateValue="false"` keeps one
76
+ stat still, since the input wins over the config.
77
+ - **`ds-search` shows a running search, with `[loading]`.** A band sweeps along the bottom edge
78
+ of the field, easing in and out on every pass and fading at both ends of the track; the band fades
79
+ in when `loading` turns on and out when it turns off. The input reports `aria-busy`, and the query
80
+ stays visible and editable. Under `prefers-reduced-motion: reduce` the band stands still.
81
+ - **`check-overrides` lists the semantic tokens a full theme of your own does not set.** A rule
82
+ block in your styles that sets 20 or more of the tokens declared in `themes/_semantic.scss` is
83
+ read as a full theme; a semantic token it leaves out takes the library default inside it. For
84
+ each such block the check prints the file, the line, the selector and the tokens it does not set.
85
+ With `--from=<version>`, the version you upgraded from, it warns only about the tokens added
86
+ after it and prints the rest as information; without it every token the block does not set is a
87
+ warning. `--strict` fails on these warnings too, and the closing line counts them as theme gaps.
88
+ - **Migration manifest items list the semantic tokens they add, in `themeTokens`.** The item's
89
+ `action` names each one and says a full theme of your own sets it. `check-overrides --from`
90
+ reads the field to tell which tokens were added after the version you upgraded from.
91
+ - **`check-overrides` warns about a field of your own that hovers or focuses in `--border-strong`.**
92
+ `--border-strong` is fainter than `--border-field`, so a field drawn in `--border-field` at rest
93
+ that switches to `--border-strong` on `:hover`, `:focus`, `:focus-visible` or `:focus-within`
94
+ fades instead of strengthening. The check reports such a rule when its resting rule, the same
95
+ selector without the state or the parent of a nested `&:hover`, draws `--border-field` or a
96
+ library field's border token, and prints the file, the line and the selector. Use
97
+ `--border-field-hover` for a field's hover and focus border. `--strict` fails on it, and the
98
+ closing line counts these as field state borders.
99
+ - **An icon: `file-pen`.** A page with a pencil at its foot, for a draft or a document being
100
+ written. It sits on the 24-unit grid and takes the set's stroke.
101
+ - **An icon: `ds-mark`.** The design system's logo, four rounded blocks in blue, green, yellow and
102
+ red, the same mark as the docs site's favicon. It marks something that comes from the design
103
+ system, such as a DS component in a layers tree. It is filled in its own colours: `color`, the
104
+ stroke and a theme leave it unchanged.
105
+ - **`ds-icon-button` takes `color="inherit"` for a button on a surface filled with a colour.** A
106
+ `standard` button draws its icon in the surrounding text colour, and lays hover and press as that
107
+ colour at `--opacity-overlay-hover` and `--opacity-overlay-pressed`; its focus ring takes that
108
+ colour too, and its disabled icon is `--ds-icon-button-icon-color-disabled`, which on such a
109
+ button defaults to `color-mix(in srgb, currentcolor 40%, transparent)`. Use it for a close or
110
+ action button on a chip, a banner or a header with a coloured fill, where the default grey icon
111
+ and accent ring do not show. Other variants and a selected button keep the `primary` family. New
112
+ export `IconButtonColor` (`ButtonColor | 'inherit'`), the type of `color` now: code that reads
113
+ `color()` back as a `ButtonColor` handles `'inherit'`.
114
+ - **`ds-chat-step` shows the time a step took, at the end of its heading row.** `startedAt` and
115
+ `endedAt` take the step's timestamps, as a `Date`, an ISO string or epoch milliseconds, and the
116
+ row ends in the duration, right-aligned before `[trailing]`. A `running` step with `startedAt`
117
+ alone counts up each second until `endedAt` is set. The words come from the new `DsIntl` key
118
+ `chat.stepElapsed(seconds)`: `'4s'`, `'1m 13s'`, `'1h 2m'`. A step without `startedAt` draws
119
+ as before.
120
+ - **A `dsTreeTrailing` template is handed `expanded`.** `TreeTrailingContext` gains
121
+ `expanded: boolean`, `true` while the row's children show and `false` for a collapsed row or a
122
+ row without children. Read it with `let-expanded="expanded"` to show a folder's count of changes
123
+ only while it is collapsed.
124
+ - **Tonal press roles: `--primary-muted-pressed`, `--secondary-muted-pressed`,
125
+ `--tertiary-muted-pressed`, `--error-muted-pressed`, `--success-muted-pressed`,
126
+ `--warning-muted-pressed` and `--accent-muted-pressed`.** Each is the family's `-muted` fill mixed
127
+ 28% toward its base colour, in both themes; `--accent-muted-pressed` is the primary one, and
128
+ inside `ds-color` that family's. A `tonal` `ds-button` reads them for its press fill, which it
129
+ mixed itself; it draws the same colours. Set one to change the pressed tonal fill of that colour
130
+ across the app. A full theme of your own sets them too.
131
+ - **Neutral fill roles: `--neutral-fill`, `--neutral-fill-on`, `--neutral-fill-hover`,
132
+ `--neutral-fill-pressed`, `--neutral-fill-muted`, `--neutral-fill-muted-strong` and
133
+ `--neutral-fill-muted-pressed`.** The fill is `--text-secondary` under a `--surface-default`
134
+ label; hover and press step it with the same formula as `--primary-hover` and `--primary-pressed`,
135
+ and the tonal fills mix it into `--surface-default`, in both themes. A `ds-button` with
136
+ `color="neutral"` reads them; its fill and tonal colours are the ones it computed itself, and its
137
+ solid hover and press change as the solid `ds-button` entry under Changed says. Set one to change
138
+ neutral buttons across the app. A full theme of your own sets them too.
139
+ - **`ds-button` confirms a finished save in place, with `showSuccess(label)`.** Call it once the
140
+ work behind `loading` has succeeded: for 1.5 s the button takes the `success` colour in its own
141
+ variant, shows a check where the leading icon sits (before the label when there is none) and
142
+ `label` instead of its own label, and announces `label` through a polite live region; then its own
143
+ label and colour return. The check grows in from 80% over `--duration-base`. A second call
144
+ restarts the 1.5 s; `loading` set to `true` hides it at once. Without the call the button draws as
145
+ before.
146
+ - **`ds-number-stepper` is a form field.** It takes `label`, `required`, `hint`, `error`, `errors`,
147
+ `warning`, `invalid`, `touched`, `reserveMessage` and `messageIcon` as the other fields do: the
148
+ label above the box with an asterisk when `required`, the message line under it, the box in the
149
+ error colours while invalid and with the warning border under a warning. It binds
150
+ `[formControl]`, `formControlName`, `ngModel` and signal forms; a control reset to `null` sets
151
+ the value to `min`. Leaving the stepper marks it touched, and `hidden` hides it. `ariaLabel`
152
+ names the input only when there is no `label`. Without the new inputs it draws as before, unless
153
+ the app turns `DS_CONFIG.field.reserveMessage` on, with
154
+ `provideDsConfig({ field: { reserveMessage: true } })` or `dsReserveMessages`: then it reserves
155
+ the empty message line under the box, as every field does. Nothing to change in your code,
156
+ unless such a stepper must keep its height: set `reserveMessage="false"` on it.
157
+ - **`ds-dropzone` is a form field, with its error inside the zone.** It takes `label`, `required`,
158
+ `hint`, `error`, `errors`, `warning`, `invalid`, `touched`, `reserveMessage` and `messageIcon`:
159
+ the label above the zone, a hint or warning on the message line under it, and an error drawn
160
+ inside the dashed frame, which turns `--error` on `--error-subtitle`, with no line under
161
+ it. It binds `[formControl]`, `formControlName`, `ngModel` and signal forms, the value being the
162
+ `DropzoneFile[]` of `files`; a control reset to `null` empties the list. Picking, dropping,
163
+ removing a file or leaving the zone marks it touched. A row's own `message` stays in the file
164
+ list. `label` also names the file input, in place of `DS_INTL.dropzone.label`. Without the new
165
+ inputs it draws as before, unless the app turns `DS_CONFIG.field.reserveMessage` on: then it
166
+ reserves the empty message line under the zone, as every field does. Nothing to change in your
167
+ code, unless such a dropzone must keep its height: set `reserveMessage="false"` on it.
168
+ - **`ds-badge` draws a status lozenge, with `appearance="lozenge"`.** The badge takes a 1px border
169
+ in `--ds-badge-border-color`, 14px regular text with no letter spacing on a 16px line, `--space-0-5`
170
+ `--space-1` padding and a `--space-1` gap, so it stands 20px high. `icon` puts an `IconName`
171
+ before the label, 12px in the lozenge and 16px otherwise, drawn in `--ds-badge-icon-color`, the
172
+ label colour by default, and not shown while `count` is set; the icon is decorative, so the label
173
+ names the status. `status.define` takes a `border` colour per
174
+ status and sets the icon colour from `dot`; `status.semantic-preset` gives each of its statuses
175
+ its `--*-border` role (`--border-default` for `neutral`). New export `BadgeAppearance`
176
+ (`'default' | 'lozenge'`). In the lozenge `--ds-badge-padding-x` defaults to `--space-1`,
177
+ `--ds-badge-padding-y` to `--space-0-5`, `--ds-badge-font-size` to `--font-size-s`,
178
+ `--ds-badge-font-weight` to `--font-weight-regular` and `--ds-badge-letter-spacing` to
179
+ `--letter-spacing-normal`; a value you set on them still wins. Without `appearance` and `icon`
180
+ the badge draws as before.
181
+ - **Three icons: `success-filled`, `error-filled` and `progress`.** A filled circle with a check, a
182
+ filled circle with an exclamation mark, and a ring with its right half filled, for a status
183
+ lozenge. They are drawn in `currentColor`.
184
+ - **`ds-number-stepper` and `ds-dropzone` show the checking and changed states.** They take
185
+ `pending`, `dirty` and `showDirty` as the other fields do, and read the same from `[formControl]`,
186
+ `formControlName`, `ngModel` and signal forms. While `pending` or an async validator runs, a
187
+ spinner draws in the top corner of the stepper box beside the plus button, over the box so the
188
+ value does not move, and on the dropzone's message line under the zone. Under `showDirty`,
189
+ `dsShowDirty` or `DS_CONFIG.field.showDirty`, a changed value adds a dot in the same place and
190
+ "Changed" to the message line; with an error inside the dropzone, the spinner, dot and
191
+ "Changed" join it there. Without these inputs and a bound form control, both draw as before.
192
+ - **`ds-button`, `ds-split-button` and `ds-icon-button` take a `surface` variant: the outline
193
+ button on the field fill.** `variant="surface"` draws the border of `outline` (`outlined` on
194
+ `ds-icon-button`) over `--surface-default`, the fill of `ds-select` and `ds-input`, so the button
195
+ stays a plate on `--surface-secondary` and `--surface-muted`, where a transparent `outline` takes
196
+ the colour of the surface: on `--surface-muted` the plate stands at 1.19:1 in light and 1.20:1
197
+ under `data-theme="dark"`. Hover and press mix `--state-overlay` into that fill. Disabled, it
198
+ draws as a disabled `outline` does. The fill is `--ds-button-bg-color` and
199
+ `--ds-icon-button-bg-color`, and the new `--ds-split-button-surface-bg-color` on
200
+ `ds-split-button`. On `ds-button`, `success` and `warning` `surface` dev-warn as their `outline`
201
+ does. `ButtonVariant`, `SplitButtonVariant` and `IconButtonVariant` gain `'surface'`: a `Record`
202
+ keyed by one of them, or a `switch` that returns from each of its values, handles `'surface'`.
203
+
204
+ ### Changed
205
+
206
+ - **Controls are rounded 6px, on a new `--radius-sm-md` step.** `--ds-radius-control` resolves to
207
+ `--radius-sm-md` (6px), where it resolved to `--radius-md` (8px), so every component whose radius
208
+ hook falls back to it rounds 2px less, among them button, icon button, input, textarea, select,
209
+ multi-select, autocomplete, search, date and time picker triggers, field group, tag, alert,
210
+ banner, tooltip, tabs, pagination, table, nav item and group, chat input and the chart tooltip.
211
+ `--radius-md` keeps 8px. Nothing to change in your code, unless a screen must keep 8px controls:
212
+ set `--ds-radius-control: var(--radius-md)` on `:root`, or on one element for the corners drawn
213
+ inside it. Put it in a stylesheet loaded after the design system's, where it wins on order.
214
+ - **`ds-number-stepper` draws its buttons on tinted pads inside the box.** The minus and plus are
215
+ square pads inset `--space-1` inside the border (`--space-0-5` in a box under 32px, with a 14px
216
+ glyph instead of 18px), rounded `--ds-radius-inner`, on
217
+ `--ds-number-stepper-step-bg-color` (new, default `--surface-secondary`), with no dividers beside
218
+ the value. Under the pointer a pad takes `--ds-number-stepper-step-bg-color-hover` (new, default
219
+ `--accent-subtitle`, where the hover was `--surface-secondary`) and its glyph
220
+ `--ds-number-stepper-step-text-color-hover` (new, default `--accent-strong`); a press keeps
221
+ `--ds-number-stepper-step-bg-color-active`. On the error fill the pads take the box's own
222
+ background, and disabled pads are clear. The value is set in medium weight and the minus and plus
223
+ in regular, where both were bold, and the box is 12px narrower at `sm`, `md` and `lg`. Nothing to
224
+ change in your code, unless a screen must keep flat buttons: set
225
+ `--ds-number-stepper-step-bg-color: transparent`,
226
+ `--ds-number-stepper-step-bg-color-hover: var(--surface-secondary)` and
227
+ `--ds-number-stepper-step-text-color-hover: var(--text-primary)` on its `ds-number-stepper`; no
228
+ hook restores the dividers or the bold weight.
229
+ - **A `ds-badge` with text is rounded 4px, not a pill.** `--ds-badge-radius` defaults to
230
+ `--ds-radius-inner` (4px), where it defaulted to `--ds-radius-pill`. A count badge (`count` set)
231
+ and the status dot stay round. Nothing to change in your code, unless a screen must keep the
232
+ pill: set `--ds-badge-radius: var(--ds-radius-pill)` on its `ds-badge`.
233
+ - **Component corners drawn from `--radius-md` read a radius role, so a theme's
234
+ `--ds-radius-control` reaches them.** `--ds-radius-control` (6px, where they drew 8px): `ds-menu`
235
+ (`--ds-menu-radius` defaults to it), `ds-toggle-button`, `ds-split-button`, the end buttons of
236
+ `ds-button-group`, `ds-number-stepper`, the cells of `ds-otp-input`, `ds-skeleton`, `ds-w3w`,
237
+ the `ds-color-picker` trigger and colour plane, the typed confirmation field of
238
+ `ds-modal-confirm`, the month and year menus of `ds-date-picker`, the file rows of `ds-dropzone`,
239
+ the `ds-nav` mark, the `ds-nav-group` caret button, the rows, search box and more button of
240
+ `ds-nav-footer`, the reload overlay of a chart, and the segments of `ds-segmented`
241
+ (`--segmented-r-inner`; the track follows at 8px, where it was 10px, 2px of padding outside
242
+ them). `--ds-radius-panel` (12px): the `ds-color-picker` panel, as the other picker panels.
243
+ `--ds-radius-inner` (4px): the `ds-color-picker` preview swatch and the alert icons of
244
+ `ds-nav-footer`. A `ds-nav-group` header takes the group's own radius, `--ds-nav-group-radius`
245
+ (6px by default). Nothing to change in your code, unless a screen must keep the 8px corners: the
246
+ `:root` setting of `--ds-radius-control` above restores every corner that now reads it. For one
247
+ component, set `--ds-radius-control: var(--radius-md)` on its element: `ds-color-picker` and
248
+ `ds-date-picker` carry it onto their panels, so it reaches the colour plane and the month and
249
+ year menus. The search box of `ds-nav-footer` sits in a popover that only the `:root` setting
250
+ reaches. `ds-segmented` takes `--ds-segmented-radius-inner: var(--radius-md)` instead, and the
251
+ colour picker panel `--ds-radius-panel: var(--radius-md)` on `ds-color-picker`. No hook restores
252
+ the 8px preview swatch of `ds-color-picker` or the 8px alert icons of `ds-nav-footer`.
253
+ - **`--ds-dropdown-panel-max-height` caps the option list too.** Set on `ds-select`,
254
+ `ds-multi-select`, `ds-autocomplete` or another picker, it sets how tall the list grows before it
255
+ scrolls: 480px shows 14.7 rows of 32px instead of stopping at 280px (8.75 rows). Unset, the list
256
+ stops at `--picker-maxh` (280px). Nothing to change in your code, unless a picker sets
257
+ `--ds-dropdown-panel-max-height` and must keep its list at 280px: lower that value to 280px, or
258
+ set `max-height: var(--picker-maxh)` on `.dropdown-list` in a `panelClass` of its own.
259
+ - **The `ds-switch` knob settles with `--ease-settle`.** It travels over `--duration-base` on the
260
+ damped curve `ds-button`, `ds-badge`, `ds-description-item` and `ds-toast` use, with no overshoot,
261
+ where it took `--ease-standard`. The track colour keeps `--ease-standard`. Under
262
+ `prefers-reduced-motion: reduce` the knob moves at once. Nothing to change in your code; no hook
263
+ restores the old curve.
264
+ - **A `ds-button` eases to its new width when it starts or stops loading or shows a success.** When
265
+ `loading` or `showSuccess(label)` changes the button's width (a label set while loading, the
266
+ success label), it tweens from the old width to the new over `--duration-slow` with
267
+ `--ease-settle`, so the buttons beside it slide instead of jumping. A `fullWidth` button does not
268
+ tween, and a button its container stretches keeps its width. The loading spinner fades in over
269
+ `--duration-fast`. Under `prefers-reduced-motion: reduce` the width changes at once. Nothing to
270
+ change in your code; no hook turns the tween off.
271
+ - **A `ds-badge` count rolls to its new value.** When `count` changes, only the characters that
272
+ change roll, paired with the old ones from the right: a new digit slides in from the top on a rise
273
+ and from the bottom on a fall while the old one slides out the other way, a character that stays
274
+ (the 1 of 12 to 13) does not move, and a digit that appears or goes grows from or shrinks to zero
275
+ width, so the badge eases to its new width, over `--duration-base` with `--ease-settle`;
276
+ `--ds-badge-count-roll-duration` and `--ds-badge-count-roll-easing` set the timing. The first
277
+ value and a change that keeps the shown text (`99+` to `99+`) do not move, and under
278
+ `prefers-reduced-motion: reduce` nothing rolls. The roll renders in `ds-badge-count-roll`, an
279
+ internal element in a deferred chunk that loads only for a badge with a `count` and the roll on:
280
+ it is not API, so do not use it in a template or style it. Nothing to change in your code, unless
281
+ a badge must keep the instant change: set `animateCount="false"` on it, or
282
+ `provideDsConfig({ badge: { animateCount: false } })` for the whole app
283
+ (`DsConfig.badge.animateCount`, default `true`); the input wins over the config.
284
+ - **Short labels in a fixed box are centred on their glyphs.** The count of `ds-badge`, the counters
285
+ of `ds-tabs` and `ds-nav-item`, the initials of `ds-avatar`, the step number of `ds-stepper`, the
286
+ repeat count of `ds-toast`, the brand letter of `ds-nav` and `ds-auth-layout` and the page numbers
287
+ of `ds-pagination` sat high in their box, since figures and capitals have no descender. Each label
288
+ is trimmed to cap height and baseline (`text-box: trim-both cap alphabetic`), which centres its
289
+ glyphs to within half a pixel; a browser without `text-box` keeps line-box centring. The page
290
+ numbers of `ds-pagination` are also centred across on their ink, where a figure with wide side
291
+ bearings, such as 1, sat right of the tile's centre: each label is moved sideways by the gap
292
+ between the centre of its ink and the centre of its advance width, read from the rendered font.
293
+ Nothing to change in your code; no hook restores line-box centring or the sideways move.
294
+ - **The `ds-toast` `[actions]` slot sits on the toast's vertical centre.** It sat at the top of the
295
+ toast; it now shares the centre line of the text action and the icon action, in a toast of one
296
+ line and of several. The close button stays at the top. Nothing to change in your code; no hook
297
+ puts the slot back at the top.
298
+ - **The `ds-description-item` copy button fades to a green check.** On copy the icon fades out over
299
+ `--duration-fast` while a `--success-text` check grows in from 80% over `--duration-base`, where
300
+ the icons swapped at once and the check took the button's colour. After 1.2 s the check fades out
301
+ and the copy icon back in over `--duration-fast`. Under `prefers-reduced-motion: reduce` they swap
302
+ at once. Nothing to change in your code; no hook restores the instant swap or the check's colour.
303
+ - **The dashed `ds-dropzone` border is drawn in `--border-field`.** `--ds-dropzone-border` defaults
304
+ to `--border-field`, where it defaulted to `--border-default` (1.31:1 on white), and the zone
305
+ clips its fill to the padding box, so the dashes lie over the surface under it: 3.44:1 on the
306
+ page, 3.47:1 on a card and 3.37:1 on `--surface-muted` in light, 4.38:1, 4.32:1 and 4.03:1 under
307
+ `data-theme="dark"`. Hover and drag-over keep `--accent`. Nothing to change in your code, unless a
308
+ screen must keep the light dashes: set `--ds-dropzone-border: var(--border-default)` on its
309
+ `ds-dropzone`.
310
+ - **An unchecked `ds-checkbox` and `ds-radio` and an OTP cell darken their border under the pointer,
311
+ as a field does.** All three hover to `--border-field-hover`, where the checkbox and radio hovered
312
+ to `--accent`, the colour of the checked state and of focus, and the cells of `ds-otp-input` did
313
+ not change. A checked or indeterminate box keeps its checked border under the pointer, and a
314
+ focused OTP cell keeps its focus border. `--ds-checkbox-hover-border-color` defaults to
315
+ `--border-field-hover`; the OTP cell takes the new `--ds-otp-cell-border-color-hover`, default
316
+ `--border-field-hover`. Nothing to change in your code, unless a screen must keep the old hover:
317
+ set `--ds-checkbox-hover-border-color: var(--accent)` on its `ds-checkbox`, or
318
+ `--ds-otp-cell-border-color-hover: var(--border-field)` on its `ds-otp-input`. No hook restores
319
+ the `--accent` hover of `ds-radio`.
320
+ - **The active `ds-nav-item` draws no edge marker by default.** `rail` on `ds-nav` defaults to
321
+ `false`, where it was `true`, and a `ds-nav-item` whose own `rail` is unset follows it, so the
322
+ active item is marked by its `--ds-nav-item-bg-color-active` fill and
323
+ `--ds-nav-item-label-color-active` label alone. `rail` on a `ds-nav-item` still overrides the nav
324
+ for that item, and a `[rail]="false"` you set on `ds-nav` is now the default and can go. Nothing
325
+ to change in your code, unless a screen must keep the marker: set `[rail]="true"` on its `ds-nav`,
326
+ which puts back the 3px `--ds-nav-item-rail` marker for every item.
327
+ - **The field border is translucent, so it darkens with the surface under it.** `--border-field` is
328
+ `rgb(0 0 0 / 46%)` in light and `rgb(255 255 255 / 44%)` under `data-theme="dark"`;
329
+ `--border-field-hover` is 68% of the same colour in both themes. It holds 3.37-3.47:1 on the page,
330
+ a card, a popover, a modal and their secondary and muted fills in light, and 3.36-4.38:1 in dark.
331
+ Every box that draws it clips its fill to the padding box (`background-clip: padding-box`), so the
332
+ border lies over the surface under the field, not over the field's own fill: input, textarea,
333
+ select, multi-select, autocomplete, search, number stepper, the date, time and colour picker
334
+ triggers, field group, OTP cells, chat input, checkbox and radio. The off track of `ds-switch`,
335
+ filled with `--border-field`, is translucent too. Nothing to change in your code, unless a screen
336
+ must keep the solid border: set
337
+ `--border-field: color-mix(in srgb, var(--neutral-500) 86%, var(--neutral-400))` and
338
+ `--border-field-hover: var(--neutral-600)` on `:root`, and
339
+ `--border-field: color-mix(in srgb, var(--neutral-500) 80%, var(--neutral-400))` and
340
+ `--border-field-hover: var(--neutral-500)` on `:root[data-theme="dark"]`. Put it in a stylesheet
341
+ loaded after the design system's, where it wins on order.
342
+ - **The glyph in a `ds-chat-step` or `ds-timeline-item` marker sits on its optical centre.** The
343
+ marker moves the glyph so that the point midway between the centre of its stroke box and the
344
+ centre of its stroke length lands on the circle's centre: a symmetric glyph (`x`, `pause`,
345
+ `clock`) stays centred by its box, and a glyph heavier on one side, such as `flag`, `folder` or
346
+ `bell`, moves a fraction of a pixel toward balancing it. It applies to every `icon` a
347
+ `ds-timeline-item` is given, including one registered with `provideDsIcons()`. Nothing to change
348
+ in your code; no hook restores box centring.
349
+ - **A `ds-chat-step` or `ds-timeline-item` that changes `status` moves to the new state instead of
350
+ switching.** The marker's fill, ring and glyph colours fade over `--duration-base`, and the dashed
351
+ ring of a `pending` step fades into the solid one and back. A step that turns `done`, `error` or
352
+ `waiting` takes the spinner's arc over from the angle and length it stands at: the arc keeps
353
+ turning while its head runs on round to a ring in the new colour over `--duration-slow`, the fill
354
+ grows out of the ring to the marker's edge over `--duration-base`, and the glyph draws stroke by
355
+ stroke, the check in one stroke and the cross and the pause in two, about 0.5 s in all. A spinner
356
+ arriving grows its arc from nothing to its length over `--duration-slow`, and the glyph it
357
+ replaces leaves over `--ds-motion-check-exit-duration` with `--ds-motion-check-exit-easing`, as a
358
+ checkbox's check does. A `ds-chat-step` heading fades into the running shimmer and back out of it
359
+ over `--duration-slow`, the sweep pausing where it stood. The first paint of a step does not
360
+ animate, and under `prefers-reduced-motion: reduce` every change is instant. Nothing to change in
361
+ your code; no hook turns the motion off.
362
+ - **A focused field draws one crisp ring in its border colour, without the soft halo.**
363
+ `--ds-field-focus-shadow` defaults to `0 0 0 var(--border-width-default) var(--primary)`, where it
364
+ was the 3px `--focus-field` halo, so the 1px border and the shadow read as one 2px ring;
365
+ `--ds-field-focus-shadow-error`, `-warning` and `-success` do the same in `--error`, the warning
366
+ hue (see the next entry) and `--success`. This is the field ring `data-focus="edge"` drew, and
367
+ `edge` now only sets the control outline offset to 0. `--accent-focus-field` is the same ring, in
368
+ the zone's colour inside a `ds-color` zone, so `ds-multi-select`, `ds-otp-input`,
369
+ `ds-color-picker` and the `ds-modal-confirm` input draw it too; an invalid `ds-otp-input` cell
370
+ rings in `--ds-field-focus-shadow-error`. It reaches `ds-input`, `ds-textarea`, `ds-select`,
371
+ `ds-multi-select`, `ds-search`, `ds-autocomplete`, `ds-date-picker`, `ds-time-picker`,
372
+ `ds-number-stepper`, `ds-field-group`, `ds-otp-input`, `ds-color-picker` and `ds-chat-input`, in
373
+ both themes. `data-focus="ring"` and `data-focus="inset"` are unchanged. Nothing to change in your
374
+ code, unless the app must keep the halo: set `data-focus="halo"` on `<html>`, which puts back
375
+ `--ds-field-focus-shadow`, its error, warning and success variants and `--accent-focus-field`,
376
+ inside `ds-color` zones too.
377
+ - **A field under a warning draws its border in the bright warning hue.** The border reads the new
378
+ `--ds-field-border-warning`, and once focused the new `--ds-field-focus-border-warning`, both
379
+ `hsl(var(--warning-h) var(--warning-s) var(--warning-l))`, `#F3CB39` in both themes, where it was
380
+ `--warning-text`; the focus ring `--ds-field-focus-shadow-warning` takes the same colour. The
381
+ border reads 1.57:1 on `--surface-default` and 1.50:1 on `--surface-canvas` in light, 11.01:1 and
382
+ 11.89:1 under `data-theme="dark"`. Under `data-focus="ring"`, `"halo"` and `"inset"` a focused
383
+ warning field keeps its `--warning-text` border. The message under the field stays
384
+ `--warning-text`. It reaches `ds-input`, `ds-textarea`, `ds-select`, `ds-multi-select`,
385
+ `ds-autocomplete`, `ds-date-picker`, `ds-time-picker`, `ds-color-picker`, `ds-otp-input`,
386
+ `ds-number-stepper` and `ds-dropzone`. Nothing to change in your code, unless a screen must keep
387
+ the darker border: set `--ds-field-border-warning: var(--warning-text)` on `:root` (4.59:1 on
388
+ `--surface-default`), and `data-focus="halo"` on `<html>` for the focused border and halo. Put it
389
+ in a stylesheet loaded after the design system's, where it wins on order.
390
+ - **A `pills` `ds-tabs` strip sits on a darker grey track.** `--ds-tabs-pills-bg-color` defaults to
391
+ `--surface-muted`, where it was `--surface-secondary`; the selected tab keeps `--surface-default`.
392
+ On `--surface-canvas` the track reads 1.13:1 in light and 1.30:1 in dark, where it read 1.05:1 and
393
+ 1.19:1, and the selected tab reads 1.19:1 and 1.20:1 on the track, where it read 1.10:1. Nothing
394
+ to change in your code, unless a screen must keep the lighter track: set
395
+ `--ds-tabs-pills-bg-color: var(--surface-secondary)` on its `ds-tabs`.
396
+ - **A vertical `pills` `ds-tabs` strip and its selected tab draw no line on their right edge.** The
397
+ strip drew the `--ds-tabs-divider` line of a vertical `line` strip on its right edge, and the
398
+ selected tab the `--ds-tab-indicator-color` line beside its fill; both are gone, so the selected
399
+ tab shows its fill alone and each tab is narrower by `--ds-tab-indicator-width`, 2px by default.
400
+ Horizontal `pills` and the `line` variant are unchanged. Nothing to change in your code; no hook
401
+ restores the lines.
402
+ - **The `ds-tabs` indicator slides from the old tab to the new one.** A `line` strip, horizontal or
403
+ vertical, draws one indicator that moves and resizes to the selected tab over `--duration-slow`,
404
+ where each tab lit its own border; it appears in place on first render and follows a tab whose
405
+ width changes. `--ds-tab-indicator-color` and `--ds-tab-indicator-width` style it. Only the `line`
406
+ strip slides, and under `prefers-reduced-motion: reduce` it moves at once. Nothing to change in
407
+ your code; no hook turns the slide off.
408
+ - **The `ds-segmented` selection slides to the chosen segment.** The track draws one thumb under the
409
+ segments that moves and resizes to the selected one over `--duration-slow`, the labels' colour
410
+ changing over the same time. It takes `--ds-segmented-selected-bg-color` and
411
+ `--ds-segmented-selected-shadow`. A `joined` control does not slide: its selected segment keeps
412
+ its own fill. Under `prefers-reduced-motion: reduce` the thumb moves at once. Nothing to change in
413
+ your code; no hook turns the slide off.
414
+ - **The `[steps]` of a `ds-chat-message` take the whole row, not the bubble's width.** A step's
415
+ time, chevron and `[trailing]` end at the thread's right edge, level with the user's bubbles,
416
+ instead of at `--ds-chat-message-max-width`. The bubble under the steps keeps its width. Nothing
417
+ to change in your code; no hook narrows the steps to the bubble.
418
+ - **Hover and press on a surface are a layer of the element's own text colour.** The new roles
419
+ `--state-layer-hover` and `--state-layer-pressed` lay the text colour at `--opacity-state-hover`
420
+ (8%) and `--opacity-state-pressed` (16%) over whatever is under the element. `ds-list-item`,
421
+ `ds-menu-item`, `ds-tree` rows, `ds-table` rows, dropdown options, the `ds-nav-item` hover, the
422
+ nav group, the nav footer press, `ds-accordion` headers, `ds-pagination`, the `ds-tabs` close and
423
+ scroll buttons, `ds-inline-edit`, `ds-tag`, the `ds-date-picker` and `ds-time-picker` cells, chart
424
+ legends, the `ds-toast` close, `ds-description-item`, the `ds-multi-select` chip remove,
425
+ `ds-info-hint` and a pressed `ds-definition-term` read them, where they painted
426
+ `--surface-secondary` on hover and `--surface-muted` on press, and `ds-tag` and `ds-inline-edit`
427
+ hovered in `--surface-muted`. On a tinted card or inside an overlay the hover takes that surface's
428
+ hue instead of a grey patch. Nothing to change in your code, unless a screen must keep the grey:
429
+ set its component's hover hook to `var(--surface-secondary)`: `--ds-list-item-hover-bg-color`,
430
+ `--ds-menu-item-hover-bg-color`, `--ds-tree-row-hover-bg-color`, `--ds-table-row-hover-bg-color`,
431
+ `--ds-option-bg-color-active`, `--ds-nav-item-bg-color-hover`,
432
+ `--ds-accordion-header-hover-bg-color`, `--ds-pagination-button-bg-color-hover`,
433
+ `--ds-tab-close-bg-color-hover`, `--ds-tabs-scroll-arrow-bg-color-hover`,
434
+ `--ds-date-picker-day-hover-bg-color` or `--ds-chart-legend-hover-bg-color`; set
435
+ `--ds-tag-hover-bg-color`, `--ds-inline-edit-hover-bg-color` and `--ds-table-row-pressed-bg-color`
436
+ to `var(--surface-muted)`. No hook restores the other presses, or the hover of the nav group and
437
+ the `ds-toast` close.
438
+ - **Under `data-theme="dark"` a selected row is lighter than the card it sits on.** `--surface-tint`
439
+ is `color-mix(in srgb, var(--primary) 30%, var(--surface-default))`, the rule the overlays use for
440
+ their level, where it was `hsl(from var(--primary) h 45% 16%)`: 1.32:1 against a card, where it
441
+ was 1.04:1. `--primary-strong`, `--secondary-strong` and `--tertiary-strong` are 80% lightness,
442
+ where they were 72%, so a selected label keeps 4.5:1 on the lighter fill (6.20:1 with the library
443
+ brand), and `--accent-strong-overlay` equals `--accent-strong` in both themes. Nothing to change
444
+ in your code, unless a screen must keep the darker fill and labels: set
445
+ `--surface-tint: hsl(from var(--primary) h 45% 16%)`,
446
+ `--primary-strong: hsl(from var(--primary) h 90% 72%)`,
447
+ `--secondary-strong: hsl(var(--secondary-h) 90% 72%)`,
448
+ `--tertiary-strong: hsl(var(--tertiary-h) 90% 72%)` and
449
+ `--accent-strong-overlay: hsl(from var(--primary) h 90% 80%)` on `:root[data-theme="dark"]`. Put
450
+ it in a stylesheet loaded after the design system's, where it wins on order.
451
+ - **`ghost` and `outline` `ds-button` hover and press in their own colour on the page and in the
452
+ surface's hue on a coloured one.** They paint the new `--state-overlay` at the new
453
+ `--opacity-overlay-hover` on hover and `--opacity-overlay-pressed` on press, 6% and 12% in light
454
+ and 8% and 14% under `data-theme="dark"`, where they painted an opaque fill: the colour's
455
+ `-subtitle` on hover and `-muted` on press, `--surface-secondary` and `--neutral-fill-muted` for
456
+ `neutral`. `--state-overlay` is `currentcolor`, so on the page a `primary` ghost hovers blue and a
457
+ `neutral` one grey. Inside a `ds-alert` or a `ds-banner` it is the new `--state-overlay-tinted`,
458
+ black in light and white in dark, so the hover shades that surface instead of laying a second hue
459
+ on it; give a coloured panel of your own the same with
460
+ `--state-overlay: var(--state-overlay-tinted)` on the panel. Over a `--ds-button-bg-color` set on
461
+ the button the same overlay is mixed into that fill. An `outline` `ds-split-button` hovers and
462
+ presses with the same overlay, mixed into `--ds-split-button-outline-bg-color`, where it hovered
463
+ to `--surface-secondary` and pressed to `--surface-muted`. A `standard` or `outlined`
464
+ `ds-icon-button` does the same in its icon colour, where a `standard` one painted
465
+ `--surface-muted` on hover and press and an `outlined` one `--surface-secondary` on hover and
466
+ `--surface-muted` on press. A full theme of your own sets `--state-overlay-tinted`,
467
+ `--opacity-overlay-hover` and `--opacity-overlay-pressed` too. Nothing to change in your code,
468
+ unless a screen must keep the opaque fills: set `--ds-button-bg-color-hover` and
469
+ `--ds-button-bg-color-active` to the colour's `-subtitle` and `-muted` roles, for example
470
+ `var(--primary-subtitle)` and `var(--primary-muted)` on
471
+ `ds-button[data-variant="ghost"][data-color="primary"]` and
472
+ `ds-button[data-variant="outline"][data-color="primary"]`, and to `var(--surface-secondary)` and
473
+ `var(--neutral-fill-muted)` for `neutral`;
474
+ `--ds-split-button-outline-bg-color-active: var(--surface-muted)` on a `ds-split-button`, whose
475
+ hover has no hook; and `--ds-icon-button-bg-color-hover` and `--ds-icon-button-bg-color-active` on
476
+ a `ds-icon-button`, both `var(--surface-muted)` for `standard`, `var(--surface-secondary)` and
477
+ `var(--surface-muted)` for `outlined`.
478
+ - **A `solid` `ds-button` hovers and presses with its colour's roles.** It reads `--accent-hover`
479
+ and `--accent-pressed` (`primary`), `--secondary-hover`, `--tertiary-hover`, `--error-hover`,
480
+ `--success-hover`, `--warning-hover` and their `-pressed` pairs, and `--neutral-fill-hover` and
481
+ `--neutral-fill-pressed` (`neutral`), where it mixed its fill with 12% and then 24% of black in
482
+ both themes. A value your app sets on one of those roles reaches it. A fill set with
483
+ `--ds-button-bg-color` steps with the same formula as the roles, away from the button's label.
484
+ Nothing to change in your code, unless a screen must keep the old hover: set
485
+ `--ds-button-bg-color-hover: color-mix(in srgb, var(--primary) 88%, black)` and
486
+ `--ds-button-bg-color-active: color-mix(in srgb, var(--primary) 76%, black)` on
487
+ `ds-button[data-variant="solid"][data-color="primary"]`, and the same with the colour's role in
488
+ place of `--primary` for the others: `--neutral-fill` for `neutral`, and `--ds-button-bg-color`
489
+ where you set one.
490
+ - **The `-hover` and `-pressed` colour roles step away from their label colour.** `--primary-hover`,
491
+ `--primary-selected-hover`, `--secondary-hover`, `--tertiary-hover`, `--success-hover`,
492
+ `--warning-hover`, `--error-hover` and `--info-hover` move the role's OKLCH lightness by 0.05, and
493
+ the `-pressed` roles by 0.12, keeping its chroma and hue: darker when its `-on` colour is light,
494
+ lighter when it is dark (`--text-on-primary` for `info`), in both themes, so the label gains
495
+ contrast on hover and press. Where the pressed step would end under OKLCH lightness 0.3 or over
496
+ 0.95, both states move toward the label instead, so a near-black fill lightens and a pale yellow
497
+ one darkens. They mixed 12% and 24% of black in light and of white under `data-theme="dark"`.
498
+ Nothing to change in your code, unless a screen must keep the old states: set
499
+ `--primary-hover: color-mix(in srgb, var(--primary) 88%, black)` and
500
+ `--primary-pressed: color-mix(in srgb, var(--primary) 76%, black)` (or the family's pair) on
501
+ `:root`, and the same with `white` in place of `black` on `:root[data-theme="dark"]`. Put it in
502
+ a stylesheet loaded after the design system's, where it wins on order.
503
+ - **The focus ring and the field halo take `--primary`, and `--focus-ring-outer-h`,
504
+ `--focus-ring-outer-s` and `--focus-ring-outer-l` are removed.** `--focus-ring`,
505
+ `--focus-ring-inset` and `--focus-field` read the colour of `--primary` at their own alpha, where
506
+ they read the channels `--primary-h`, `--primary-s` and `--primary-l`, so a brand that set
507
+ `--primary` alone had a blue ring and halo. The default theme draws the same colours. A brand that
508
+ set the channels without `--primary` gets its ring in `--primary` now: set `--primary` too. To
509
+ tint the ring apart from `--primary`, where you set the removed tokens, set `--focus-ring` and
510
+ `--focus-ring-inset`. `--focus-ring-outer-alpha` stays.
511
+ - **`ds-chat-input` animates the buttons that come and go while it is busy.** With
512
+ `busyAction="queue"`, Redirect and Stop grow in from nothing beside the main button as text is
513
+ typed and shrink away when it is cleared, so the bar widens and narrows instead of jumping; the
514
+ main button keeps its square while its icon fades in on each change between send, Stop and Queue,
515
+ and the Stop ring fades instead of snapping. Under `prefers-reduced-motion: reduce` each state
516
+ shows at once. The `div.send` wrapper no longer carries a `queue` class, so a rule you wrote
517
+ against `.send.queue` targets nothing now. Nothing else to change; no hook turns the motion off.
518
+ - **The `ds-heatmap-chart` scale sits 12px under the grid, with the reading marker on it.** The gap
519
+ above the colour scale is `--space-3` (12px), where it was `--space-6` (24px), so every heatmap is
520
+ 12px shorter. The marker that shows the hovered cell's reading sits on the scale, centred on it,
521
+ on a `--text-primary` plate with `--surface-default` text, where it stood above the scale with an
522
+ arrow. Nothing to change in your code; no hook restores the old gap or marker.
523
+ - **`ds-scatter-chart` hover draws the ring alone.** The dashed line from the pointer to the nearest
524
+ point is gone, and with it the `line.nearest-tether` element; the ring still glides to the nearest
525
+ point. A rule you wrote against `.nearest-tether` targets nothing now, and
526
+ `--ds-chart-cursor-line-color` no longer reaches `ds-scatter-chart`, though it still styles the
527
+ cursor line of `ds-chart` and `ds-line-chart`. No hook restores the line.
528
+ - **A `running` `ds-chat-step` heading and the `ds-chat-thread` working row are swept by a moving
529
+ highlight.** The text is drawn in `--text-tertiary` with a band of `--text-primary` crossing it
530
+ from left to right every `--duration-loop-slow`. Under `prefers-reduced-motion: reduce` nothing
531
+ moves and the text keeps its own colour, `--text-primary` for the heading and `--text-secondary`
532
+ for the working row. Nothing to change in your code; no hook turns the sweep off.
533
+ - **An unpressed `ds-toggle-button` draws the outline button border.**
534
+ `--ds-toggle-button-border-color` defaults to `--border-default`, the border of a `neutral`
535
+ `outline` `ds-button`, where it defaulted to `--border-field`. Hover still takes
536
+ `--border-field-hover`. Nothing to change in your code, unless a screen must keep the field
537
+ border: set `--ds-toggle-button-border-color: var(--border-field)` on its `ds-toggle-button`.
538
+ - **A read-only and a disabled `ds-multi-select` look like the same `ds-select`.** Read-only, the
539
+ trigger takes the `--surface-secondary` fill and the `--border-readonly` border, at rest and on
540
+ hover, with the chevron in `--icon-muted`; it drew the editable border and darkened it under the
541
+ pointer. Disabled, it takes the `--surface-disabled` fill and the `--border-disabled` border,
542
+ with the chevron and the chip labels in `--icon-muted` and `--text-disabled`, where it kept the
543
+ field border on a `--surface-muted` fill and dark chip labels. In both states the chips show no
544
+ remove button, so a value can no longer be removed from a read-only or disabled multi-select.
545
+ Nothing to change in your code, unless a screen let a user remove chips from such a
546
+ multi-select: keep it editable while its value may change.
547
+ - **A read-only `ds-select` shows its chevron and draws its value in the field text colour.** The
548
+ chevron, hidden in read-only, shows in `--icon-muted`, the colour of a disabled select's chevron,
549
+ and the select still does not open. The value took `--text-secondary` and now takes
550
+ `--ds-select-text-color`, which defaults to `--text-primary`, as a read-only `ds-input` does. The
551
+ border stays `--border-readonly` at rest and on hover. Nothing to change in your code, unless a
552
+ screen must keep the lighter value: set `--ds-select-text-color: var(--text-secondary)` on that
553
+ read-only `ds-select`.
554
+ - **The unfilled `ds-slider` track draws the field border.** `--ds-slider-track-color` defaults to
555
+ `--border-field`, the colour of the off `ds-switch` track, where it defaulted to
556
+ `--surface-muted`: the track holds 3.37-3.47:1 on the page, a card, `--surface-muted` and
557
+ `--surface-tint` in light and 3.78-4.38:1 under `data-theme="dark"`, where it was 1.00-1.30:1. A
558
+ disabled slider keeps the light track, `--border-disabled`. The filled part and the thumb are
559
+ unchanged, and range sliders follow. Nothing to change in your code, unless a screen must keep the
560
+ light track: set `--ds-slider-track-color: var(--surface-muted)` on its `ds-slider`.
561
+ - **A disabled field keeps its border on a grey surface.** `--border-disabled` is
562
+ `rgb(0 0 0 / 12%)` in light and `rgb(255 255 255 / 14%)` under `data-theme="dark"`, where it was
563
+ `--neutral-150`, the colour of `--surface-muted`, and vanished on it. Translucent like
564
+ `--border-field`, it reads 1.31-1.32:1 on `--surface-default`, `--surface-secondary` and
565
+ `--surface-muted` in light and 1.53-1.57:1 in dark, where it was 1.00-1.20:1; still below 3:1, as
566
+ a disabled control is exempt, and lighter than `--border-readonly`. Every box that draws it
567
+ moves: a disabled `ds-input`, `ds-textarea`, `ds-select`, `ds-multi-select`, `ds-autocomplete`,
568
+ `ds-search`, `ds-number-stepper`, `ds-date-picker`, `ds-time-picker`, `ds-field-group`,
569
+ `ds-dropzone`, `ds-chat-input`, `ds-checkbox` and `ds-radio`, and the track of a disabled
570
+ `ds-slider`. Forced colours still draw `GrayText`. Nothing to change in your code, unless a
571
+ screen must keep the solid border: set `--border-disabled: var(--neutral-150)` on `:root` and
572
+ `:root[data-theme='dark']` inside `@media not (forced-colors: active)`, so forced colours keep
573
+ `GrayText`. Put it in a stylesheet loaded after the design system's, where it wins on order.
574
+
575
+ ### Deprecated
576
+
577
+ - **`ds-sidenav`, `ds-sidenav-group`, `ds-sidenav-item` and `ds-sidenav-footer`, with their exports,
578
+ hooks and slot, are removed 10 releases after 1.2.0.** Until then each still works: an old tag
579
+ renders the same component and warns once in the console in development; `SidenavComponent`,
580
+ `SidenavGroupComponent`, `SidenavItemComponent`, `SidenavFooterComponent`, `SIDENAV`,
581
+ `SidenavContract`, `SidenavItemModel`, `SidenavAlertItem`, `SidenavSearchProvider` and
582
+ `SidenavSearchResult` are the `Nav` symbols under the old names; every `--ds-nav-*` hook falls
583
+ back to its `--ds-sidenav-*` name; and `ds-app-layout` still projects an element marked `sidenav`.
584
+ Rename them to the `ds-nav` names. `@ids-group-ltd/ids-design-system/components/sidenav` and
585
+ `@ids-group-ltd/ids-design-system/components/sidenav-footer` export both names and go with the old
586
+ ones.
587
+
588
+ ### Fixed
589
+
590
+ - **`[data-density]` on an element inside the page sets field heights there too.** The field
591
+ heights `--field-h-sm` and `--field-h-md`, `--sidenav-collapsed-item` and `--calendar-cell-min` are
592
+ re-derived under every `[data-density]`, so a `compact` section draws its inputs, selects,
593
+ steppers and buttons at 32px and the rest of the page keeps its own height. They were derived only
594
+ on `:root`, so density set below `html` left them at the page's height. Density on `html` renders
595
+ as before. Nothing to change in your code.
596
+ - **A disabled `ds-input` draws its value in `--text-disabled`, as a disabled `ds-select` does.**
597
+ The value kept the field text colour, `--text-primary`, so a disabled input read like an enabled
598
+ one. `--ds-input-text-color` and `--ds-field-text-color` do not reach a disabled input. Nothing to
599
+ change in your code, unless a screen must keep the darker value: set
600
+ `--text-disabled: var(--text-primary)` on its `ds-input`.
601
+ - **A disabled `ds-textarea` draws its value in `--text-disabled`, as a disabled `ds-input` does.**
602
+ The value kept the field text colour, `--text-primary`, so a disabled textarea read like an
603
+ enabled one. `--ds-input-text-color` and `--ds-field-text-color` do not reach a disabled
604
+ textarea. Nothing to change in your code, unless a screen must keep the darker value: set
605
+ `--text-disabled: var(--text-primary)` on its `ds-textarea`.
606
+ - **A disabled or read-only `ds-textarea` shows no resize handle.** Its `resize` input applies
607
+ only while the field is editable. Nothing to change in your code; no hook restores the handle on
608
+ a disabled or read-only textarea.
609
+ - **A link in the dark theme keeps its contrast on hover and press.** `.link` darkened its colour
610
+ toward black for hover and press in both themes, which in the dark theme fell to 4.21:1 on hover
611
+ and 2.99:1 on press against `--surface-default`. Hover and press now mix toward the new role
612
+ `--text-link-state-ink`: black in the light theme, as before, and white in the dark theme, where
613
+ the same link reads 7.92:1 on hover and 9.25:1 on press. Visited links follow the same role. An
614
+ override of `--ds-link-color-hover`, `--ds-link-color-active`, `--ds-link-color-visited-hover` or
615
+ `--ds-link-color-visited-active` still wins. A full theme of your own sets
616
+ `--text-link-state-ink`. Nothing else to change in your code.
617
+ - **Under forced colours a disabled field draws its border and text in `GrayText`.** Forced
618
+ colours paint every author border colour as `CanvasText`, so a disabled field looked like an
619
+ enabled one. Under `forced-colors: active`, `--border-disabled` and `--text-disabled` are
620
+ `GrayText`, a system colour the browser keeps: a disabled field, checkbox, radio and dropzone
621
+ draws its border in `GrayText`, and every control that draws disabled text (menu items, tabs and
622
+ pagination among them) draws it in `GrayText`. Nothing to change.
623
+ - **The search field in the `ds-table` column filter draws the field border and radius.**
624
+ `.col-filter-search` took `--border-default`, 1.31:1 on white, and `--ds-radius-inner` (4px). It
625
+ takes `--border-field`, `--ds-radius-control` (6px by default) and clips its fill to the padding
626
+ box, so the border reads 3.45:1 on the filter popover in light and 4.04:1 under
627
+ `data-theme="dark"`. Nothing to change.
628
+ - **The HEX field in the `ds-color-picker` panel draws the field border and radius.** `.hex-input`
629
+ took `--border-default`, 1.31:1 on white, and `--ds-radius-inner` (4px). It takes
630
+ `--border-field` and `--ds-radius-control`, the radius of `ds-input` (6px by default), and clips
631
+ its fill to the padding box, so the border reads 3.45:1 on the panel in light and 4.04:1 under
632
+ `data-theme="dark"`. Nothing to change.
633
+ - **The type-to-confirm field of `ModalService.confirm` draws the field border.** `.confirm-input`
634
+ took `--border-default`, 1.31:1 on white, and read as a box rather than a field. It takes
635
+ `--border-field` and clips its fill to the padding box, as `ds-input` does, so the border reads
636
+ 3.45:1 on the modal in light and 4.19:1 under `data-theme="dark"`. Nothing to change.
637
+ - **A read-only `ds-input`, `ds-select` and `ds-textarea` draw one border, `--border-readonly`.**
638
+ A read-only input and textarea took `--border-field` and darkened it on hover, so they read as
639
+ editable beside a read-only select; the select took `--border-divider`, which is the colour of
640
+ `--surface-muted` and vanished on it. All three take the new `--border-readonly` at rest and on
641
+ hover, over the same `--surface-secondary` fill; focus still draws the focus border.
642
+ `--border-readonly` is `rgb(0 0 0 / 24%)` in light and `rgb(255 255 255 / 24%)` under
643
+ `data-theme="dark"`, about 1.8:1 on white and on `--surface-muted` in light and 2.2:1 in dark:
644
+ lighter than a field, stronger than a disabled one. `--ds-input-border` and
645
+ `--ds-input-border-hover` do not reach a read-only field. A full theme of your own sets
646
+ `--border-readonly`. Nothing else to change in your code, unless a screen must keep the old
647
+ read-only borders: set `--border-readonly: var(--border-divider)` on `ds-select`, and
648
+ `--border-readonly: var(--border-field)` on `ds-input` and `ds-textarea` for their resting
649
+ border. No hook restores the darker hover of a read-only input or textarea.
650
+ - **`ds-search` and `ds-number-stepper` strengthen their border under the pointer.** `ds-search`
651
+ hovered to its resting colour: its `--ds-search-border-hover` defaults to
652
+ `--ds-field-border-color-hover`, then `--border-field-hover`. `ds-number-stepper` had no hover on
653
+ its box: its border turns `--ds-number-stepper-border-color-hover` (new, default
654
+ `--border-field-hover`). With the translucent field border (see Changed), the hover border of
655
+ every field stands 2.15-2.26:1 from
656
+ the resting one in light and 1.85-1.98:1 under `data-theme="dark"`, where it was 1.08:1. The fill
657
+ does not change, and focus and disabled still win over hover. Nothing to change in your code,
658
+ unless a screen must keep a border that does not change on hover: set
659
+ `--ds-search-border-hover: var(--ds-search-border, var(--ds-field-border-color, var(--border-field)))`
660
+ on `ds-search` and
661
+ `--ds-number-stepper-border-color-hover: var(--ds-number-stepper-border-color, var(--border-field))`
662
+ on `ds-number-stepper`.
663
+ - **A new `ds-toast` no longer casts its shadow over the toast next to it while it fades in.** Once
664
+ the toasts around it had slid into place, the shadow of the arriving toast lay on top of its
665
+ neighbour until the fade ended, then dropped behind it. Each toast now paints in the stack's
666
+ order for the whole animation, so the shadow stays under the neighbour throughout. Nothing to
667
+ change.
668
+ - **A closing `ds-toast` slides out, and the toasts after it slide into its place.** It faded on
669
+ the spot, and once it was gone the toasts after it jumped into the freed space in one frame. Now
670
+ it moves `--ds-toast-enter-offset` toward the edge the `ds-toast-region` is pinned to while it
671
+ fades, over `--ds-toast-leave-duration`, and the remaining toasts then slide up (or down, for a
672
+ region at the bottom) over `--ds-toast-shift-duration`. A toast promoted from the queue in the
673
+ same moment no longer makes its neighbours jump back and forth. Under
674
+ `prefers-reduced-motion: reduce` the toast goes and the others move at once. Nothing to change.
675
+ - **The user's own `ds-chat-message` bubble keeps its white text readable on a pale `--primary`.**
676
+ `--ds-chat-message-user-bg-color` defaults to `oklab(from var(--primary) min(l, 0.55) a b)`,
677
+ where it was `var(--primary)`: the fill keeps the hue and chroma of `--primary` with its OKLCH
678
+ lightness capped at 0.55. A theme whose `--primary` is #93adc8 draws the bubble in
679
+ rgb(92, 116, 141), where white text reads 4.84:1 instead of 2.32:1. A `--primary` at or below
680
+ that lightness, the library brand among them, draws as before. The text stays
681
+ `--text-on-primary`. Nothing to change in your code, unless a screen must keep the bubble in
682
+ `--primary` itself: set `--ds-chat-message-user-bg-color: var(--primary)` on `ds-chat-message`.
683
+ - **A `tone="primary"` `ds-timeline-item` keeps its white marker glyph readable on a pale
684
+ `--accent`.** The marker fill and ring are `oklab(from var(--accent) min(l, 0.55) a b)`, where
685
+ they were `var(--accent)`: the hue and chroma of `--accent` with its OKLCH lightness capped at
686
+ 0.55. A theme whose `--accent` (by default `--primary`) is #93adc8 draws the marker in
687
+ rgb(92, 116, 141), where the white glyph reads 4.84:1 instead of 2.32:1. An `--accent` at or
688
+ below that lightness, the library brand among them, draws as before. Other tones and every
689
+ `status` are unchanged. Nothing to change in your code; no hook restores a marker filled with a
690
+ pale `--accent` itself.
691
+ - **A `ds-breadcrumbs` trail wider than its box ends its labels in an ellipsis.** The crumbs kept
692
+ their full width, so the trail was cut at the edge of the box in the middle of a letter. The
693
+ parent crumbs give up their width first, down to about two letters and «…» each, and share what
694
+ the current crumb leaves; in a box narrower still every crumb shrinks in proportion to its width,
695
+ the current one included, and ends in «…». A clipped label shows its full text in a tooltip on
696
+ hover or keyboard focus. A crumb without a link (`[clickable]="false"`, or an item without
697
+ `href`) truncates as a link does. A `flex-wrap: wrap` set on the trail's inner `nav` from outside
698
+ keeps the crumbs on one line, the parents truncated, where it moved them to a second line. For a
699
+ deep trail in a narrow box, set `maxItems` to fold the middle crumbs. Nothing to change.
700
+ - **A `ds-breadcrumbs` with `maxItems` set to `2` keeps the current crumb.** The trail showed the
701
+ first crumb and «… N more» and left out the current page; it shows the first crumb and the current
702
+ one, with no «… more» crumb between them. Only a `maxItems` of `2` changes. Nothing to
703
+ change in your code.
704
+ - **A hovered or pressed `ds-menu-item` keeps its description at 4.5:1 or more.** The second line
705
+ stayed `--text-tertiary` on the hover and press layers, where it read 4.04:1 and 3.40:1 in the
706
+ light theme and 3.58:1 pressed in the dark one. While the row is hovered or pressed it takes
707
+ `--text-secondary`. A `--ds-menu-item-description-color` you set applies in every state, as
708
+ before. Nothing to change.
709
+ - **`ds-tree` no longer grows its rows when its `nodes` or `expandedIds` change from code.** Rows
710
+ folded open whenever `nodes` or `expandedIds` changed after the tree's first render, so a tree
711
+ whose data or expanded ids arrived a moment later grew every row from zero. Only a toggle the user
712
+ makes (a click, a double click, Enter, Space or an arrow key) folds rows open and shut and turns
713
+ the chevron now; rows shown or hidden from code appear and go at once, and their chevron turns at
714
+ once. Nothing to change.
715
+ - **Selecting a `ds-tree` row keeps its label in place.** A selected row set its label in semibold,
716
+ so the wider glyphs pushed the text to the right and could cut a long label earlier. A selected row
717
+ keeps the regular weight and is marked by its background and text colour, as `ds-list-item` is.
718
+ Nothing to change in your code; no hook restores the semibold label.
719
+ - **A `dsTooltip` no longer opens on focus the keyboard did not move.** Picking an item with the
720
+ pointer in a `ds-menu` or `ds-popover` returns focus to the trigger, and the trigger's tooltip
721
+ opened on that focus and stayed, since no pointer left the trigger to close it. Every `dsTooltip`
722
+ now opens on focus only when the focused element matches `:focus-visible`. Hover and Tab open it
723
+ as before. Nothing to change.
724
+ - **A long `ds-tree` label ends in an ellipsis.** A row label wider than the tree ran past its edge
725
+ and made the container scroll sideways, because the grid track around each row grew to the
726
+ label's full width. The track shrinks with the tree, so the label is cut with «…»; a
727
+ shrink-to-fit tree is still as wide as its widest row. A `min-width: 0` or
728
+ `grid-template-columns` set on `ds-tree .row-shell` from outside is what the library now does
729
+ itself and can be removed; nothing else to change.
730
+ - **`ids-design-system/no-removed-inputs` reports `dsTooltipClippedLead` in a template.** A
731
+ template binding to `dsTooltipClippedLead`, an input `dsTooltip` no longer has, passed the rule.
732
+ It is reported now; delete the binding, since nothing replaces the input.
733
+ - **A brand that sets `--primary` once keeps it under `data-theme="dark"`.** The dark theme declared
734
+ `--primary` and the other input colours again, and won over a brand set on `:root` or
735
+ `[data-brand]`, so its buttons, tints, chips and focus ring were the library blue in dark. The
736
+ input colours (`--primary`, `--primary-on`, the `--primary-h/s/l`, `--secondary-h/s/l`,
737
+ `--tertiary-h/s/l`, `--error-h/s/l`, `--success-h/s/l` and `--warning-h/s/l` channels,
738
+ `--secondary`, `--tertiary`, `--secondary-on` and `--tertiary-on`) are declared once for both
739
+ themes, and each theme derives its shades from them. The default theme draws the same colours. A
740
+ brand that repeated `--primary` under `[data-theme='dark']` keeps working. Nothing to change in
741
+ your code, unless a screen must keep the library primary in dark under a brand: under
742
+ `:root[data-theme='dark']` set `--primary: var(--blue-600)` and `--primary-h`, `--primary-s` and
743
+ `--primary-l` to `var(--blue-h)`, `var(--blue-s)` and `var(--blue-l)`, and any other input your
744
+ brand sets back to its library value. Put it in a stylesheet loaded after the design system's,
745
+ where it wins on order.
746
+ - **A disabled neutral `ds-button` or `ds-icon-button` stays grey.** The disabled label, icon,
747
+ background and border took the hue of the accent at a fixed chroma, and a near-white accent has
748
+ no hue of its own, so the control drew pink: for `#f4f6fb` the label `rgb(178, 150, 157)`, the
749
+ background `rgb(247, 221, 228)`, the border `rgb(233, 199, 208)`. An accent below chroma 0.02
750
+ now gives chroma 0 and a coloured one keeps its capped chroma: the neutral reads the pure greys
751
+ `rgb(158, 158, 158)`, `rgb(228, 228, 228)` and `rgb(209, 209, 209)`, and a coloured accent such
752
+ as `#6d5cff` keeps its colours. Nothing to change in your code.
753
+ - **A `ds-dropzone` holding files centres its file list.** The list kept the 16px gap that sits
754
+ under the upload prompt, which the zone hides once it holds files, so the list sat 42px below the
755
+ zone's top edge and 26px above its bottom. It sits 26px from both now, and the zone is 16px
756
+ shorter. Nothing to change in your code.
757
+
3
758
  ## 1.1.2 — 2026-11-10
4
759
 
5
760
  ### Added