@ids-group-ltd/ids-design-system 0.14.7 → 0.15.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 (294) hide show
  1. package/CHANGELOG.md +735 -230
  2. package/components.md +64 -25
  3. package/docs/agent/INDEX.md +3 -1
  4. package/docs/agent/charts/ds-bar-chart.md +7 -4
  5. package/docs/agent/charts/ds-chart.md +1 -1
  6. package/docs/agent/charts/ds-column-chart.md +1 -1
  7. package/docs/agent/charts/ds-funnel-chart.md +1 -1
  8. package/docs/agent/charts/ds-pie-chart.md +1 -1
  9. package/docs/agent/charts/ds-waterfall-chart.md +2 -2
  10. package/docs/agent/feedback/ds-loading-overlay.md +2 -0
  11. package/docs/agent/feedback/ds-skeleton.md +1 -1
  12. package/docs/agent/forms/ds-button.md +2 -2
  13. package/docs/agent/forms/ds-date-picker.md +1 -0
  14. package/docs/agent/foundations/global-helper-classes.md +3 -3
  15. package/docs/agent/overlays/ds-bottom-sheet.md +1 -1
  16. package/docs/agent/overlays/ds-definition-term.md +10 -0
  17. package/docs/agent/overlays/ds-drawer.md +1 -1
  18. package/docs/agent/overlays/ds-info-hint.md +10 -0
  19. package/docs/agent/overlays/ds-menu.md +1 -1
  20. package/docs/agent/overlays/ds-modal-card.md +1 -1
  21. package/docs/agent/overlays/ds-modal.md +19 -1
  22. package/docs/agent/overlays/ds-tooltip-panel.md +1 -1
  23. package/docs/agent/overlays/ds-tooltip.md +3 -3
  24. package/docs/agent/tables/ds-table.md +3 -2
  25. package/eslint/deprecated-api.json +889 -0
  26. package/eslint/index.mjs +394 -0
  27. package/fesm2022/ids-group-ltd-ids-design-system-components-accordion.mjs +4 -4
  28. package/fesm2022/ids-group-ltd-ids-design-system-components-accordion.mjs.map +1 -1
  29. package/fesm2022/ids-group-ltd-ids-design-system-components-alert.mjs +2 -2
  30. package/fesm2022/ids-group-ltd-ids-design-system-components-alert.mjs.map +1 -1
  31. package/fesm2022/ids-group-ltd-ids-design-system-components-app-layout.mjs +6 -12
  32. package/fesm2022/ids-group-ltd-ids-design-system-components-app-layout.mjs.map +1 -1
  33. package/fesm2022/ids-group-ltd-ids-design-system-components-auth-layout.mjs +2 -2
  34. package/fesm2022/ids-group-ltd-ids-design-system-components-auth-layout.mjs.map +1 -1
  35. package/fesm2022/ids-group-ltd-ids-design-system-components-autocomplete.mjs +19 -7
  36. package/fesm2022/ids-group-ltd-ids-design-system-components-autocomplete.mjs.map +1 -1
  37. package/fesm2022/ids-group-ltd-ids-design-system-components-avatar-group.mjs +2 -2
  38. package/fesm2022/ids-group-ltd-ids-design-system-components-avatar-group.mjs.map +1 -1
  39. package/fesm2022/ids-group-ltd-ids-design-system-components-avatar.mjs +2 -2
  40. package/fesm2022/ids-group-ltd-ids-design-system-components-avatar.mjs.map +1 -1
  41. package/fesm2022/ids-group-ltd-ids-design-system-components-badge.mjs +2 -2
  42. package/fesm2022/ids-group-ltd-ids-design-system-components-badge.mjs.map +1 -1
  43. package/fesm2022/ids-group-ltd-ids-design-system-components-banner.mjs +2 -2
  44. package/fesm2022/ids-group-ltd-ids-design-system-components-banner.mjs.map +1 -1
  45. package/fesm2022/ids-group-ltd-ids-design-system-components-bar-chart.mjs +169 -37
  46. package/fesm2022/ids-group-ltd-ids-design-system-components-bar-chart.mjs.map +1 -1
  47. package/fesm2022/ids-group-ltd-ids-design-system-components-bar.mjs +2 -2
  48. package/fesm2022/ids-group-ltd-ids-design-system-components-bar.mjs.map +1 -1
  49. package/fesm2022/ids-group-ltd-ids-design-system-components-bottom-sheet.mjs +2 -2
  50. package/fesm2022/ids-group-ltd-ids-design-system-components-bottom-sheet.mjs.map +1 -1
  51. package/fesm2022/ids-group-ltd-ids-design-system-components-breadcrumbs.mjs +2 -2
  52. package/fesm2022/ids-group-ltd-ids-design-system-components-breadcrumbs.mjs.map +1 -1
  53. package/fesm2022/ids-group-ltd-ids-design-system-components-button-group.mjs +2 -2
  54. package/fesm2022/ids-group-ltd-ids-design-system-components-button-group.mjs.map +1 -1
  55. package/fesm2022/ids-group-ltd-ids-design-system-components-button.mjs +2 -2
  56. package/fesm2022/ids-group-ltd-ids-design-system-components-button.mjs.map +1 -1
  57. package/fesm2022/ids-group-ltd-ids-design-system-components-calendar-day.mjs +2 -2
  58. package/fesm2022/ids-group-ltd-ids-design-system-components-calendar-day.mjs.map +1 -1
  59. package/fesm2022/ids-group-ltd-ids-design-system-components-card.mjs +2 -2
  60. package/fesm2022/ids-group-ltd-ids-design-system-components-card.mjs.map +1 -1
  61. package/fesm2022/ids-group-ltd-ids-design-system-components-chart-data-table.mjs +2 -2
  62. package/fesm2022/ids-group-ltd-ids-design-system-components-chart-data-table.mjs.map +1 -1
  63. package/fesm2022/ids-group-ltd-ids-design-system-components-chart-legend.mjs +2 -2
  64. package/fesm2022/ids-group-ltd-ids-design-system-components-chart-legend.mjs.map +1 -1
  65. package/fesm2022/ids-group-ltd-ids-design-system-components-chart-tooltip.mjs +195 -27
  66. package/fesm2022/ids-group-ltd-ids-design-system-components-chart-tooltip.mjs.map +1 -1
  67. package/fesm2022/ids-group-ltd-ids-design-system-components-chart.mjs +23 -20
  68. package/fesm2022/ids-group-ltd-ids-design-system-components-chart.mjs.map +1 -1
  69. package/fesm2022/ids-group-ltd-ids-design-system-components-checkbox.mjs +2 -2
  70. package/fesm2022/ids-group-ltd-ids-design-system-components-checkbox.mjs.map +1 -1
  71. package/fesm2022/ids-group-ltd-ids-design-system-components-color-picker.mjs +2 -2
  72. package/fesm2022/ids-group-ltd-ids-design-system-components-color-picker.mjs.map +1 -1
  73. package/fesm2022/ids-group-ltd-ids-design-system-components-column-chart.mjs +9 -9
  74. package/fesm2022/ids-group-ltd-ids-design-system-components-column-chart.mjs.map +1 -1
  75. package/fesm2022/ids-group-ltd-ids-design-system-components-date-picker.mjs +2 -2
  76. package/fesm2022/ids-group-ltd-ids-design-system-components-date-picker.mjs.map +1 -1
  77. package/fesm2022/ids-group-ltd-ids-design-system-components-definition-term.mjs +107 -0
  78. package/fesm2022/ids-group-ltd-ids-design-system-components-definition-term.mjs.map +1 -0
  79. package/fesm2022/ids-group-ltd-ids-design-system-components-description-list.mjs +4 -4
  80. package/fesm2022/ids-group-ltd-ids-design-system-components-description-list.mjs.map +1 -1
  81. package/fesm2022/ids-group-ltd-ids-design-system-components-divider.mjs +2 -2
  82. package/fesm2022/ids-group-ltd-ids-design-system-components-divider.mjs.map +1 -1
  83. package/fesm2022/ids-group-ltd-ids-design-system-components-drawer.mjs +5 -15
  84. package/fesm2022/ids-group-ltd-ids-design-system-components-drawer.mjs.map +1 -1
  85. package/fesm2022/ids-group-ltd-ids-design-system-components-dropzone.mjs +2 -2
  86. package/fesm2022/ids-group-ltd-ids-design-system-components-dropzone.mjs.map +1 -1
  87. package/fesm2022/ids-group-ltd-ids-design-system-components-empty-state.mjs +2 -2
  88. package/fesm2022/ids-group-ltd-ids-design-system-components-empty-state.mjs.map +1 -1
  89. package/fesm2022/ids-group-ltd-ids-design-system-components-field-group.mjs +2 -2
  90. package/fesm2022/ids-group-ltd-ids-design-system-components-field-group.mjs.map +1 -1
  91. package/fesm2022/ids-group-ltd-ids-design-system-components-field-message.mjs +2 -2
  92. package/fesm2022/ids-group-ltd-ids-design-system-components-field-message.mjs.map +1 -1
  93. package/fesm2022/ids-group-ltd-ids-design-system-components-filter-bar.mjs +2 -2
  94. package/fesm2022/ids-group-ltd-ids-design-system-components-filter-bar.mjs.map +1 -1
  95. package/fesm2022/ids-group-ltd-ids-design-system-components-funnel-chart.mjs +11 -8
  96. package/fesm2022/ids-group-ltd-ids-design-system-components-funnel-chart.mjs.map +1 -1
  97. package/fesm2022/ids-group-ltd-ids-design-system-components-heatmap-chart.mjs +4 -3
  98. package/fesm2022/ids-group-ltd-ids-design-system-components-heatmap-chart.mjs.map +1 -1
  99. package/fesm2022/ids-group-ltd-ids-design-system-components-icon-button.mjs +2 -2
  100. package/fesm2022/ids-group-ltd-ids-design-system-components-icon-button.mjs.map +1 -1
  101. package/fesm2022/ids-group-ltd-ids-design-system-components-info-hint.mjs +44 -0
  102. package/fesm2022/ids-group-ltd-ids-design-system-components-info-hint.mjs.map +1 -0
  103. package/fesm2022/ids-group-ltd-ids-design-system-components-input.mjs +2 -2
  104. package/fesm2022/ids-group-ltd-ids-design-system-components-input.mjs.map +1 -1
  105. package/fesm2022/ids-group-ltd-ids-design-system-components-layout.mjs +6 -6
  106. package/fesm2022/ids-group-ltd-ids-design-system-components-layout.mjs.map +1 -1
  107. package/fesm2022/ids-group-ltd-ids-design-system-components-line-chart.mjs +10 -4
  108. package/fesm2022/ids-group-ltd-ids-design-system-components-line-chart.mjs.map +1 -1
  109. package/fesm2022/ids-group-ltd-ids-design-system-components-list.mjs +4 -4
  110. package/fesm2022/ids-group-ltd-ids-design-system-components-list.mjs.map +1 -1
  111. package/fesm2022/ids-group-ltd-ids-design-system-components-loading-overlay.mjs +2 -2
  112. package/fesm2022/ids-group-ltd-ids-design-system-components-loading-overlay.mjs.map +1 -1
  113. package/fesm2022/ids-group-ltd-ids-design-system-components-menu.mjs +136 -29
  114. package/fesm2022/ids-group-ltd-ids-design-system-components-menu.mjs.map +1 -1
  115. package/fesm2022/ids-group-ltd-ids-design-system-components-modal.mjs +21 -26
  116. package/fesm2022/ids-group-ltd-ids-design-system-components-modal.mjs.map +1 -1
  117. package/fesm2022/ids-group-ltd-ids-design-system-components-multi-select.mjs +19 -7
  118. package/fesm2022/ids-group-ltd-ids-design-system-components-multi-select.mjs.map +1 -1
  119. package/fesm2022/ids-group-ltd-ids-design-system-components-number-stepper.mjs +2 -2
  120. package/fesm2022/ids-group-ltd-ids-design-system-components-number-stepper.mjs.map +1 -1
  121. package/fesm2022/ids-group-ltd-ids-design-system-components-otp-input.mjs +2 -2
  122. package/fesm2022/ids-group-ltd-ids-design-system-components-otp-input.mjs.map +1 -1
  123. package/fesm2022/ids-group-ltd-ids-design-system-components-page-footer.mjs +2 -2
  124. package/fesm2022/ids-group-ltd-ids-design-system-components-page-footer.mjs.map +1 -1
  125. package/fesm2022/ids-group-ltd-ids-design-system-components-page-header.mjs +2 -2
  126. package/fesm2022/ids-group-ltd-ids-design-system-components-page-header.mjs.map +1 -1
  127. package/fesm2022/ids-group-ltd-ids-design-system-components-pagination.mjs +2 -2
  128. package/fesm2022/ids-group-ltd-ids-design-system-components-pagination.mjs.map +1 -1
  129. package/fesm2022/ids-group-ltd-ids-design-system-components-password-rules.mjs +2 -2
  130. package/fesm2022/ids-group-ltd-ids-design-system-components-password-rules.mjs.map +1 -1
  131. package/fesm2022/ids-group-ltd-ids-design-system-components-pie-chart.mjs +8 -6
  132. package/fesm2022/ids-group-ltd-ids-design-system-components-pie-chart.mjs.map +1 -1
  133. package/fesm2022/ids-group-ltd-ids-design-system-components-popover.mjs +2 -2
  134. package/fesm2022/ids-group-ltd-ids-design-system-components-popover.mjs.map +1 -1
  135. package/fesm2022/ids-group-ltd-ids-design-system-components-radio-group.mjs +4 -4
  136. package/fesm2022/ids-group-ltd-ids-design-system-components-radio-group.mjs.map +1 -1
  137. package/fesm2022/ids-group-ltd-ids-design-system-components-scatter-chart.mjs +19 -5
  138. package/fesm2022/ids-group-ltd-ids-design-system-components-scatter-chart.mjs.map +1 -1
  139. package/fesm2022/ids-group-ltd-ids-design-system-components-search.mjs +2 -2
  140. package/fesm2022/ids-group-ltd-ids-design-system-components-search.mjs.map +1 -1
  141. package/fesm2022/ids-group-ltd-ids-design-system-components-segmented.mjs +2 -2
  142. package/fesm2022/ids-group-ltd-ids-design-system-components-segmented.mjs.map +1 -1
  143. package/fesm2022/ids-group-ltd-ids-design-system-components-select.mjs +21 -7
  144. package/fesm2022/ids-group-ltd-ids-design-system-components-select.mjs.map +1 -1
  145. package/fesm2022/ids-group-ltd-ids-design-system-components-sidenav-footer.mjs +2 -2
  146. package/fesm2022/ids-group-ltd-ids-design-system-components-sidenav-footer.mjs.map +1 -1
  147. package/fesm2022/ids-group-ltd-ids-design-system-components-sidenav.mjs +6 -6
  148. package/fesm2022/ids-group-ltd-ids-design-system-components-sidenav.mjs.map +1 -1
  149. package/fesm2022/ids-group-ltd-ids-design-system-components-skeleton.mjs +2 -2
  150. package/fesm2022/ids-group-ltd-ids-design-system-components-skeleton.mjs.map +1 -1
  151. package/fesm2022/ids-group-ltd-ids-design-system-components-slider.mjs +2 -2
  152. package/fesm2022/ids-group-ltd-ids-design-system-components-slider.mjs.map +1 -1
  153. package/fesm2022/ids-group-ltd-ids-design-system-components-sparkline.mjs +2 -2
  154. package/fesm2022/ids-group-ltd-ids-design-system-components-sparkline.mjs.map +1 -1
  155. package/fesm2022/ids-group-ltd-ids-design-system-components-spinner.mjs +2 -2
  156. package/fesm2022/ids-group-ltd-ids-design-system-components-spinner.mjs.map +1 -1
  157. package/fesm2022/ids-group-ltd-ids-design-system-components-split-button.mjs +2 -2
  158. package/fesm2022/ids-group-ltd-ids-design-system-components-split-button.mjs.map +1 -1
  159. package/fesm2022/ids-group-ltd-ids-design-system-components-stat.mjs +2 -2
  160. package/fesm2022/ids-group-ltd-ids-design-system-components-stat.mjs.map +1 -1
  161. package/fesm2022/ids-group-ltd-ids-design-system-components-status-dot.mjs +2 -2
  162. package/fesm2022/ids-group-ltd-ids-design-system-components-status-dot.mjs.map +1 -1
  163. package/fesm2022/ids-group-ltd-ids-design-system-components-stepper.mjs +2 -2
  164. package/fesm2022/ids-group-ltd-ids-design-system-components-stepper.mjs.map +1 -1
  165. package/fesm2022/ids-group-ltd-ids-design-system-components-switch.mjs +2 -2
  166. package/fesm2022/ids-group-ltd-ids-design-system-components-switch.mjs.map +1 -1
  167. package/fesm2022/ids-group-ltd-ids-design-system-components-table-columns.mjs +4 -4
  168. package/fesm2022/ids-group-ltd-ids-design-system-components-table-columns.mjs.map +1 -1
  169. package/fesm2022/ids-group-ltd-ids-design-system-components-table.mjs +223 -8
  170. package/fesm2022/ids-group-ltd-ids-design-system-components-table.mjs.map +1 -1
  171. package/fesm2022/ids-group-ltd-ids-design-system-components-tabs.mjs +2 -2
  172. package/fesm2022/ids-group-ltd-ids-design-system-components-tabs.mjs.map +1 -1
  173. package/fesm2022/ids-group-ltd-ids-design-system-components-tag.mjs +2 -2
  174. package/fesm2022/ids-group-ltd-ids-design-system-components-tag.mjs.map +1 -1
  175. package/fesm2022/ids-group-ltd-ids-design-system-components-textarea.mjs +2 -2
  176. package/fesm2022/ids-group-ltd-ids-design-system-components-textarea.mjs.map +1 -1
  177. package/fesm2022/ids-group-ltd-ids-design-system-components-time-picker.mjs +4 -4
  178. package/fesm2022/ids-group-ltd-ids-design-system-components-time-picker.mjs.map +1 -1
  179. package/fesm2022/ids-group-ltd-ids-design-system-components-timeline.mjs +4 -4
  180. package/fesm2022/ids-group-ltd-ids-design-system-components-timeline.mjs.map +1 -1
  181. package/fesm2022/ids-group-ltd-ids-design-system-components-toast.mjs +4 -4
  182. package/fesm2022/ids-group-ltd-ids-design-system-components-toast.mjs.map +1 -1
  183. package/fesm2022/ids-group-ltd-ids-design-system-components-toggle-button.mjs +2 -2
  184. package/fesm2022/ids-group-ltd-ids-design-system-components-toggle-button.mjs.map +1 -1
  185. package/fesm2022/ids-group-ltd-ids-design-system-components-tooltip.mjs +410 -145
  186. package/fesm2022/ids-group-ltd-ids-design-system-components-tooltip.mjs.map +1 -1
  187. package/fesm2022/ids-group-ltd-ids-design-system-components-topbar.mjs +2 -2
  188. package/fesm2022/ids-group-ltd-ids-design-system-components-topbar.mjs.map +1 -1
  189. package/fesm2022/ids-group-ltd-ids-design-system-components-tree.mjs +2 -2
  190. package/fesm2022/ids-group-ltd-ids-design-system-components-tree.mjs.map +1 -1
  191. package/fesm2022/ids-group-ltd-ids-design-system-components-w3w.mjs +2 -2
  192. package/fesm2022/ids-group-ltd-ids-design-system-components-w3w.mjs.map +1 -1
  193. package/fesm2022/ids-group-ltd-ids-design-system-components-waterfall-chart.mjs +14 -11
  194. package/fesm2022/ids-group-ltd-ids-design-system-components-waterfall-chart.mjs.map +1 -1
  195. package/fesm2022/ids-group-ltd-ids-design-system-components.mjs +86 -2
  196. package/fesm2022/ids-group-ltd-ids-design-system-components.mjs.map +1 -1
  197. package/fesm2022/ids-group-ltd-ids-design-system-core.mjs +18 -81
  198. package/fesm2022/ids-group-ltd-ids-design-system-core.mjs.map +1 -1
  199. package/fesm2022/ids-group-ltd-ids-design-system-icons.mjs +2 -2
  200. package/fesm2022/ids-group-ltd-ids-design-system-icons.mjs.map +1 -1
  201. package/fesm2022/ids-group-ltd-ids-design-system-overlay.mjs +1 -0
  202. package/fesm2022/ids-group-ltd-ids-design-system-overlay.mjs.map +1 -1
  203. package/fesm2022/ids-group-ltd-ids-design-system.mjs +2 -0
  204. package/fesm2022/ids-group-ltd-ids-design-system.mjs.map +1 -1
  205. package/migrations/0.10.0.json +79 -21
  206. package/migrations/0.10.1.json +38 -21
  207. package/migrations/0.10.2.json +44 -7
  208. package/migrations/0.10.3.json +7 -5
  209. package/migrations/0.11.0.json +10 -7
  210. package/migrations/0.11.1.json +25 -14
  211. package/migrations/0.11.2.json +3 -3
  212. package/migrations/0.11.3.json +9 -6
  213. package/migrations/0.11.4.json +13 -12
  214. package/migrations/0.12.1.json +41 -14
  215. package/migrations/0.12.2.json +7 -6
  216. package/migrations/0.12.3.json +3 -3
  217. package/migrations/0.13.0.json +11 -11
  218. package/migrations/0.13.1.json +60 -8
  219. package/migrations/0.13.2.json +98 -44
  220. package/migrations/0.13.3.json +46 -16
  221. package/migrations/0.13.4.json +23 -22
  222. package/migrations/0.14.0.json +5 -5
  223. package/migrations/0.14.1.json +5 -5
  224. package/migrations/0.14.2.json +1 -1
  225. package/migrations/0.14.4.json +6 -5
  226. package/migrations/0.14.5.json +13 -7
  227. package/migrations/0.14.6.json +2 -2
  228. package/migrations/0.14.8.json +56 -0
  229. package/migrations/0.15.0.json +999 -0
  230. package/migrations/0.2.0.json +2 -2
  231. package/migrations/0.3.0.json +43 -6
  232. package/migrations/0.4.0.json +95 -13
  233. package/migrations/0.5.0.json +116 -10
  234. package/migrations/0.5.1.json +97 -11
  235. package/migrations/0.6.0.json +30 -1
  236. package/migrations/0.6.1.json +22 -1
  237. package/migrations/0.6.2.json +8 -4
  238. package/migrations/0.6.3.json +17 -5
  239. package/migrations/0.7.0.json +58 -9
  240. package/migrations/0.7.1.json +62 -8
  241. package/migrations/0.8.0.json +60 -12
  242. package/migrations/0.9.0.json +68 -25
  243. package/migrations/0.9.1.json +1 -1
  244. package/migrations/README.md +57 -3
  245. package/package.json +19 -1
  246. package/schematics/check-overrides/index.cjs +4 -11
  247. package/schematics/check-overrides/scan.cjs +12 -1
  248. package/schematics/check-overrides/surface.json +51 -10
  249. package/schematics/ng-add/index.cjs +7 -1
  250. package/stylelint/deprecated-tokens.json +2697 -0
  251. package/stylelint/index.mjs +94 -0
  252. package/stylelint/since-version.mjs +26 -0
  253. package/styles/_chart-motion.scss +3 -9
  254. package/styles/_chip-row.scss +5 -2
  255. package/styles/_clear-button.scss +2 -0
  256. package/styles/_component-base.scss +56 -0
  257. package/styles/_dismiss-button.scss +16 -0
  258. package/styles/_dropdown-overlay.scss +19 -0
  259. package/styles/_focus.scss +4 -1
  260. package/styles/_overlay-motion.scss +4 -6
  261. package/styles/_pinned.scss +43 -0
  262. package/styles/_skeleton-shimmer.scss +2 -8
  263. package/styles/_table-controls.scss +4 -0
  264. package/styles/_target.scss +40 -0
  265. package/styles/_text-clip.scss +23 -4
  266. package/styles/_tokens.scss +0 -1
  267. package/styles/_typography.scss +2 -0
  268. package/styles/_visually-hidden.scss +2 -0
  269. package/styles/ds.scss +0 -1
  270. package/themes/README.md +7 -7
  271. package/types/ids-group-ltd-ids-design-system-components-autocomplete.d.ts +4 -1
  272. package/types/ids-group-ltd-ids-design-system-components-bar-chart.d.ts +74 -4
  273. package/types/ids-group-ltd-ids-design-system-components-button.d.ts +2 -2
  274. package/types/ids-group-ltd-ids-design-system-components-chart-tooltip.d.ts +40 -4
  275. package/types/ids-group-ltd-ids-design-system-components-chart.d.ts +8 -3
  276. package/types/ids-group-ltd-ids-design-system-components-column-chart.d.ts +4 -3
  277. package/types/ids-group-ltd-ids-design-system-components-definition-term.d.ts +22 -0
  278. package/types/ids-group-ltd-ids-design-system-components-drawer.d.ts +0 -1
  279. package/types/ids-group-ltd-ids-design-system-components-funnel-chart.d.ts +7 -3
  280. package/types/ids-group-ltd-ids-design-system-components-heatmap-chart.d.ts +1 -0
  281. package/types/ids-group-ltd-ids-design-system-components-info-hint.d.ts +14 -0
  282. package/types/ids-group-ltd-ids-design-system-components-line-chart.d.ts +5 -0
  283. package/types/ids-group-ltd-ids-design-system-components-menu.d.ts +8 -3
  284. package/types/ids-group-ltd-ids-design-system-components-modal.d.ts +0 -2
  285. package/types/ids-group-ltd-ids-design-system-components-multi-select.d.ts +4 -1
  286. package/types/ids-group-ltd-ids-design-system-components-pie-chart.d.ts +5 -3
  287. package/types/ids-group-ltd-ids-design-system-components-scatter-chart.d.ts +13 -3
  288. package/types/ids-group-ltd-ids-design-system-components-select.d.ts +4 -1
  289. package/types/ids-group-ltd-ids-design-system-components-table.d.ts +30 -3
  290. package/types/ids-group-ltd-ids-design-system-components-tooltip.d.ts +48 -17
  291. package/types/ids-group-ltd-ids-design-system-components-waterfall-chart.d.ts +6 -2
  292. package/types/ids-group-ltd-ids-design-system-components.d.ts +26 -2
  293. package/types/ids-group-ltd-ids-design-system-core.d.ts +7 -11
  294. package/types/ids-group-ltd-ids-design-system.d.ts +3 -1
@@ -25,7 +25,7 @@
25
25
  "old": "ds-search",
26
26
  "new": null,
27
27
  "action": "Only if you re-added a ring to that button yourself — that rule can go. (delete list: search-clear-button-focus-rule)",
28
- "note": "0.10.2's ring fix silenced the base indicator with a shell-wide reset, which also hit `.search-clear`, a `tabindex=0` tab stop: tabbing from the input to the clear button changed nothing on screen — box-shadow, outline, border, background and colour all identical — so a keyboard user could not tell it had focus. A WCAG 2.4.7 failure. Every shell names the single control it silences now.",
28
+ "note": "0.10.2's ring fix silenced the base indicator with a shell-wide reset, which also hit `.search-clear`, a `tabindex=0` tab stop: in every shadow-based focus style, tabbing from the input to the clear button changed nothing on screen — box-shadow, outline, border, background and colour all identical (only `data-focus=\"outline\"` and forced colours still drew an outline) — so a keyboard user could not tell it had focus. A WCAG 2.4.7 failure. Every shell names the single control it silences now.",
29
29
  "surface": "style",
30
30
  "verify": "Type into a ds-search so the clear button appears, then Tab: the × shows its own ring on top of the field halo. Same for a chip close button in ds-autocomplete or ds-multi-select, and for the arrows in ds-number-stepper.",
31
31
  "searchHints": [
@@ -40,13 +40,15 @@
40
40
  "kind": "behavior",
41
41
  "old": "ds-date-picker, ds-time-picker",
42
42
  "new": null,
43
- "action": "Only if you worked around either: a rule adding a ring to `.period-trigger` or `.time-action`, or a `border-radius` forced onto `.time-panel`, can go.",
43
+ "action": "Only if you worked around either: a rule adding a ring to `.period-trigger`, `.picker-cell`, `.preset-btn` or `.time-action`, or a `border-radius` forced onto `.time-panel`, can go.",
44
44
  "pitfall": "The mechanism is worth knowing before you style a DS panel yourself: a private `--_*` token declared on `:host` does NOT reach a panel the CDK has portaled out of that host, and an unresolvable `var()` silently becomes the property's initial value — `none` for box-shadow, `0` for border-radius. Read the PUBLIC `--ds-*` token from outside instead.",
45
- "note": "Two tabbable buttons inside the portaled panels had no focus indicator at all, and one panel had square corners: both read a private focus-shadow token declared on the host, and with `outline: none` beside it nothing was left.",
45
+ "note": "Tabbable buttons inside both portaled panels had no focus indicator at all - the date-picker's month/year header, month and year cells and preset buttons, and the time-picker's action button - and one panel had square corners: all read a private focus-shadow token declared on the host, and with `outline: none` beside it nothing was left.",
46
46
  "surface": "style",
47
- "verify": "Open the ds-date-picker calendar and Tab to the month/year header: it shows a focus ring. Open the ds-time-picker panel and Tab to its action button: same. The time-picker panel has rounded corners.",
47
+ "verify": "Open the ds-date-picker calendar and Tab to the month/year header, a month or year cell and a preset button: each shows a focus ring. Open the ds-time-picker panel and Tab to its action button: same. The time-picker panel has rounded corners.",
48
48
  "searchHints": [
49
49
  "period-trigger",
50
+ "picker-cell",
51
+ "preset-btn",
50
52
  "time-action",
51
53
  "time-panel",
52
54
  "--ds-date-picker-focus-shadow",
@@ -59,7 +61,7 @@
59
61
  "If you add a component that paints its own ring on :focus-within, suppress the base rule on the control it speaks for - `outline: 0` cannot do it, because the base indicator is a box-shadow.",
60
62
  "Two authoring mixins are now documented for consumers building their own composite controls: `focus.owns-the-focus-ring($control)` in styles/focus, and `text-clip.single-line-ellipsis` in styles/text-clip. Both are opt-in - no existing code changes.",
61
63
  "A private --_* token declared on :host does not reach a CDK-portaled panel, and an unresolvable var() silently becomes the property's initial value - none for box-shadow, 0 for border-radius. If you style a DS panel from your own CSS, read the PUBLIC --ds-* token there, not the private one.",
62
- "Fourteen public tokens were always overridable but never reached the token reference: --ds-container-pad-x, --ds-multi-select-border-color (+-focus), --ds-segmented-selected-bg-color / -label-color / --ds-segmented-radius, --ds-time-picker-option-bg-color-selected / -text-color-selected / -bg-color-hover, --ds-time-picker-trigger-bg-color / -border / -color, --ds-field-message-icon-offset, --ds-time-picker-focus-shadow. Nothing changed in the components - if you hand-rolled around one of these because it looked unsupported, the override is supported and is the way to do it."
64
+ "Fourteen public tokens were always overridable but never reached the token reference: --ds-container-pad-x, --ds-multi-select-border-color (+-focus), --ds-segmented-selected-bg-color / -label-color / --ds-segmented-radius, --ds-time-picker-option-bg-color-selected / -text-color-selected / -bg-color-hover, --ds-time-picker-trigger-bg-color / -border / -color, --ds-field-message-icon-offset, --ds-time-picker-focus-shadow (it reaches the time-picker panel's action button only from this release - see portaled-panel-focus-indicator). Otherwise nothing changed in the components - if you hand-rolled around one of these because it looked unsupported, the override is supported and is the way to do it."
63
65
  ],
64
66
  "deleteList": [
65
67
  {
@@ -8,10 +8,10 @@
8
8
  "new": null,
9
9
  "action": "Only if you extend one of these and already declare one of the GAINED names: rename yours, or add `override` if you meant to replace ours. Build after upgrading — the compiler enumerates every collision.",
10
10
  "appliesWhen": "Subclassing a DS component is unsupported, but consumers do it. Template users of the `<ds-…>` elements need nothing.",
11
- "pitfall": "`protected` is no protection: a redeclared protected member collides exactly as a public one does. Six members — `hint`, `error`, `warning`, `messageIcon`, `reserveMessage` and `reserveMessageResolved` — moved one level up between two internal base classes, so a member-by-member diff can report them as lost and regained. They still reach your subclass with the same names, types and defaults, and an existing `override` still works because it accepts a member from any ancestor. Nothing to do for those; only the GAINED names below can collide.",
12
- "note": "Compared against 0.10.3. Gained: TableComponent `cellLink`; ButtonComponent `disabledReason`, `ariaDescribedBy`, `softDisabled`, `message`, `fieldMessage`, `hasMessageRow`, `describedBy`, `hintId`, `reasonId`, `uid`; IconButtonComponent `ariaDescribedBy`; SidenavComponent `brandRoute`, `brandLinkLabel` and the protected `brandAriaLabel`; CheckboxComponent and RadioGroupComponent each the protected `controlState`. TS4114 asks for an `override` modifier, TS2415 fires where the signature differs.",
11
+ "pitfall": "`protected` is no protection: a redeclared protected member collides exactly as a public one does. Six members — `hint`, `error`, `warning`, `messageIcon`, `reserveMessage` and `reserveMessageResolved` — moved one level up between two internal base classes for the FIELD components, so a member-by-member diff can report them as lost and regained. They still reach your subclass with the same names, types and defaults, and an existing `override` still works because it accepts a member from any ancestor. Nothing to do for those on a field; only the GAINED names below can collide. ButtonComponent had none of the six before and gains them all, so on a ButtonComponent subclass they collide like any other gained name.",
12
+ "note": "Compared against 0.10.3. Gained: TableComponent `cellLink`; ButtonComponent `hint`, `error`, `warning`, `messageIcon`, `reserveMessage`, `reserveMessageResolved` (it extends the internal message base now), plus `disabledReason`, `ariaDescribedBy`, `softDisabled`, `message`, `fieldMessage`, `hasMessageRow`, `describedBy`, `hintId`, `reasonId`, `uid`; IconButtonComponent `ariaDescribedBy`; SidenavComponent `brandRoute`, `brandLinkLabel` and the protected `brandAriaLabel`; CheckboxComponent and RadioGroupComponent each the protected `controlState`. TS4114 asks for an `override` modifier, TS2416 fires where the signature differs.",
13
13
  "surface": "typescript",
14
- "verify": "Build your app: no TS4114 or TS2415 is raised against a class that extends a DS component.",
14
+ "verify": "Build your app: no TS4114 or TS2416 is raised against a class that extends a DS component.",
15
15
  "searchHints": [
16
16
  "extends TableComponent",
17
17
  "extends ButtonComponent",
@@ -22,7 +22,7 @@
22
22
  "softDisabled",
23
23
  "hasMessageRow",
24
24
  "TS4114",
25
- "TS2415",
25
+ "TS2416",
26
26
  "extends SidenavComponent",
27
27
  "brandRoute",
28
28
  "brandLinkLabel",
@@ -35,13 +35,17 @@
35
35
  "extends TableComponent",
36
36
  "extends ButtonComponent",
37
37
  "extends IconButtonComponent",
38
+ "extends CheckboxComponent",
39
+ "CheckboxComponent",
40
+ "extends RadioGroupComponent",
41
+ "RadioGroupComponent",
38
42
  "cellLink",
39
43
  "disabledReason",
40
44
  "ariaDescribedBy",
41
45
  "softDisabled",
42
46
  "hasMessageRow",
43
47
  "TS4114",
44
- "TS2415",
48
+ "TS2416",
45
49
  "extends SidenavComponent",
46
50
  "brandRoute",
47
51
  "brandLinkLabel",
@@ -95,11 +99,10 @@
95
99
  }
96
100
  ],
97
101
  "informational": [
98
- "`--ds-field-message-icon-offset` and `--ds-time-picker-focus-shadow` are public, overridable, and listed in the token reference - the supported way to retune either. Nothing changed in the components - if you hand-rolled around either because it looked unsupported, the override is supported and is the way to do it. They belong with the twelve named under 0.10.3.",
99
102
  "ds-table columns take a new optional `link: (row) => string | readonly unknown[] | null`. Nothing changes on a column that does not set it; see the exported-class-members-grew item if you SUBCLASS TableComponent. Where you compensated for an invisible row click by repeating the destination as a 'View Details' item in the row overflow menu, that item can go: give the name column `link` instead and the destination becomes a real <a> - tabbable as a link, Ctrl/Cmd-clickable, and announced as a link rather than as a table row. If you also set `rowInteractive`, note the pair costs two tab stops per row; the link alone is usually the better trade on a long list. (delete list: row-menu-view-details-duplicate)",
100
103
  "ds-card gains --ds-card-overflow, default visible. Opt-in on purpose: clipping a card also cuts the focus ring off any child at its edge, so where a clipped card holds focusable content pair it with data-focus=\"inset\".",
101
104
  "ds-button gains --ds-button-shadow and --ds-button-shadow-hover, both default none. Purely additive; -shadow-hover falls back to -shadow, and the focus/pressed hooks still win in their own states.",
102
- "ds-button gains disabledReason, hint, warning, error, messageIcon, reserveMessage and ariaDescribedBy; ds-icon-button gains ariaDescribedBy. All additive - a button that sets none of them is byte-identical in behaviour and layout. Two things worth knowing before you use them. (1) disabledReason CHANGES HOW THE BUTTON IS DISABLED: with a reason set the button carries aria-disabled=\"true\" instead of the native disabled attribute, so it stays focusable and the reason is announced as its accessible description; the click is swallowed in the handler, so (pressed) still never fires. If you have CSS keyed on `ds-button button[disabled]` or `:disabled`, add `[aria-disabled=\"true\"]` - the library's own disabled paint already covers both. (2) hint/warning/error are for the OTHER kind of refusal: a temporary one the user lifts by filling the form in. Do not disable the button for those - leave it live, judge validity in the submit handler, and let the message line explain. A message-bearing button becomes a column, and since the host shrinks to fit, a message longer than the label widens the pair, button included. (delete list: button-disabled-reason-tooltip)",
105
+ "ds-button gains disabledReason, hint, warning, error, messageIcon, reserveMessage and ariaDescribedBy; ds-icon-button gains ariaDescribedBy. All additive - a button that sets none of them is byte-identical in behaviour and layout, unless the app sets `DS_CONFIG.field.reserveMessage: true`: reserveMessage falls back to it, so every such button then reserves an empty message line and its host becomes a column. Set [reserveMessage]=\"false\" on those buttons to keep the old box. Two things worth knowing before you use them. (1) disabledReason CHANGES HOW THE BUTTON IS DISABLED: with a reason set the button carries aria-disabled=\"true\" instead of the native disabled attribute, so it stays focusable and the reason is announced as its accessible description; the click is swallowed in the handler, so (pressed) still never fires. If you have CSS keyed on `ds-button button[disabled]` or `:disabled`, add `[aria-disabled=\"true\"]` - the library's own disabled paint already covers both. (2) hint/warning/error are for the OTHER kind of refusal: a temporary one the user lifts by filling the form in. Do not disable the button for those - leave it live, judge validity in the submit handler, and let the message line explain. A message-bearing button becomes a column, and since the host shrinks to fit, a message longer than the label widens the pair, button included. (delete list: button-disabled-reason-tooltip)",
103
106
  "Every item in every published manifest now carries `action` (the imperative alone, the only field to execute), `appliesWhen` (the boundary, including what is NOT affected) and `pitfall` (the way to apply it correctly and still break the app); `note` keeps the reasoning. If you read these files with your own tooling, read `action` first and `pitfall` before reporting an item done. Nothing was removed - every field that was there is still there with the same name and meaning.",
104
107
  "ds-w3w renders `///word.word.word` flush now. It previously showed a space after the `///` prefix (7.8px wider than the format allows, measured), which also disagreed with its own aria-label. Purely a rendering fix - no API change and nothing to edit. Worth a look only if you compensated for the space: a negative margin or a letter-spacing tweak aimed at ds-w3w's mark, or a hand-built pill you wrote because the DS one looked wrong, would now over-correct.",
105
108
  "ds-banner now sets `text-align: start` on its own box instead of inheriting. Nothing to do unless you were centring a banner by centring its container - that no longer reaches the banner, and the fix is to say so rather than to work around it. The reported symptom (a centred title over a start-aligned body) does not come from the DS: measured across every banner and both layouts, title and body both compute `start`, and a centred ancestor moves BOTH - it cannot split them. If you still see the split, something on your side targets `.title` or `.body` directly; those are generic class names and a global rule reaches them.",
@@ -7,7 +7,7 @@
7
7
  "old": ".autocomplete-list, .autocomplete-optgroup, .autocomplete-optgroup-label",
8
8
  "new": ".dropdown-list, .optgroup, .optgroup-label",
9
9
  "appliesWhen": "You wrote a global rule against `.ds-overlay-pane .autocomplete-list` or a sibling. The check icon's `.icon` inside an option is `.option-check` too, and all of them sit inside a new `.dropdown-panel` wrapper. Nothing to do if you only use the `<ds-autocomplete>` element and its inputs.",
10
- "pitfall": "The panel is portaled to document.body, so these rules are almost always global rather than component-scoped - grep your global stylesheets, not just the component next to the picker. Retargeting one is also a WIDENING: the three pickers share this panel and it carries no per-picker class, attribute or token, so a rule that used to reach the autocomplete alone now reaches ds-select and ds-multi-select too. There is a second trap under it - a rule of yours on `.ds-overlay-pane` loses to the panel radius and background, which the picker copies off its own host as an inline style.",
10
+ "pitfall": "The panel is portaled to document.body, so these rules are almost always global rather than component-scoped - grep your global stylesheets, not just the component next to the picker. Retargeting one is also a WIDENING: the three pickers share this panel and it carries no per-picker class, attribute or token, so a rule that used to reach the autocomplete alone now reaches ds-select and ds-multi-select too. There is a second trap under it - a rule of yours on `.ds-overlay-pane` loses to the panel radius and background, which the picker copies off its own host as an inline style. Padding and row-radius compensation in a retargeted rule is dead (delete list: autocomplete-listbox-padding-override).",
11
11
  "searchHints": [
12
12
  "autocomplete-list",
13
13
  "autocomplete-optgroup"
@@ -18,14 +18,14 @@
18
18
  ".autocomplete-optgroup",
19
19
  ".autocomplete-optgroup-label"
20
20
  ],
21
- "verify": "The autocomplete's open panel carries `ds-dropdown-panel` on its `.cdk-overlay-pane`, and its rows have 4px padding and a 4px radius without any rule of yours.",
21
+ "verify": "The autocomplete's open panel carries `ds-dropdown-panel` on its `.cdk-overlay-pane`, the panel has 4px padding and its rows a 4px radius without any rule of yours.",
22
22
  "restore": "To keep a rule on one picker, scope it by something outside the pane - a container class on the page - and re-narrow it once a per-picker panel class is available. To set that picker's own radius or background, write it on the host: `ds-autocomplete { --ds-autocomplete-panel-radius: <value>; }`, which is copied onto the pane and wins.",
23
23
  "note": "The panel now renders through the same shared partial as ds-select and ds-multi-select, so it inherits their padding, row radius, selected-row hooks and pressed states. An override that existed only to close that gap is dead weight, and one that names an old class silently stops matching. A `panelClass` input on each picker arrives in 0.13.1 and is the scoped route; until then a widened rule is the only expressible form, so mark it where you write it and narrow it when you reach that version.",
24
- "action": "Retarget every rule that names an old class, then delete the ones that only restored padding or row radius."
24
+ "action": "Retarget every rule that names an old class onto its new name."
25
25
  },
26
26
  {
27
27
  "id": "autocomplete-option-hover-token-removed",
28
- "kind": "token-rename",
28
+ "kind": "removed-api",
29
29
  "old": "--ds-autocomplete-option-bg-color-hover",
30
30
  "new": "--ds-option-selected-bg-color, --ds-option-selected-label-color, --ds-option-selected-bg-color-hover, --ds-option-check-color",
31
31
  "appliesWhen": "You set --ds-autocomplete-option-bg-color-hover anywhere.",
@@ -39,7 +39,7 @@
39
39
  ],
40
40
  "verify": "A :root or ds-autocomplete override of --ds-option-selected-bg-color repaints the selected row in ds-select and ds-autocomplete. ds-multi-select marks selection with a checkbox, so it answers to --ds-multi-select-check-* instead.",
41
41
  "restore": null,
42
- "note": "The autocomplete had no separate selected treatment, so one token painted both hover and selection. The panel-level hooks reach all three pickers and separate the two states, which is what the 0.9.0 notes already claimed was true.",
42
+ "note": "The autocomplete had no separate selected treatment, so one token painted both hover and selection. The panel-level hooks paint the selected row and its hover in ds-select and ds-autocomplete; ds-multi-select marks selection with a checkbox and answers to --ds-multi-select-check-* instead, and an unselected row's hover is a fixed --surface-secondary with no hook.",
43
43
  "action": "Replace --ds-autocomplete-option-bg-color-hover with the panel-level --ds-option-* hooks."
44
44
  },
45
45
  {
@@ -48,7 +48,7 @@
48
48
  "old": "ds-autocomplete",
49
49
  "new": null,
50
50
  "appliesWhen": "You use `<ds-autocomplete>` in single mode in a narrow column.",
51
- "pitfall": "Multi mode is unchanged — its chips already had a measured cap. This only affects the settled single value.",
51
+ "pitfall": "Multi mode with the default chip fit is unchanged - its chips already had a measured cap. `maxVisibleChips=\"all\"` is not: the trigger no longer wraps, so its chips stay on one line unless `valueOverflow=\"wrap\"` is set.",
52
52
  "searchHints": [
53
53
  "ds-autocomplete"
54
54
  ],
@@ -58,7 +58,7 @@
58
58
  ],
59
59
  "verify": "A long value in a 144px-wide single-select autocomplete keeps the trigger one row tall and ends in an ellipsis, with the full text on the element's title.",
60
60
  "restore": "valueOverflow=\"wrap\"",
61
- "note": "A settled single value now clips with an ellipsis and keeps the trigger one row tall, with the full text on the element title. Multi mode is untouched — its chips already had a measured cap. Nothing in your markup has to change unless the wrapping was deliberate.",
61
+ "note": "A settled single value now clips with an ellipsis and keeps the trigger one row tall, with the full text on the element title. Multi mode with the default chip fit is untouched - its chips already had a measured cap; with maxVisibleChips=\"all\" the trigger no longer wraps unless valueOverflow=\"wrap\" is set. Nothing in your markup has to change unless the wrapping was deliberate.",
62
62
  "action": "Do nothing, or set valueOverflow=\"wrap\" on the pickers that relied on the value wrapping."
63
63
  },
64
64
  {
@@ -67,7 +67,7 @@
67
67
  "old": "SelectComponent, MultiSelectComponent, AutocompleteComponent",
68
68
  "new": null,
69
69
  "appliesWhen": "Subclassing a DS component is unsupported, but consumers do it. Template users of the `<ds-…>` elements need nothing.",
70
- "pitfall": "`protected` is no protection: a redeclared protected member collides exactly as a public one does. Separately, seven symbols are newly exported and can shadow a local name of the same spelling rather than collide with a member: `DsControlWidth`, `DsTriggerDisplay`, `DsChipTemplateDirective`, `DsCreateTemplateDirective`, `DsEmptyTemplateDirective`, `DsOptionTemplateDirective`, `DsPickerTriggerDirective`. Those are new names, not changed ones — nothing of yours breaks unless you already had one.",
70
+ "pitfall": "`protected` is no protection: a redeclared protected member collides exactly as a public one does. Separately, seventeen symbols are newly exported and can shadow a local name of the same spelling rather than collide with a member: `DsControlWidth`, `DsTriggerDisplay`, `DsChipTemplateDirective`, `DsCreateTemplateDirective`, `DsEmptyTemplateDirective`, `DsOptionTemplateDirective`, `DsPickerTriggerDirective`, `DsOptionGroup`, `DsOptionItem`, `isDsOptionGroup`, `flattenDsOptions`, `AutocompleteItem`, `AutocompleteValueOverflow`, `MultiSelectItem`, `MultiSelectOptionGroup`, `MultiSelectWidth`, `SelectWidth`. Those are new names, not changed ones — nothing of yours breaks unless you already had one. ds-autocomplete also lost the protected computed `filteredGroups`: a subclass member of that name marked `override` fails with TS4113, and one without the modifier compiles and never runs, so check for it by hand.",
71
71
  "searchHints": [
72
72
  "extends SelectComponent",
73
73
  "extends MultiSelectComponent",
@@ -78,7 +78,17 @@
78
78
  "DsCreateTemplateDirective",
79
79
  "DsEmptyTemplateDirective",
80
80
  "DsOptionTemplateDirective",
81
- "DsPickerTriggerDirective"
81
+ "DsPickerTriggerDirective",
82
+ "DsOptionGroup",
83
+ "DsOptionItem",
84
+ "isDsOptionGroup",
85
+ "flattenDsOptions",
86
+ "AutocompleteItem",
87
+ "AutocompleteValueOverflow",
88
+ "MultiSelectItem",
89
+ "MultiSelectOptionGroup",
90
+ "MultiSelectWidth",
91
+ "SelectWidth"
82
92
  ],
83
93
  "surface": "typescript",
84
94
  "detect": [
@@ -88,7 +98,7 @@
88
98
  ],
89
99
  "verify": "The app builds with no TS2415 or TS2416 naming a picker component.",
90
100
  "restore": null,
91
- "note": "All three pickers gained members: ds-select a width input and a private panelTokens field, ds-multi-select and ds-autocomplete a label/required/optional block plus projection slots. Subclassing a DS component is unsupported but consumers do it, and a redeclared member collides whether it is public or protected. The compiler enumerates every collision, so a build is the whole check and no list here could stay current.",
101
+ "note": "All three pickers gained members. ds-select, 5: `width`, `panelTokens`, `optionTemplate`, `emptyTemplate` and `pickerTrigger`. ds-multi-select, 29: `searchable`, `searchableResolved`, `width`, `size`, `sizeResolved`, `triggerDisplay`, `label`, `labelId`, `required`, `optional`, `optionTemplate`, `chipTemplate`, `emptyTemplate`, `pickerTrigger`, `allOptions`, `filteredItems`, `enabledIn`, the private `firstEnabledIndex`, `flatIndexOf`, `isGroup`, `groupAllSelected`, `groupSomeSelected`, `toggleGroup`, `showsCompactTrigger`, `showsGroupSelectAll`, `showsPanelSelectAll`, `showsSearch`, `triggerActiveDescendant` and `triggerCaption`. ds-autocomplete, 16: `valueOverflow`, `label`, `labelId`, `required`, `optional`, `optionTemplate`, `chipTemplate`, `createTemplate`, `emptyTemplate`, `pickerTrigger`, `filteredItems`, `isGroup`, `hasSingleValue`, `selectedOption`, `triggerSelection` and `resolvedAriaLabel`. It lost `optionGroups`, which has its own item, and the protected `filteredGroups`. Subclassing a DS component is unsupported but consumers do it, and a redeclared member collides whether it is public or protected. The compiler enumerates every collision, so a build is the whole check and no list here could stay current.",
92
102
  "action": "Build after upgrading, and rename or mark `override` every member of yours the compiler reports as colliding."
93
103
  },
94
104
  {
@@ -135,10 +145,10 @@
135
145
  "kind": "class-rename",
136
146
  "old": ".panel, .options",
137
147
  "new": ".dropdown-panel, .dropdown-list",
138
- "action": "Retarget any rule naming the old classes, then delete the ones that only restored what the shared panel already gives.",
148
+ "action": "Retarget any rule naming the old classes onto their new names.",
139
149
  "note": "The multi-select carried its own copy of the panel and the option row while its pane also carried ds-dropdown-panel, so both rule sets applied at once and the component’s won. It renders through the shared partial now, like the other two pickers.",
140
150
  "appliesWhen": "You wrote a global rule against `.ds-overlay-pane .panel` or `.options` for the multi-select - both classes live inside its portaled panel.",
141
- "pitfall": "The panel is portaled to document.body, so such a rule is almost always global rather than beside the component.",
151
+ "pitfall": "The panel is portaled to document.body, so such a rule is almost always global rather than beside the component. A declaration in it that only restored what the shared panel gives - its padding, row radius and fills - restates the default once retargeted.",
142
152
  "searchHints": [
143
153
  "ds-overlay-pane .panel",
144
154
  ".options"
@@ -237,9 +247,9 @@
237
247
  "ds-multi-select and ds-autocomplete gained `label`, `required` and `optional`, which existed on ds-select alone; ds-multi-select gained `size`, which the other two already had.",
238
248
  "New slots: dsEmptyTemplate on all three pickers, dsCreateTemplate on ds-autocomplete. ds-select shows an empty row when it has no options, where it used to open a blank panel.",
239
249
  "selectAll on ds-multi-select accepts 'group' and 'both' beside true/false.",
240
- "All three pickers now forward the four panel-level --ds-option-* hooks onto their portaled pane, so a per-instance override reaches the panel.",
250
+ "All three pickers now forward the four panel-level --ds-option-* hooks onto their portaled pane, so a per-instance override reaches the panel. They paint only ds-select and ds-autocomplete: ds-multi-select marks selection with a checkbox and takes --ds-multi-select-check-* instead.",
241
251
  "The dropdown panel geometry now lives only in styles/_dropdown-overlay.scss, behind --ds-dropdown-panel-bg-color/-radius/-maxh/-minw/-maxw. The per-picker names (--ds-multi-select-panel-bg-color, --ds-autocomplete-panel-bg-color/-radius/-maxh) are aliases of those and still work; a global rule of yours that relied on a component stylesheet out-ranking the partial no longer has a competing rule to beat.",
242
- "A bare searchable attribute on a picker now means true, where it meant \"unset\" and so could not override an app-level DS_CONFIG.picker.searchable of false — the one case that key exists for. If you set that key to false and wrote a bare searchable on a picker to opt it back in, that picker was not searchable before and is now, which is what the markup asked for. Write searchable=\"false\" where you want the app-level default to stand. NO ACTION otherwise."
252
+ "ds-multi-select gained `searchable`: true shows the filter row, false hides it, a number sets an option-count threshold. A bare attribute means true. Unset falls back to the new DS_CONFIG.picker.searchable, then true, so nothing changes by default."
243
253
  ],
244
254
  "deleteList": [
245
255
  {
@@ -247,6 +257,7 @@
247
257
  "surface": "style",
248
258
  "find": [
249
259
  ".ds-overlay-pane .autocomplete-list",
260
+ ".ds-overlay-pane .dropdown-list",
250
261
  "padding",
251
262
  "border-radius"
252
263
  ],
@@ -7,7 +7,7 @@
7
7
  "old": "SelectComponent, MultiSelectComponent, AutocompleteComponent",
8
8
  "new": null,
9
9
  "action": "Build after upgrading, and rename or mark `override` every member of yours the compiler reports as colliding.",
10
- "note": "All three pickers gained members for the new inputs and outputs. Subclassing a DS component is unsupported but consumers do it, and a redeclared member collides whether it is public or protected. The compiler enumerates every collision, so a build is the whole check and no list here could stay current.",
10
+ "note": "All three pickers gained members for the new inputs and outputs: `AutocompleteComponent` gained 21, `MultiSelectComponent` gained 22 and `SelectComponent` gained 15, among them the `opened` and `closed` outputs, `loading` and the private `setOpen`. Subclassing a DS component is unsupported but consumers do it, and a redeclared member collides whether it is public or protected. The compiler enumerates every collision, so a build is the whole check and no list here could stay current.",
11
11
  "appliesWhen": "You subclass a picker component. Template users of the `<ds-...>` elements need nothing.",
12
12
  "pitfall": "`protected` is no protection: a redeclared protected member collides exactly as a public one does.",
13
13
  "searchHints": [
@@ -30,7 +30,7 @@
30
30
  "old": "TableComponent",
31
31
  "new": null,
32
32
  "action": "Build after upgrading, and rename or mark `override` every member of yours the compiler reports as colliding.",
33
- "note": "TableComponent gained members for row expansion: expandMode, expandAllToggle, rowExpanded, rowCollapsed and the protected helpers behind the header toggle. A redeclared member collides whether it is public or protected, and the compiler enumerates every one, so a build is the whole check.",
33
+ "note": "TableComponent gained members for row expansion (expandMode, expandAllToggle, rowExpanded, rowCollapsed and the protected helpers behind the header toggle) and for bounded and touch column resizing (resizeRange, onResizeFocus, onResizeBlur, onColumnWidthStep, resizeStep, columnSheetOpen, coarsePointer and private helpers). `TableComponent` gained 24 in all and lost the protected `windowData`. A redeclared member collides whether it is public or protected, and the compiler enumerates every one, so a build is the whole check.",
34
34
  "appliesWhen": "You subclass TableComponent. Template users of `<ds-table>` need nothing.",
35
35
  "pitfall": "`protected` is no protection: a redeclared protected member collides exactly as a public one does.",
36
36
  "searchHints": [
@@ -112,7 +112,7 @@
112
112
  "new": null,
113
113
  "action": "If a ds-select has to show more than 280px of options, set `--picker-maxh` globally, in your own `:root` or on a shell element the pickers sit under. All three pickers follow it.",
114
114
  "appliesWhen": "Only ds-select, and only where the list was long enough to reach the old 320px. ds-autocomplete and ds-multi-select already capped at this value and do not move. There is no per-picker form of this at this version: the panel is portaled and carries no class of its own, and `--picker-maxh` is read inside the pane rather than copied onto it from the host, so a value set on one picker does not reach its panel.",
115
- "pitfall": "Two independent caps, and the one a consumer reaches for is the wrong one. `--ds-dropdown-panel-maxh` caps the PANEL box and is forwarded from the host, so it is the one that looks settable per picker - and raising it alone changes nothing you can see. The list INSIDE caps separately at `--picker-maxh`, and that is what decides how many rows are visible.",
115
+ "pitfall": "Two independent caps, and the one a consumer reaches for is the wrong one. `--ds-dropdown-panel-maxh` caps the PANEL box (ds-select does not forward it from its host; only ds-autocomplete does), so raising it alone changes nothing you can see. The list INSIDE caps separately at `--picker-maxh`, and that is what decides how many rows are visible.",
116
116
  "note": "The option list's own max-height moved into the shared panel partial, so ds-select caps its list at `--picker-maxh` (280px) where it previously ran to the panel's `--ds-dropdown-panel-maxh` (320px). A `panelClass` input on each picker arrives in 0.13.1; a rule on that class is the scoped route to one picker's list height, and until then the token is global or nothing.",
117
117
  "searchHints": [
118
118
  "ds-dropdown-panel-maxh",
@@ -25,10 +25,10 @@
25
25
  "kind": "behavior",
26
26
  "old": "ToastRegionComponent",
27
27
  "new": null,
28
- "action": "Build after upgrading. Rename or mark `override` every member the compiler reports as colliding, and DELETE any `override startCountdown` - that member no longer exists, so the override is dead code the compiler will not complain about.",
28
+ "action": "Build after upgrading. Rename or mark `override` every member the compiler reports as colliding, and DELETE any `startCountdown` member of yours - ours no longer exists, so yours is dead code the compiler only flags when it carries `override` (TS4113).",
29
29
  "appliesWhen": "Only a class that extends ToastRegionComponent. Template users of `<ds-toast-region>` and callers of ToastService need nothing.",
30
- "pitfall": "`startCountdown` was announced in 0.11.2 as a member the region had just GAINED, so an override written for that release is one release old and now overrides nothing: it compiles clean and silently never runs. And every one of the five new names is `private` or `protected`, which is no protection - a redeclared private fails with TS2415 exactly as a public collision does.",
31
- "note": "ToastRegionComponent gained `arm`, `pauseAll`, `remaining`, `resumeAll` and `startedAt`, and lost `startCountdown`. A countdown is armed when a toast is promoted to visible, and re-armed from what is left when a hover or focus pause ends - the region owns the timing because only it knows when a toast became visible. None of the five is public API or a signal, and there is no public replacement for `startCountdown`.",
30
+ "pitfall": "`startCountdown` was private in 0.11.2, so a subclass redeclaring it hit TS2415 with or without `override`. Now it is gone: a method of that name compiles clean and never runs, while one marked `override` fails with TS4113. And every one of the twelve new names is `private` or `protected`, which is no protection - a redeclared private fails with TS2415 exactly as a public collision does.",
31
+ "note": "ToastRegionComponent gained the private `arm`, `pauseAll`, `resumeAll`, `syncPause`, `paused`, `remaining`, `startedAt`, `hovered`, `focusWithin`, `host` and the protected `onHover`, `onFocusWithin`, and lost `startCountdown`. A countdown is armed when a toast is promoted to visible, and re-armed from what is left when a hover or focus pause ends - the region owns the timing because only it knows when a toast became visible. None of the twelve is public API or a signal, and there is no public replacement for `startCountdown`.",
32
32
  "searchHints": [
33
33
  "extends ToastRegionComponent",
34
34
  "ToastRegionComponent",
@@ -36,15 +36,18 @@
36
36
  "override startCountdown",
37
37
  "pauseAll",
38
38
  "resumeAll",
39
+ "onHover",
40
+ "onFocusWithin",
39
41
  "TS2415",
40
- "TS4114"
42
+ "TS4114",
43
+ "TS4113"
41
44
  ],
42
45
  "surface": "typescript",
43
46
  "detect": [
44
47
  "extends ToastRegionComponent",
45
48
  "override startCountdown"
46
49
  ],
47
- "verify": "The app builds with no TS4114 / TS2415 / TS2416 naming ToastRegionComponent, and no `override startCountdown` remains in your source.",
50
+ "verify": "The app builds with no TS4113 / TS4114 / TS2415 / TS2416 naming ToastRegionComponent, and no `startCountdown` member remains in a subclass of it.",
48
51
  "restore": null
49
52
  },
50
53
  {
@@ -139,7 +142,7 @@
139
142
  }
140
143
  ],
141
144
  "informational": [
142
- "The banner, toast and alert icon now centres on the message block instead of aligning to the first line of text. Nothing to change: it is a visual default, applied by the components themselves. One-line messages look identical either way, which covers most toasts; the difference grows with the text, and was 12px at two lines and 21px at three.",
145
+ "The banner, toast and alert icon now centres on the message block instead of aligning to the first line of text. Nothing to change: it is a visual default, applied by the components themselves. One-line messages look the same either way, which covers most toasts, except a banner with layout set to row and actions beside the text: its icon was pinned to the top of the row and now centres with the text; the difference grows with the text, and was 12px at two lines and 21px at three.",
143
146
  "ToastService.promise() and any toast with an `action` changed their dismissal timing. A settled promise toast now counts its 4s/6s from when it becomes visible rather than from when the promise resolved, so one queued behind `maxVisible` is no longer removed before it is shown. A toast with an `action` no longer auto-dismisses at all and is always dismissible, because the region is last in tab order and the button was unreachable within the old five seconds. Hovering or focusing the region pauses every countdown. Nothing to change in consumer code; if you relied on an action toast disappearing on its own, dismiss it from the action handler.",
144
147
  "Inside a `ds-color=\"error\"`, `=\"success\"` or `=\"warning\"` zone, anything that reads the scoped accent's strong colour, --accent-strong, now renders in that status colour instead of falling back to body text — selected list and tree rows, the active sidenav item and its rail, the active tab pill, avatar initials, the active tag, dropzone text, the toast's action label, the selected toggle button, the split-button hover fill, the tonal, ghost, outline and text variants of ds-button, and the tonal variant of ds-icon-button. Nothing to change: those three families simply never defined the role the zone asked for, and --accent-strong now asks for -strong first and the family's readable on-tint -text second. A zone whose accent looked plain before will now look coloured, which is the intended appearance.",
145
148
  "ds-banner's close button gained aria-label=\"Dismiss\", which ds-toast and ds-alert already carried. NO ACTION.",
@@ -17,7 +17,7 @@
17
17
  ],
18
18
  "verify": "A success callback receives the resolved value with its real type: toast.promise(loadOrder(), { success: (order) => `Saved #${order.id}` }) compiles without a cast.",
19
19
  "restore": null,
20
- "note": "promise<T> declared a type parameter and then threw it away, because the messages interface hardcoded unknown. Every call site that wanted the resolved value had to cast. A widened exported type, not a rename: the bare name still compiles (T defaults to unknown), but a typed success/error callback against the bare annotation stops compiling — annotate with your concrete T.",
20
+ "note": "promise<T> declared a type parameter and then threw it away, because the messages interface hardcoded unknown. Every call site that wanted the resolved value had to cast. A widened exported type, not a rename: the bare name still means `unknown`, so a typed success callback against it fails exactly as before - annotate with your concrete T. `error` still receives `unknown`.",
21
21
  "action": "Annotate as ToastPromiseMessages<T> where you name the type; inline object literals need no change."
22
22
  },
23
23
  {
@@ -47,7 +47,7 @@
47
47
  "old": "--ds-toast-border, --ds-toast-border-info, --ds-toast-border-success, --ds-toast-border-warning, --ds-toast-border-error",
48
48
  "new": "--ds-toast-border-color, --ds-toast-border-color-info, --ds-toast-border-color-success, --ds-toast-border-color-warning, --ds-toast-border-color-error",
49
49
  "appliesWhen": "You set any of the five anywhere - :root, a theme file, or a per-instance ds-toast block.",
50
- "pitfall": "The old name simply stops resolving, and the declaration it sits in is dropped whole - so a toast loses its border rather than falling back to a default. Nothing errors.",
50
+ "pitfall": "The old name simply stops being read: your declaration stays valid and inert, and the toast falls back to the default --border-default colour instead of yours. Nothing errors.",
51
51
  "searchHints": [
52
52
  "ds-toast-border"
53
53
  ],
@@ -141,7 +141,7 @@
141
141
  ],
142
142
  "verify": "Raise six toasts at once: with maxVisible 0 all six are on screen, and with the default five are, the sixth arriving as one dismisses.",
143
143
  "restore": "Pass provideDsConfig({ toast: { maxVisible: 0 } }).",
144
- "note": "The default moved from unlimited to 5. A negative value means unlimited too and warns in development, because 0 already says it.",
144
+ "note": "The default moved from unlimited to 5. A negative provideDsConfig value is ignored and leaves the cap at 5; only 0 asks for an uncapped stack. A negative maxVisible bound straight on ds-toast-region means unlimited and warns in development.",
145
145
  "action": "Decide whether an uncapped stack was deliberate. If it was, pass provideDsConfig({ toast: { maxVisible: 0 } }); otherwise change nothing."
146
146
  },
147
147
  {
@@ -173,7 +173,7 @@
173
173
  "old": "ToastComponent, ToastRegionComponent, ToastService, TableComponent, BannerComponent, AlertComponent",
174
174
  "new": null,
175
175
  "appliesWhen": "Only a class that extends one of those six. Template users and service callers need nothing.",
176
- "pitfall": "Every new name is private or protected, which is no protection - a redeclared private fails with TS2415 exactly as a public collision does. And an `override promoteFromQueue` or `override role` now overrides nothing: it compiles clean and silently never runs.",
176
+ "pitfall": "Every new name except the public inputs `body` (ToastComponent) and `announce` (BannerComponent, AlertComponent) is private, which is no protection - a redeclared private fails with TS2415 exactly as a public collision does. `role` and `promoteFromQueue` are gone: a subclass `override role` now fails with TS4113, and a same-named member without `override` compiles but never runs.",
177
177
  "searchHints": [
178
178
  "extends ToastComponent",
179
179
  "extends ToastRegionComponent",
@@ -183,6 +183,7 @@
183
183
  "override role",
184
184
  "TS2415",
185
185
  "TS4114",
186
+ "TS4113",
186
187
  "extends BannerComponent",
187
188
  "extends AlertComponent"
188
189
  ],
@@ -197,10 +198,10 @@
197
198
  "extends BannerComponent",
198
199
  "extends AlertComponent"
199
200
  ],
200
- "verify": "The app builds with no TS4114 / TS2415 / TS2416 naming any of the six classes, and no override of promoteFromQueue, role or message remains in your source.",
201
+ "verify": "The app builds with no TS4113 / TS4114 / TS2415 / TS2416 naming any of the six classes, and no override of promoteFromQueue, role or message remains in your source.",
201
202
  "restore": null,
202
- "note": "ToastComponent lost `role`. ToastRegionComponent gained `leaveTimers`, `slideNeighbours`, `toastNodes`, `measureTops` and `leaveDuration`, and renamed `promoteFromQueue` to `drainQueue`. ToastService gained `announcer`, `pendingAnnouncements`, `pendingAssertive`, `announceTimer`, `scrimWatcher`, `announce` and `keepAboveScrims`. TableComponent gained `eventsAtExport`, `eventMessages`, `tableHead`, `hostElement` and `announceExport`. None is public API or a signal. BannerComponent and AlertComponent each gained `announce`. ToastComponent also gained `body` and lost `message`, which is the input rename listed separately.",
203
- "action": "Build after upgrading. Rename or mark `override` every member the compiler reports as colliding, and DELETE any `override promoteFromQueue` or `override role` - neither member exists any more, so the override is dead code."
203
+ "note": "ToastComponent lost `role`. ToastRegionComponent gained `leaveTimers`, `slideNeighbours`, `toastNodes`, `measureTops` and `leaveDuration`, and renamed `promoteFromQueue` to `drainQueue`. ToastService gained `announcer`, `pendingAnnouncements`, `pendingAssertive`, `announceTimer`, `scrimWatcher`, `announce` and `keepAboveScrims`, and lost `position`. TableComponent gained `eventsAtExport`, `eventMessages`, `tableHead`, `hostElement` and `announceExport`. None is public API. BannerComponent and AlertComponent each gained `announce`. ToastComponent also gained `body` and lost `message`, which is the input rename listed separately.",
204
+ "action": "Build after upgrading. Rename or mark `override` every member the compiler reports as colliding, and DELETE any `override promoteFromQueue` or `override role` - neither member exists any more, so a marked override fails with TS4113 and an unmarked one is dead code."
204
205
  },
205
206
  {
206
207
  "id": "banner-alert-aria-getters-nullable",
@@ -208,20 +209,20 @@
208
209
  "old": "BannerComponent.ariaRole, AlertComponent.ariaRole",
209
210
  "new": null,
210
211
  "appliesWhen": "Only a class extending BannerComponent or AlertComponent that reads or overrides ariaRole or ariaLive. Nothing in a template sees these.",
211
- "pitfall": "A widening breaks the READER, not the writer: an override that still declares the narrow return type fails, and code that fed the value somewhere non-nullable fails too, both at a site that did not change.",
212
+ "pitfall": "A widening breaks the READER, not the writer: code that fed the value somewhere non-nullable fails with TS2322 at a site that did not change, while an override that still declares the narrow return type compiles, because a narrower return type still satisfies the base.",
212
213
  "searchHints": [
213
214
  "ariaRole",
214
215
  "ariaLive",
215
216
  "extends BannerComponent",
216
217
  "extends AlertComponent",
217
- "TS2416"
218
+ "TS2322"
218
219
  ],
219
220
  "surface": "typescript",
220
221
  "detect": [
221
222
  "ariaRole",
222
223
  "ariaLive"
223
224
  ],
224
- "verify": "The app builds with no TS2416 naming ariaRole or ariaLive, and any code consuming either handles null.",
225
+ "verify": "The app builds with no TS2322 naming ariaRole or ariaLive, and any code consuming either handles null.",
225
226
  "restore": null,
226
227
  "note": "Both getters widened from `'alert' | 'status'` and `'assertive' | 'polite'` to include `null`, and return null while `announce` is false, which is the default - that is how the attribute is left off entirely rather than set to an empty value.",
227
228
  "action": "Widen your own declaration to include null, and handle null wherever you read either getter."
@@ -229,7 +230,7 @@
229
230
  ],
230
231
  "informational": [
231
232
  "Typing on a closed ds-select now commits the type-ahead jump, as a native <select> does. The path existed but was unreachable, so nothing that worked before changes. NO ACTION.",
232
- "A chip row's guard against a parent that hugs its content was unreachable and is removed; the measurement is unchanged. NO ACTION.",
233
+ "A chip row's guard against a parent that hugs its content was unreachable and is replaced by one that asks layout whether the parent's width depends on the trigger. Where it does - a parent at fit-content, an inline-block one, or a flex item that cannot grow - the row now budgets from the trigger's own width instead of reading back its own cut. Affects ds-multi-select and ds-autocomplete. NO ACTION.",
233
234
  "A queued toast is not lost: it appears as an earlier one dismisses. The stack also animates when a toast is added rather than jumping, and --ds-toast-shift-duration and --ds-toast-shift-easing tune that. NO ACTION.",
234
235
  "Info, success and loading toasts raised through ToastService are now announced at all, where before only error and warning were. NO ACTION.",
235
236
  "Six tokens the connected panel reads - --ds-option-padding, -gap, -radius, -row-gap, --ds-option-bg-color-active and --ds-dropdown-panel-maxh - now take effect when scoped to one picker (ds-select { ... }), where before only a global declaration reached them. The panel is portaled outside the component, so a host-scoped value arrives only if the token is on the forwarded list, and these six were not. They join the list every dropdown picker shares, so none of them appears in a picker's own list of forwarded tokens; --ds-dropdown-panel-maxh reached ds-autocomplete and neither of its siblings. NO ACTION, and nothing moves on its own: it changes only where such a declaration is already written on an element and was being ignored. If you widened one to a global rule because the scoped form did nothing, the scoped form is now the narrower way to say it.",
@@ -238,7 +239,7 @@
238
239
  "The skeleton shimmer is driven per element instead of by one registered custom property on :root, so skeletons no longer travel in lock-step with one another. The property that drove it, --skeleton-shimmer-x, no longer exists: it was never a --ds-* hook, but if you referenced it, it now resolves to nothing. NO ACTION otherwise.",
239
240
  "A focused row in ds-list-item, ds-tree, ds-tag, ds-description-list or ds-color-picker now draws ONE ring, in the focus colour. It drew two — its own outline inside the library-wide focus halo — and that outline asked for --focus-ring-color, which nothing defined, so every site fell through to currentColor and ringed itself in its own text colour. The token is defined now and follows --accent, so it is the brand hue by default and the family’s hue inside a ds-color zone. Override it per brand with --focus-ring-color. NO ACTION.",
240
241
  "A selected ds-list-item or ds-tree node now retints its leading icon along with its label, where the icon stayed on its resting colour. Two new hooks control it if you want them apart: --ds-list-item-selected-icon-color and --ds-tree-row-selected-icon-color, each defaulting to the selected label colour. NO ACTION.",
241
- "ds-avatar-group and ds-button-group match their children as the direct child rather than by tag name. Computed output in an ordinary Angular application is unchanged — this only restores the avatar overlap and ring, and the joined buttons’ overlap and flattened radii, in a build that registers the library as custom elements, where a nested tag has to be renamed and a tag selector matched none of the children. NO ACTION.",
242
+ "ds-avatar-group and ds-button-group match their children as the direct child rather than by tag name. Computed output in an ordinary Angular application is unchanged when every child is a ds-avatar / ds-button placed directly in the group; any other direct child, such as a wrapper element or a ds-icon-button, now takes the group styling itself. Beyond that this only restores the avatar overlap and ring, and the joined buttons’ overlap and flattened radii, in a build that registers the library as custom elements, where a nested tag has to be renamed and a tag selector matched none of the children. NO ACTION.",
242
243
  "ds-split-button hovers with --accent-hover instead of the family’s readable on-tint colour, which was never meant as a background and left the label near-unreadable inside a status zone. The hover now follows the rest state instead of jumping to another hue. --ds-split-button-bg-hover-color still overrides it. NO ACTION.",
243
244
  "A ds-table loading scrim starts at the measured header height instead of an assumed 40px, so it no longer cuts into the header at the default density nor leaves the first row showing through it under [data-density=\"ultra-compact\"]. It lands correctly at any density and any header font size you set. --ds-table-head-h still overrides the value, which you should no longer need for the scrim (delete list: table-head-h-scrim-compensation). NO ACTION otherwise.",
244
245
  "A toast no longer sits under a modal, drawer, confirm or bottom sheet opened after it, so its action button stays reachable. Raising --layer-toast never fixed this and could not: every overlay host lives in the browser’s top layer, which paints strictly in the order hosts were shown and ignores z-index and stacking contexts altogether. The library re-shows the toast host itself now. If you raised --layer-toast or --layer-tooltip to work around this, that override was doing nothing and can go (delete list: layer-toast-tooltip-overrides). NO ACTION otherwise."