@ids-group-ltd/ids-design-system 0.11.1 → 0.11.2

This diff represents the content of publicly available package versions that have been released to one of the supported registries. The information contained in this diff is provided for informational purposes only and reflects changes between package versions as they appear in their respective public registries.
@@ -71,51 +71,6 @@
71
71
  "--ds-menu-divider-spacing"
72
72
  ]
73
73
  },
74
- {
75
- "id": "published-manifests-corrected",
76
- "kind": "behavior",
77
- "old": "A repo whose last @ids-group-ltd/ids-design-system upgrade ran before this release and crossed 0.2.0, 0.5.1, 0.7.1, 0.8.0, 0.9.0 or 0.10.0",
78
- "new": null,
79
- "action": "Re-run these items, now corrected in migrations/<version>.json: 0.2.0#surface-subtle-token-rename, 0.5.1#progress-variant-remap, 0.5.1#badge-variant-to-status-rename, 0.7.1#surface-motion-partial-a-la-carte, 0.7.1#modal-title-flex-moved-to-heading, 0.8.0#table-client-sort-replaced-by-sort-mode, 0.9.0#input-signal-types-widened-by-transforms, 0.10.0#input-floating-removed, 0.10.0#modal-confirm-error-tone-paints-a-badge. Nothing else in those files changed meaning.",
80
- "appliesWhen": "Only for a repo that already stepped through one of those six versions. A first-time consumer, or one whose upgrade runs from here on, reads the corrected files and needs none of this. The defects are independent - crossing 0.7.1 says nothing about 0.9.0.",
81
- "pitfall": "Two of these UNDO work rather than adding it. 0.7.1 filed the modal `.title` as a rename to `.heading`; no rename ever happened, so a repo that renamed it on our word must put it back - `.title` still paints the heading text. And 0.7.1 handed out bare `styles/…` @use specifiers that resolve only inside this library's own source tree: the line looks right and fails at build from an app. The 0.8.0 one is the silent case - an unset sortMode was documented as resolving to server when it resolves to client, so a server-paged table passes every check while sorting only the rows already on screen.",
82
- "note": "Each listed item was corrected against the code of its own release: three changes that had no item, two wrong instructions, one verify that certified a bug, and three items whose surface named too few file types.",
83
- "surface": [
84
- "style",
85
- "template",
86
- "typescript"
87
- ],
88
- "verify": "No `--surface-subtle` remains in any stylesheet. No bare `@use 'styles/…'` of a design-system partial remains - each is package-qualified. Every ds-table that binds [total] declares sortMode=\"server\" explicitly. No `variant` remains on ds-badge or ds-progress in any file type. No stylesheet sets --field-h-floating, --field-floating-label-fs, --field-floating-label-lh, --field-floating-label-top or --field-floating-pad-t. The app builds with no TS2322 naming InputSignal and no TS2416 on a class extending a DS field.",
89
- "searchHints": [
90
- "--surface-subtle",
91
- "@use 'styles/surface-motion'",
92
- "@use 'styles/overlay-motion'",
93
- ".heading",
94
- "sortMode",
95
- "[total]",
96
- "variant",
97
- "--field-h-floating",
98
- "--field-floating-label-fs",
99
- "--field-floating-pad-t",
100
- "InputSignal<",
101
- "ds-badge",
102
- "ds-progress",
103
- "ds-modal-card",
104
- "floating"
105
- ],
106
- "detect": [
107
- "--surface-subtle",
108
- "@use 'styles/surface-motion'",
109
- "@use 'styles/overlay-motion'",
110
- "--field-h-floating",
111
- "--field-floating-label-fs",
112
- "--field-floating-label-lh",
113
- "--field-floating-label-top",
114
- "--field-floating-pad-t",
115
- "InputSignal<",
116
- "ds-modal-card ::ng-deep .heading"
117
- ]
118
- },
119
74
  {
120
75
  "id": "sidenav-item-without-destination-is-a-button",
121
76
  "kind": "behavior",
@@ -67,11 +67,18 @@
67
67
  "old": "class MySelect extends SelectComponent, class MyMultiSelect extends MultiSelectComponent, class MyAutocomplete extends 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.",
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.",
71
71
  "searchHints": [
72
72
  "extends SelectComponent",
73
73
  "extends MultiSelectComponent",
74
- "extends AutocompleteComponent"
74
+ "extends AutocompleteComponent",
75
+ "DsControlWidth",
76
+ "DsTriggerDisplay",
77
+ "DsChipTemplateDirective",
78
+ "DsCreateTemplateDirective",
79
+ "DsEmptyTemplateDirective",
80
+ "DsOptionTemplateDirective",
81
+ "DsPickerTriggerDirective"
75
82
  ],
76
83
  "surface": "typescript",
77
84
  "detect": [
@@ -167,39 +174,6 @@
167
174
  "verify": "The trigger still shows a caption and a count badge.",
168
175
  "restore": null
169
176
  },
170
- {
171
- "id": "published-manifest-corrections",
172
- "kind": "behavior",
173
- "old": "a repo upgraded through 0.5.1, 0.9.0 or 0.10.1 before this release",
174
- "new": null,
175
- "surface": [
176
- "template",
177
- "typescript",
178
- "style"
179
- ],
180
- "action": "Re-run three items whose earlier text could not do its job. 0.5.1#progress-variant-remap: search for `variant=\"warn\"` and `variant=\"indeterminate\"` on ds-progress and for `ProgressVariant` in TypeScript, and finish that remap — the colour vocabulary is `default | success | warning | error` and the indeterminate state is the bare `indeterminate` attribute. 0.9.0#search-height-joins-field-scale: search for `--hit-min` and drop the pin where it was set only to shorten a ds-search row. 0.10.1: search for `(closed)` on a modal whose body holds a ds-date-picker and keep the body mounted instead.",
181
- "appliesWhen": "Only if your last upgrade ran BEFORE this release and crossed 0.5.1, 0.9.0 or 0.10.1. A first-time consumer, or one whose upgrade runs from here on, reads the corrected files and needs none of this. The three are independent — crossing 0.5.1 says nothing about 0.10.1.",
182
- "pitfall": "The 0.5.1 one is the silent case: its old check inspected ds-badge chips and the status registry, so it passed on a ds-progress that was never migrated. A clean upgrade report from that run proves nothing about ds-progress, so search rather than trusting it. The other two leave redundant code, not broken code — a `--hit-min` pin set deliberately for density is not this, so read each hit before deleting it.",
183
- "note": "These manifests are executed by an upgrade tool, so a wrong verify or a locator that finds nothing lands in the consumer repo as an unapplied migration that reported success.",
184
- "searchHints": [
185
- "variant=\"warn\"",
186
- "variant=\"indeterminate\"",
187
- "ProgressVariant",
188
- "--hit-min",
189
- "ds-progress",
190
- "(closed)"
191
- ],
192
- "detect": [
193
- "variant=\"warn\"",
194
- "variant=\"indeterminate\"",
195
- "ProgressVariant",
196
- "--hit-min",
197
- "@if (open())"
198
- ],
199
- "verify": "No ds-progress binds `variant=\"warn\"` or `variant=\"indeterminate\"` and nothing is typed against a removed ProgressVariant member; no `--hit-min` pin exists whose only purpose was a shorter ds-search row; no modal body is torn down on `(closed)` to reset a ds-date-picker.",
200
- "restore": null,
201
- "supersedes": null
202
- },
203
177
  {
204
178
  "id": "autocomplete-options-element-type-widened",
205
179
  "kind": "behavior",
@@ -0,0 +1,158 @@
1
+ {
2
+ "version": "0.11.2",
3
+ "items": [
4
+ {
5
+ "id": "picker-subclass-members-grew",
6
+ "kind": "behavior",
7
+ "old": "class MySelect extends SelectComponent, class MyMultiSelect extends MultiSelectComponent, class MyAutocomplete extends AutocompleteComponent",
8
+ "new": null,
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.",
11
+ "appliesWhen": "You subclass a picker component. Template users of the `<ds-...>` elements need nothing.",
12
+ "pitfall": "`protected` is no protection: a redeclared protected member collides exactly as a public one does.",
13
+ "searchHints": [
14
+ "extends SelectComponent",
15
+ "extends MultiSelectComponent",
16
+ "extends AutocompleteComponent"
17
+ ],
18
+ "surface": "typescript",
19
+ "detect": [
20
+ "extends SelectComponent",
21
+ "extends MultiSelectComponent",
22
+ "extends AutocompleteComponent"
23
+ ],
24
+ "verify": "The app builds with no TS2415 or TS2416 naming a picker component.",
25
+ "restore": null
26
+ },
27
+ {
28
+ "id": "table-subclass-members-grew",
29
+ "kind": "behavior",
30
+ "old": "class MyTable extends TableComponent",
31
+ "new": null,
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.",
34
+ "appliesWhen": "You subclass TableComponent. Template users of `<ds-table>` need nothing.",
35
+ "pitfall": "`protected` is no protection: a redeclared protected member collides exactly as a public one does.",
36
+ "searchHints": [
37
+ "extends TableComponent"
38
+ ],
39
+ "surface": "typescript",
40
+ "detect": [
41
+ "extends TableComponent"
42
+ ],
43
+ "verify": "The app builds with no TS2415 or TS2416 naming TableComponent.",
44
+ "restore": null
45
+ },
46
+ {
47
+ "id": "loading-overlay-subclass-members-grew",
48
+ "kind": "behavior",
49
+ "old": "class MyOverlay extends LoadingOverlayComponent",
50
+ "new": null,
51
+ "action": "Build after upgrading, and rename or mark `override` every member of yours the compiler reports as colliding.",
52
+ "note": "LoadingOverlayComponent gained `inertContent`. A redeclared member collides whether it is public or protected, and the compiler enumerates every one, so a build is the whole check.",
53
+ "appliesWhen": "You subclass LoadingOverlayComponent. Template users of `<ds-loading-overlay>` need nothing.",
54
+ "pitfall": "`protected` is no protection: a redeclared protected member collides exactly as a public one does.",
55
+ "searchHints": [
56
+ "extends LoadingOverlayComponent"
57
+ ],
58
+ "surface": "typescript",
59
+ "detect": [
60
+ "extends LoadingOverlayComponent"
61
+ ],
62
+ "verify": "The app builds with no TS2415 or TS2416 naming LoadingOverlayComponent.",
63
+ "restore": null
64
+ },
65
+ {
66
+ "id": "toast-region-subclass-members-grew",
67
+ "kind": "behavior",
68
+ "old": "class MyToastRegion extends ToastRegionComponent",
69
+ "new": null,
70
+ "action": "Nothing unless you subclass ToastRegionComponent and declare a member of those names: rename yours, or add `override` if you meant to replace ours.",
71
+ "note": "ToastRegionComponent gained six members: the fields `timers`, `position` and `newestFirst`, and the methods `show`, `startCountdown` and `clearCountdown`. The auto-dismiss countdown moved into the region, because only it knows when a toast became visible — started in the service, a toast queued behind `maxVisible` expired without ever being shown. `newestFirst` puts the newest toast nearest the anchor.",
72
+ "appliesWhen": "Only a class that extends ToastRegionComponent.",
73
+ "pitfall": "`durationMs` is now a required field on `ToastEntry`. That reaches further than subclassing, so it is its own item — see `toast-entry-duration-required`.",
74
+ "searchHints": [
75
+ "extends ToastRegionComponent",
76
+ "ToastRegionComponent",
77
+ "timers",
78
+ "newestFirst"
79
+ ],
80
+ "surface": "typescript",
81
+ "detect": [
82
+ "extends ToastRegionComponent"
83
+ ],
84
+ "verify": "Build your app: no TS4114 or TS2415 against a class extending ToastRegionComponent.",
85
+ "restore": null
86
+ },
87
+ {
88
+ "id": "toast-entry-duration-required",
89
+ "kind": "code-add",
90
+ "old": null,
91
+ "new": "durationMs: 5000",
92
+ "action": "Add `durationMs` to every hand-built `ToastEntry`: the auto-dismiss delay in ms, or `0` for indefinite. `ToastService.show()` and its variants are unaffected — they take `ToastOptions`, where `durationMs` stays optional and defaults to 5000 (0 for `loading`).",
93
+ "note": "`ToastEntry` gained a required `durationMs: number`. The region reads it to start the countdown when the toast becomes visible, so the field has to be on the entry rather than held in the service. `ToastOptions.durationMs` is untouched — still optional, still 5000 by default, still 0 for a loading toast — so a caller of `ToastService` needs nothing.",
94
+ "appliesWhen": "You reference the `ToastEntry` type — annotating a variable, building one to pass to `add()`, or mapping your own model onto it. Callers of `ToastService` need nothing.",
95
+ "pitfall": "The break is a compile error at the construction site, not at `add()`, so a search for `add(` finds nothing. And `0` is not the same as leaving it out: it means indefinite, so a toast written that way never dismisses itself.",
96
+ "searchHints": [
97
+ "ToastEntry",
98
+ "durationMs",
99
+ ".add("
100
+ ],
101
+ "surface": "typescript",
102
+ "detect": [
103
+ "ToastEntry"
104
+ ],
105
+ "verify": "The app builds with no TS2741 or TS2739 naming `durationMs` on `ToastEntry`.",
106
+ "restore": null
107
+ },
108
+ {
109
+ "id": "select-option-list-caps-at-picker-maxh",
110
+ "kind": "behavior",
111
+ "old": "--ds-dropdown-panel-maxh",
112
+ "new": null,
113
+ "action": "If a ds-select has to show more than 280px of options, set `--picker-maxh` to the height you want — on the panel where only that select should change, or globally where the other two pickers should follow it.",
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.",
115
+ "pitfall": "`--ds-dropdown-panel-maxh` still reads 320px and still caps the PANEL. It is the list INSIDE that stops 40px sooner now, so raising the panel knob on its own changes nothing you can see.",
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).",
117
+ "searchHints": [
118
+ "ds-dropdown-panel-maxh",
119
+ "picker-maxh",
120
+ "<ds-select",
121
+ "max-height"
122
+ ],
123
+ "surface": "style",
124
+ "verify": "Open a ds-select with more options than fit: the list scrolls at the height you set, and one left alone shows 280px of rows.",
125
+ "restore": "--picker-maxh: 320px"
126
+ }
127
+ ],
128
+ "informational": [
129
+ "All three pickers scroll the keyboard cursor into view by default; scrollActiveIntoView=\"false\" turns it off.",
130
+ "Home and End now work on ds-multi-select and ds-autocomplete, which only ds-select had.",
131
+ "ds-autocomplete takes compareWith for object values; the default stays === so string and number values are unaffected.",
132
+ "New on all three pickers: loading, opened, closed. New on the two that filter: filterWith (a predicate, or \"none\" for a server-filtered list) and filterChange.",
133
+ "ds-multi-select and ds-autocomplete gained name, readOnly (with its readonly binding alias) and clearable, which were ds-select-only.",
134
+ "New slots on all three pickers: dsPanelHeaderTemplate, dsPanelFooterTemplate, dsGroupLabelTemplate.",
135
+ "The option row is tokenised: --ds-option-gap, --ds-option-padding, --ds-option-radius, --ds-option-row-gap, --ds-option-bg-color-active.",
136
+ "ds-multi-select no longer carries its own panel rules at all; --ds-multi-select-option-bg-color-active is an alias of the shared --ds-option-bg-color-active and still works.",
137
+ "The select-all row now reads the option row's gap and padding, so it lines up with the options below it; it was one step wider before.",
138
+ "DsOption gained disabledReason, so it type-checks on all three pickers. ds-select renders it today, announced through aria-describedby on the disabled row; ds-multi-select and ds-autocomplete accept the field and do not yet show it.",
139
+ "Type-ahead is on ds-select and ds-multi-select, not ds-autocomplete, whose trigger is a text field.",
140
+ "PageUp and PageDown move the cursor ten rows on all three pickers; none had them.",
141
+ "clear() is public on all three pickers now; it empties the value and does not move focus.",
142
+ "scrollActiveIntoView follows the KEYBOARD only — the rows also set the active index on mouseenter, and reacting to that pulled a half-visible row under the pointer.",
143
+ "aria-multiselectable stays absent from ds-select on purpose: ARIA permits it only on a multi-value listbox. docs/picker-contract.md states this so nobody adds it to satisfy the audit.",
144
+ "ds-table takes expandMode=\"single\" to keep one row open at a time; the default stays \"multiple\", which is what it did before.",
145
+ "ds-table takes expandAllToggle to put an expand-all chevron in the expander column header; it is page-scoped when paginating, like select-all, and is suppressed under expandMode=\"single\".",
146
+ "ds-table emits (rowExpanded) and (rowCollapsed), expand-all included. Neither fires for a collapse the host writes into expandedIds itself, nor for an id whose row is not in data().",
147
+ "ds-table announces \"N rows expanded\" in its live region from two rows up; a single expander already says so through its own aria-expanded.",
148
+ "ds-table no longer puts `skeleton-mode` on its inner `<table>` element. Nothing in the library styled it: the rule it switched on suppressed a row hover that used to reach every row, and that hover now needs `.clickable`, which a skeleton row never has. Only a consumer reaching in through ::ng-deep would notice.",
149
+ "The column-resize handle now carries aria-valuemin and aria-valuemax alongside aria-valuenow, all in px, while it has focus. A focusable role=\"separator\" is a range widget, so a bare pixel value was being announced against ARIA's implicit 0-100.",
150
+ "ds-loading-overlay now marks the content it covers `inert` while loading, so the keyboard cannot reach what the scrim already hides from the pointer. Anything focusable behind the scrim stops being tabbable and leaves the accessibility tree until loading ends; `aria-busy` on the host is unaffected.",
151
+ "inertContent=\"false\" on ds-loading-overlay turns that off, for a scrim that covers only part of its content — the consumer then owns marking the covered subtree. ds-table does this: its scrim starts below the header, and only `<tbody>` goes inert, so sorting and filtering during a refresh still work.",
152
+ "ds-table's column resize now stops at the width of the scroll viewport, on both the pointer and the keyboard path. It was unbounded before. The bound exists so the handle's aria-valuemax is true — a focusable role=\"separator\" is a range widget, and it had been announcing a ceiling nothing applied.",
153
+ "ds-table hides its column-resize handle under `(hover: none) and (pointer: coarse)` and puts −/+/Fit width controls in the column panel instead, which opens as a ds-bottom-sheet there. Nothing to change in a consumer app; a screenshot test taken on a touch profile will differ.",
154
+ "A ds-table loading scrim used to be sized to one viewport of the table and travelled with the content, so horizontal scrolling left the revealed columns uncovered. The overlay wraps the scroll container now and the scrim covers what is on screen at any offset. NO ACTION.",
155
+ "maxVisibleChips=\"fit\" on ds-multi-select and ds-autocomplete under-showed chips on a trigger that hugs its content: the width it measured was decided by the chips it was about to cut. It reads the space available now. A width=\"fill\" trigger is unaffected. NO ACTION."
156
+ ],
157
+ "deleteList": []
158
+ }
@@ -48,13 +48,25 @@
48
48
  {
49
49
  "id": "surface-subtle-token-rename",
50
50
  "kind": "token-rename",
51
- "old": "--surface-subtle",
52
- "new": "--surface-subtitle",
53
- "action": "Replace `--surface-subtle` with `--surface-subtitle`.",
51
+ "old": "--<role>-subtle",
52
+ "new": "--<role>-subtitle",
53
+ "action": "Rename the suffix on all eight: `--border-subtle`, `--error-subtle`, `--info-subtle`, `--primary-subtle`, `--secondary-subtle`, `--success-subtle`, `--tertiary-subtle`, `--warning-subtle` each become `--<role>-subtitle`. A plain search-and-replace of `-subtle` to `-subtitle` inside a custom-property name does the whole set.",
54
+ "appliesWhen": "Only a stylesheet or template of yours that reads one of the eight by name. A consumer who never overrode a subtle token has nothing to do.",
55
+ "pitfall": "The old names do not error and do not warn — a `var(--primary-subtle)` that no longer resolves falls back to nothing, so the element loses its tint and keeps rendering. Only looking at the screen finds it.",
56
+ "note": "Eight semantic tint tokens changed suffix: the `-subtle` family became `-subtitle` across border, error, info, primary, secondary, success, tertiary and warning. There is no `--surface-subtle` in this library and there never was.",
54
57
  "searchHints": [
55
- "--surface-subtle"
58
+ "-subtle",
59
+ "--border-subtle",
60
+ "--error-subtle",
61
+ "--info-subtle",
62
+ "--primary-subtle",
63
+ "--secondary-subtle",
64
+ "--success-subtle",
65
+ "--tertiary-subtle",
66
+ "--warning-subtle"
56
67
  ],
57
- "surface": "style"
68
+ "surface": "style",
69
+ "verify": "No stylesheet of yours reads a `--*-subtle` custom property any more, and every tint that was styled through one still paints."
58
70
  },
59
71
  {
60
72
  "id": "success-subtle-token-rename",
@@ -25,7 +25,7 @@
25
25
  "warning": "color=\"warning\"",
26
26
  "text": "variant=\"text\""
27
27
  },
28
- "surface": "template",
28
+ "surface": ["template", "style", "typescript"],
29
29
  "verify": "No ds-button carries a variant value outside the shipped set, and every button that used to name a colour through `variant` now names it through the colour input. Buttons render in the colour they did before the upgrade, not all in the default."
30
30
  },
31
31
  {
@@ -3,9 +3,9 @@
3
3
  "items": [
4
4
  {
5
5
  "id": "surface-motion-partial-a-la-carte",
6
- "kind": "scss-api",
7
- "old": "@use '@ids-group-ltd/ids-design-system/styles/overlay-motion';",
8
- "new": "@use '@ids-group-ltd/ids-design-system/styles/surface-motion';\n@use '@ids-group-ltd/ids-design-system/styles/overlay-motion';",
6
+ "kind": "code-add",
7
+ "old": null,
8
+ "new": "@use '@ids-group-ltd/ids-design-system/styles/surface-motion';",
9
9
  "action": "Add `@use '@ids-group-ltd/ids-design-system/styles/surface-motion';` to your styles entry, beside `styles/overlay-motion`. If you have no overlay-motion line, put it beside whatever DS partials you do `@use`. Order does not matter.",
10
10
  "appliesWhen": "Only à-la-carte consumers who `@use` DS partials individually. `styles/ds` forwards it, so its users need nothing at all.",
11
11
  "pitfall": "Missing it fails SILENTLY — no error, no warning. The keyframes simply do not exist, and modal, drawer, bottom-sheet, toast, banner, alert, loading-overlay and the overlay panels all render with no entrance animation. Write the package-qualified specifier too: a bare `styles/…` does not resolve in a consumer build.",
@@ -194,8 +194,8 @@
194
194
  "new": null,
195
195
  "action": "Build after upgrading: the compiler raises most of these collisions, but NOT the ones named in `pitfall` below — check those by hand, because they compile clean. Then per member: rename your own, or add `override` where the base semantics genuinely match.",
196
196
  "appliesWhen": "Only a consumer that EXTENDS a DS component class. Subclassing is unsupported (design-system.md § Components); template users need nothing.",
197
- "pitfall": "Two things the compiler will NOT tell you. `isStriped()` keeps its signature but now takes an ABSOLUTE row index rather than a window-relative one, so a subclass that overrode it silently computes the wrong row. And `distinctValuesOf()` was replaced by `optionsFor()` — a subclass that CALLED the old name loses it silently at the call site while only the declaration errors. Also note both CVA bases gained a `focus()` inherited by every field control, so a subclass with its own needs `override`, and four new exported symbols can shadow a local name: FieldGroupComponent, DS_FIELD_GROUP, HeaderFilterDirective, HeaderFilterContext.",
198
- "note": "TableComponent changed by far the most; ModalComponent, ModalCardComponent, InputComponent, TextareaComponent, SelectComponent, AutocompleteComponent, BreadcrumbsComponent, MenuItemComponent, AppLayoutComponent, AuthLayoutComponent, TabsComponent, LayoutScrollService and both CVA bases also moved. TS4114 demands `override`, TS2415 fires on a redeclared private, TS2416 on a differing signature.",
197
+ "pitfall": "Two things the compiler will NOT tell you. `isStriped()` keeps its signature but now takes an ABSOLUTE row index rather than a window-relative one, so a subclass that overrode it silently computes the wrong row. And `distinctValuesOf()` was replaced by `optionsFor()` — a subclass that CALLED the old name loses it silently at the call site while only the declaration errors. Also note both CVA bases gained a `focus()` inherited by every field control, so a subclass with its own needs `override`, and five new exported symbols can shadow a local name: AuthLayoutComponent, FieldGroupComponent, DS_FIELD_GROUP, HeaderFilterDirective, HeaderFilterContext — none of these existed at 0.8.0, so they are new exports rather than grown classes.",
198
+ "note": "Seventeen classes grew a member. TableComponent changed by far the most; ModalComponent, ModalCardComponent, InputComponent, TextareaComponent, SelectComponent, AutocompleteComponent, BreadcrumbsComponent, MenuItemComponent, ButtonComponent, DatePickerComponent, SearchComponent (the last three gained `inGroup`), AppLayoutComponent, TabsComponent, LayoutScrollService and both CVA bases also moved. TS4114 demands `override`, TS2415 fires on a redeclared private, TS2416 on a differing signature.",
199
199
  "searchHints": [
200
200
  "extends TableComponent",
201
201
  "extends InputComponent",
package/package.json CHANGED
@@ -1,6 +1,6 @@
1
1
  {
2
2
  "name": "@ids-group-ltd/ids-design-system",
3
- "version": "0.11.1",
3
+ "version": "0.11.2",
4
4
  "description": "IDS Group Angular design system: components, tokens, themes",
5
5
  "license": "MIT",
6
6
  "homepage": "https://ids-ds.proto.ids-group.co.uk/",
@@ -5,6 +5,7 @@
5
5
  // declares the matching rules so the portaled panel renders styled.
6
6
 
7
7
  @use 'text-clip' as text-clip;
8
+ @use 'visually-hidden' as visually-hidden;
8
9
 
9
10
  .ds-dropdown-panel {
10
11
  /* The selected row used to paint straight from the theme roles, so a brand that
@@ -27,6 +28,12 @@
27
28
 
28
29
  /* Only bite in `content` width mode, where the pane is auto-sized: in `fill` the
29
30
  component pins the pane to the trigger and there is nothing left to bound. */
31
+ --_option-gap: var(--ds-option-gap, var(--space-2));
32
+ --_option-padding: var(--ds-option-padding, var(--space-2) var(--space-2-5));
33
+ --_option-radius: var(--ds-option-radius, var(--ds-radius-inner));
34
+ --_option-row-gap: var(--ds-option-row-gap, 2px);
35
+ --_option-bg-color-active: var(--ds-option-bg-color-active, var(--surface-secondary));
36
+
30
37
  --_dropdown-panel-bg-color: var(--ds-dropdown-panel-bg-color, var(--surface-overlay));
31
38
  --_dropdown-panel-maxh: var(--ds-dropdown-panel-maxh, 320px);
32
39
  --_dropdown-panel-minw: var(--ds-dropdown-panel-minw, 0);
@@ -55,6 +62,7 @@
55
62
  }
56
63
 
57
64
  .dropdown-list {
65
+ max-height: var(--picker-maxh);
58
66
  list-style: none;
59
67
  margin: 0;
60
68
  padding: 0;
@@ -65,14 +73,14 @@
65
73
  // would push the panel past its own max-height instead of scrolling.
66
74
  min-height: 0;
67
75
  overflow-y: auto;
68
- gap: 2px;
76
+ gap: var(--_option-row-gap);
69
77
  }
70
78
 
71
79
  .optgroup {
72
80
  list-style: none;
73
81
  display: flex;
74
82
  flex-direction: column;
75
- gap: 2px;
83
+ gap: var(--_option-row-gap);
76
84
  }
77
85
 
78
86
  .optgroup-label {
@@ -95,7 +103,7 @@
95
103
  padding: 0;
96
104
  display: flex;
97
105
  flex-direction: column;
98
- gap: 2px;
106
+ gap: var(--_option-row-gap);
99
107
  }
100
108
 
101
109
  .empty {
@@ -107,15 +115,15 @@
107
115
  .option {
108
116
  display: flex;
109
117
  align-items: center;
110
- gap: var(--space-2);
118
+ gap: var(--_option-gap);
111
119
  width: 100%;
112
- padding: var(--space-2) var(--space-2-5);
120
+ padding: var(--_option-padding);
113
121
  border: 0;
114
122
  background: transparent;
115
123
  font: var(--font-weight-medium) var(--font-size-s) / var(--line-height-flat) var(--font-sans);
116
124
  color: var(--text-primary);
117
125
  cursor: pointer;
118
- border-radius: var(--ds-radius-inner);
126
+ border-radius: var(--_option-radius);
119
127
  text-align: left;
120
128
  transition: background-color var(--duration-fast) var(--ease-standard);
121
129
 
@@ -131,6 +139,12 @@
131
139
  @include text-clip.single-line-ellipsis;
132
140
  }
133
141
 
142
+ // Visually hidden, not display:none — the latter leaves the accessibility
143
+ // tree and the reason would be announced nowhere.
144
+ .option-reason {
145
+ @include visually-hidden.visually-hidden;
146
+ }
147
+
134
148
  .option-check {
135
149
  color: var(--_option-check-color);
136
150
  flex: 0 0 auto;
@@ -140,15 +154,20 @@
140
154
  // on specificity, so without it a hovered (or keyboard-active) selected row
141
155
  // repaints to the neutral surface while KEEPING the selected label colour —
142
156
  // unreadable as soon as a brand gives the selected row a dark fill.
143
- &:hover:not(.is-disabled, .is-selected),
144
- &.is-active:not(.is-disabled, .is-selected) {
145
- background: var(--surface-secondary);
157
+ &:disabled {
158
+ color: var(--text-disabled);
159
+ cursor: not-allowed;
160
+ }
161
+
162
+ &:hover:not(.is-disabled, .is-selected, :disabled),
163
+ &.is-active:not(.is-disabled, .is-selected, :disabled) {
164
+ background: var(--_option-bg-color-active);
146
165
  }
147
166
 
148
167
  // A tap on a phone has no hover, so a pressed state is the only feedback that the
149
168
  // row was hit. One rule here covers select, autocomplete and multi-select, which
150
169
  // all render their options through this partial.
151
- &:active:not(.is-disabled) {
170
+ &:active:not(.is-disabled, :disabled) {
152
171
  background: var(--surface-muted);
153
172
  }
154
173
 
@@ -535,7 +535,7 @@
535
535
  --empty-icon-size: var(--space-16); /* 64px */
536
536
  --empty-body-maxw: 360px;
537
537
 
538
- /* Pickers — the listbox panel shared by autocomplete and multi-select. */
538
+ /* Pickers — the listbox panel shared by select, autocomplete and multi-select. */
539
539
  --picker-offset: var(--space-1); /* gap below trigger */
540
540
  --picker-maxh: 280px; /* listbox max height */
541
541
 
package/themes/README.md CHANGED
@@ -6,7 +6,7 @@ Colour is layered in three concerns: a **base palette** (theme-independent primi
6
6
 
7
7
  | Layer | Lives in | Examples | Applied at |
8
8
  | ----------------------------- | ---------------------------------------------- | ------------------------------------------------------------------------------------------------------------ | -------------------------------------------- |
9
- | **Base palette** (primitives) | `themes/_base-palette.scss` | `--blue-600`, `--cool-gray-*`, `--brand-gray-*`, `--red-h/s/l`, `--static-white`, fonts, `--shadow-tint-h/s` | `:root` (theme-independent) |
9
+ | **Base palette** (primitives) | `themes/_base-palette.scss` | `--blue-600`, `--cool-gray-*`, `--brand-gray-*`, `--red-h/s/l`, `--static-ink`, fonts, `--shadow-tint-h/s` | `:root` (theme-independent) |
10
10
  | **Theme** (role map) | `themes/_semantic.scss` + `themes/<t>/_*.scss` | `--primary`, `--surface-canvas`, `--text-primary`, the `--neutral-*` slot, `--focus-ring` | `:root` (light) / `:root[data-theme='dark']` |
11
11
  | **Component / scale** | `styles/_tokens.scss`, `*.component.scss` | `--space-*`, `--radius-*`, `--ds-button-bg-color`, `--duration-fast` | `:root` (theme-independent) |
12
12
 
@@ -14,7 +14,7 @@ Colour is layered in three concerns: a **base palette** (theme-independent primi
14
14
 
15
15
  ## Files
16
16
 
17
- - **`_base-palette.scss`** — theme-independent primitives at `:root`: hue ramps (`--blue/red/green/yellow/sky/orange-*`) + HSL channels, `--cool-gray-*` / `--brand-gray-*` ramps, `--static-white` / `--static-ink` (never flip), `--shadow-tint-h/s`, font families. Shared by every theme.
17
+ - **`_base-palette.scss`** — theme-independent primitives at `:root`: hue ramps (`--blue/red/green/yellow/sky/orange-*`) + HSL channels, `--cool-gray-*` / `--brand-gray-*` ramps, `--static-ink` (never flips), `--shadow-tint-h/s`, font families. Shared by every theme.
18
18
  - **`_semantic.scss`** — `@mixin roles`: the semantic role map (surfaces, text, icons, borders, primary/secondary/tertiary families, status, status-pills, focus). Structure is identical across themes; values resolve through each theme's own `--neutral-*` ramp. Holds the **light-default** values.
19
19
  - **`light/_palette.scss` + `light/_theme.scss`** — `@mixin palette` (the `--neutral-*` slot = cool-gray + `--shadow-tint-l: 7%`) and `@mixin theme` (`palette` + `semantic.roles`). Light is the **default** skin and needs no extra overrides.
20
20
  - **`dark/_palette.scss` + `dark/_theme.scss`** — `@mixin palette` (dark neutral ramp + `--shadow-tint-l: 95%`) and `@mixin theme` (`palette` + `semantic.roles` + the value overrides that genuinely differ on dark: tint surfaces, on-tint text, hover/pressed mixed toward white, scrim, focus-halo alpha, chart tokens).
@@ -54,7 +54,7 @@ export const appConfig: ApplicationConfig = {
54
54
 
55
55
  It sets `data-theme` from `prefers-color-scheme` at startup and keeps it in sync as the OS changes; a manual `data-theme="dark"` still wins.
56
56
 
57
- On-fill text uses theme-stable `--static-white` / `--static-ink` so it doesn't flip with the neutrals.
57
+ On-fill text is the literal `white`, or the theme-stable `--static-ink` where the fill is light, so neither flips with the neutrals.
58
58
 
59
59
  **Known limitation — `data-neutrals="brand"` + dark:** the brand-gray (hue-derived) neutral switch is a **light-theme feature**. The dark block ships its own neutral ramp and is declared last, so on `data-theme="dark"` the dark neutrals win and the brand-gray tint is ignored. (Benign — renders correct dark, just not brand-tinted neutrals.)
60
60