@ids-group-ltd/ids-design-system 0.7.0 → 0.7.1

This diff represents the content of publicly available package versions that have been released to one of the supported registries. The information contained in this diff is provided for informational purposes only and reflects changes between package versions as they appear in their respective public registries.
package/CHANGELOG.md CHANGED
@@ -8,6 +8,279 @@ While the package is on `0.x`, minor releases may contain breaking changes.
8
8
 
9
9
  ## Unreleased
10
10
 
11
+ ## 0.7.1 — 2026-08-04
12
+
13
+ ### Added
14
+
15
+ - **`TableColumn.sortValue` — sort a column by its DOMAIN value instead of the rendered text.** Without
16
+ it `clientSort` compares what the cell displays, so `$1.2M / $840K / $95K` sorted by the leading
17
+ character and `Oct 09, 2023 / Feb 27, 2024` sorted by month NAME: the table looked sorted and was not,
18
+ which is worse than leaving it unsorted. Pass an accessor per column —
19
+ `{ key: 'amount', label: 'Amount', sortValue: (row) => row.amountCents }` — returning a number, `Date`
20
+ or plain string. A consumer that had to re-parse its own rendered output (mm-broker shipped a
21
+ `display-compare.ts` sniffing currency, percents and three date formats) can delete it. Only affects
22
+ sorting: the header filter still lists what the user can see. Columns with plain numeric text already
23
+ sorted correctly and need nothing.
24
+
25
+ - **`ds-checkbox`, `ds-switch` and `ds-radio` warn in dev when a caption is projected instead of passed.**
26
+ `<ds-checkbox>Accept the terms</ds-checkbox>` renders no caption — the text comes from `[label]` only —
27
+ and it failed silently: no error, no warning, nothing in the types, so it survived review and was caught
28
+ by opening the page. All three share that contract, so all three now log which component swallowed the
29
+ text. Production is untouched: the probe that detects it is rendered only under `isDevMode()`, so no
30
+ extra node ships. Real projection support is still open — see `docs/todo.md`.
31
+
32
+ - **`ds-app-layout` collapses its rail to an off-canvas overlay below `lg`.** On narrow viewports the
33
+ rail no longer occupies a grid column: below the `lg` breakpoint (read at runtime from `--bp-lg`) it
34
+ leaves the flow, becomes a `position: fixed` panel translated off-canvas, and
35
+ animates in over a scrim. A new two-way `[(railOpen)]` model drives it (ignored at/above `lg`), and a
36
+ new `railLabel` input (`'Navigation'` by default) sets the panel's `aria-label` in compact mode. While
37
+ open and compact the panel is a focus-trapped `role="dialog"` with `aria-modal="true"`; clicking the
38
+ scrim, pressing `Escape` anywhere, navigating to a new path, or crossing back above `lg` all close it
39
+ (no body-scroll lock — the host is already `100dvh; overflow: hidden`). At/above `lg` nothing changes.
40
+ Wire a trigger — e.g. a burger in your own projected topbar — to `[(railOpen)]`. The rail keeps its DOM
41
+ position, so you still project the sidenav once. New tokens:
42
+ `--ds-app-layout-rail-bg-color` (`--surface-overlay`), `--ds-app-layout-rail-shadow`
43
+ (`--shadow-modal`), `--ds-app-layout-scrim-color` (`--scrim, hsl(220deg 20% 12% / 45%)`). The
44
+ breakpoint is read from the emitted `--bp-lg` with no literal fallback, so the query and the
45
+ stylesheet's media block cannot disagree; if that custom property is missing — meaning the DS global
46
+ styles were never included — the layout stays in desktop mode and says so in dev rather than guessing
47
+ a width.
48
+
49
+ - **`dsReserveMessages` — turn on the reserved message row for a whole form at once.** With
50
+ `reserveMessage` now off by default, a validated form would otherwise repeat `[reserveMessage]="true"`
51
+ on every control. Put the directive on the form and every DS field declared inside it reserves:
52
+ `<form dsReserveMessages>…</form>`. It provides `DS_CONFIG` for its subtree, so it composes with the
53
+ app-level config instead of replacing it, and a field's own `[reserveMessage]` still wins so one
54
+ control can opt back out. The switch is the directive's presence, not an input — providers resolve
55
+ before inputs exist. Note it applies to fields **declared** inside the host: projected content keeps
56
+ the injector of the template it was written in.
57
+
58
+ - **`ds-time-picker` gains `label`, `required` and `optional` — a date + time row now aligns without a
59
+ hand-rolled label.** The time picker had no label API at all, so a labelled form row meant authoring the
60
+ label yourself; the date picker's own label reserved a row the time picker did not, leaving the two
61
+ triggers 22.8px apart vertically. The label renders the same `.label` block with the same tokens as
62
+ `ds-date-picker`, and drives the single-mode trigger's accessible name (`aria-labelledby` when a label
63
+ is set, `aria-label` when it is not) plus `aria-required`; range mode's start/end segment triggers are
64
+ not wired to the label yet.
65
+ Measured on a two-column probe, date vs time now differ by 0px on label top/height, trigger
66
+ top/height/bottom, value inset and glyph top.
67
+
68
+ - **The value typography of both pickers is now tokenised.** It was hardcoded: the date value was pinned to
69
+ `--font-mono` and the time trigger to `--font-weight-medium`, so a brand could not bring either in line
70
+ with `ds-input` / `ds-select`. Adds `--ds-date-picker-value-font-family` / `-font-size` / `-weight` and
71
+ `--ds-time-picker-value-font-family` / `-font-size` / `-weight`, plus `--ds-time-picker-required-color`.
72
+ The date picker's ghost mask now follows the same three tokens — without that, overriding the family
73
+ drifted the painted placeholders off the value behind them — and both the input and the mask carry
74
+ `font-variant-numeric: tabular-nums`, so a proportional override still lands on the mask.
75
+
76
+ - **`ds-modal` / `ds-modal-card` take an `[eyebrow]` slot above the title.** Dialogs that need a context
77
+ line ("MY ACTIVITY · ROBERT THOMPSON") had to put it as the first line of the body. The slot renders
78
+ nothing when unfilled, and ships uppercase + tracked by default, retunable via
79
+ `--ds-modal-eyebrow-text-color` / `-font-size` / `-weight` / `-tracking` / `-transform`. Internally the
80
+ `<h2 class="title">` and the eyebrow are now wrapped together in a `<div class="heading">` that carries
81
+ the `flex: 1` the `<h2>` used to hold — a consumer whose own CSS targeted `.modal-card .title` for that
82
+ flex must retarget `.heading`.
83
+
84
+ - **`ds-table` takes a `rowId` accessor.** Row identity (tracking, selection, expansion, the active-row
85
+ highlight) defaulted to `row.id`, so display-only data with no natural key had to be mapped through a
86
+ synthetic id just to satisfy the generic. Pass `[rowId]="row => row.channel + row.sentAt"` instead; the
87
+ row type relaxes from `{ id: string }` to `object`, and the resolver is public as `rowKey(row)` for hosts
88
+ reading `selectedIds` / `expandedIds`. Rows keeping an `id` need no change.
89
+
90
+ - **`ds-date-picker` and `ds-time-picker` take `fullWidth`.** Both hugged their content, so neither filled
91
+ a grid/flex track the way `ds-input` and `ds-select` do — a mixed form row had to pin the picker widths
92
+ by hand. Opt-in; the default stays hug-your-content.
93
+
94
+ - **`ds-pagination` takes `showPageSize`, and its range label is tokenised.** A screen with a fixed page
95
+ size had to hide the rows-per-page dropdown in CSS; the label could only be switched off, not restyled.
96
+ Adds `--ds-pagination-label-font-size` / `-weight` / `-color`.
97
+
98
+ - **`ds-table` per-side cell padding + header tokens.** `--ds-table-cell-pad-{top,right,bottom,left}` each
99
+ fall back to the existing `-pad-x` / `-pad-y` pair, so an editorial table can ask for a right-only gutter
100
+ (first column flush) without redefining both axes. Also adds `--ds-table-head-border-color`,
101
+ `--ds-table-head-weight` and `--ds-table-head-tracking`.
102
+
103
+ - **`DS_CONFIG.field.reserveMessage` sets the message-row default app-wide.** With the per-field default
104
+ now `false` (see Changed), a form that validates throughout can turn the reserved row back on in one
105
+ place: `provideDsConfig({ field: { reserveMessage: true } })` covers all 14 message-bearing fields
106
+ instead of repeating `[reserveMessage]="true"` on every control; a per-field input still wins. The
107
+ input's type widens from `boolean` to `boolean | null` (`null` = "not set" → fall through to the config,
108
+ then to the hard-coded fallback), so existing bindings and bare attributes behave exactly as before.
109
+
110
+ - **`focus()` on `ds-search`, `ds-input` and `ds-textarea`.** The search input was only reachable from
111
+ inside the component, so a filter toolbar's Clear button — disabled once there is nothing left to clear —
112
+ blurred into `<body>` and restarted Tab order at the top of the document. Also gives forms a way to
113
+ focus the first invalid field.
114
+
115
+ - **Five override tokens that were previously hardcoded:** `--ds-modal-title-font-size` (pairs with the
116
+ existing `-title-weight`), `--ds-date-picker-trigger-radius` (the counterpart of
117
+ `--ds-time-picker-trigger-radius`), `--ds-date-picker-panel-radius` (forwarded onto the portaled pane),
118
+ `--ds-checkbox-radius` (the box only — the indeterminate dash keeps its own), and `--ds-menu-max-width`.
119
+ `ds-toast` also gains `--ds-toast-min-width` / `--ds-toast-max-width` as per-instance hooks over the
120
+ global `--toast-minw` / `--toast-maxw` geometry. All default to the current values.
121
+
122
+ - **`--ds-popover-min-width` and `--ds-menu-min-width`.** A popover (or a `ds-menu` projected into one)
123
+ hugged its content with no way to widen it — `--ds-popover-max-width` was the only size hook, so a user
124
+ menu that should be wider than its longest item needed global CSS against `.popover` / `ds-menu`. Both
125
+ default to `auto` (today's behaviour) and both are forwarded onto the portaled overlay pane on open, so
126
+ scoping them per instance (`ds-popover { --ds-popover-min-width: 220px; }`) works.
127
+
128
+ - **Surface entrances are now customizable per surface, via four shipped presets.** Every DS surface
129
+ names its entrance through `--ds-<surface>-enter-keyframes` and takes `-enter-duration` / `-enter-easing`
130
+ (plus `-enter-offset` or `-enter-scale` for the travel/scale a preset reads); surfaces that animate on
131
+ close also take `-leave-duration` / `-leave-easing`. Covered: overlay panels (`--ds-overlay-*`, shared by
132
+ select, multi-select, autocomplete, date / time / colour picker, popover, tooltip and menu submenus),
133
+ modal, drawer, bottom sheet, toast, banner, alert and loading overlay. The presets are global keyframes —
134
+ `ds-slide-in` (fade + short travel), `ds-scale-in` (grows from a micro-scale), `ds-fade-in` (opacity only)
135
+ and `ds-slide-edge-in` (full-distance travel, no fade) — so `ds-select { --ds-overlay-enter-keyframes:
136
+ ds-fade-in; }` is enough to re-skin one instance, and portaled panels forward the tokens onto their
137
+ overlay pane on open — every one except `--ds-overlay-enter-scale`, which is not forwarded, so scaling
138
+ one overlay panel per instance does not work yet (scope it globally instead). Your own `@keyframes` work
139
+ too, but must be declared in GLOBAL styles: emulated
140
+ view encapsulation renames keyframes defined in a component stylesheet. `none` disables an entrance.
141
+ All defaults are unchanged. Leave keyframes are deliberately not swappable — modal/drawer/bottom-sheet
142
+ teardown matches them by name — and reduced motion still wins: the library zeroes the duration itself,
143
+ so a custom entrance carrying its own timing is silenced too. New: `src/lib/styles/_surface-motion.scss`
144
+ (exported from `styles/ds`; add it alongside `styles/overlay-motion` if you import partials à la carte).
145
+
146
+ ### Changed
147
+
148
+ - **`clientSort` now sinks blank cells to the bottom in BOTH directions, and collates text naturally.**
149
+ Two changes to how an existing table sorts, both deliberate. (1) A cell that reads as "no data" — empty,
150
+ `—`, `–`, `-`, `n/a`, `never`, `none`, matched case-insensitively — sorts last regardless of direction,
151
+ so a descending sort no longer opens with a screen of empty rows. Previously an empty string was simply
152
+ the smallest value and floated to the top. (2) The text fallback now passes `{ numeric: true }` to
153
+ `localeCompare`, so `item 9` comes before `item 10` instead of after it. Both apply to every
154
+ `clientSort` column, with or without the new `sortValue`. If a table relied on blanks sorting first,
155
+ supply a `sortValue` that maps them to a real value.
156
+
157
+ - **Several exported component classes change their member surface, which breaks a consumer that extends
158
+ them.** Everything else in this release is additive for anyone using the `<ds-…>` elements. Subclassing
159
+ a DS component is unsupported (`design-system.md` § Components), but where it happens the names collide —
160
+ TS4114 demands an `override` modifier, TS2415 fires on a redeclared private member, TS2416 where a
161
+ signature differs. New members this range: all 14 message-bearing field components gain
162
+ `reserveMessageResolved`, and `CheckboxComponent`, `SwitchComponent` and `RadioComponent` also gain a
163
+ protected `devMode`; `InputComponent` and `TextareaComponent` also gain `control` and `focus`, and
164
+ `SearchComponent` gains `focus`; `TableComponent` gains `rowId` and `rowKey`; `PaginationComponent`
165
+ gains `showPageSize`; `TimePickerComponent` gains `label`, `required`, `optional`, `labelId` and
166
+ `fullWidth`; `DatePickerComponent` gains `fullWidth`; and `AppLayoutComponent` gains `railOpen`,
167
+ `railLabel`, `compact`, `closeRail` and the private `navigation`, `destroyRef` and
168
+ `watchDesktopBreakpoint`. One REMOVAL: `TooltipDirective` (`dsTooltip`) drops its protected `onOpen`,
169
+ split into `onPointerEnter` / `onFocusIn` / `onFocusOut` plus a private `scheduleShow`,
170
+ `describedElement` and `focusedTarget` — a subclass that overrode `onOpen` no longer compiles, because
171
+ its `override` now names a member the base does not declare. Rename the subclass's own member, or add
172
+ `override` where the base's semantics genuinely match. Build after upgrading — the compiler enumerates
173
+ every collision.
174
+
175
+ - **A nested `provideDsConfig` now MERGES with the config above it instead of replacing it.** The
176
+ config resolves through the element-injector chain, so it was always scopable to a route, component
177
+ or directive — but because the provider used `useValue`, a subtree that set one flag silently dropped
178
+ every unrelated app-level setting (scoping `field.reserveMessage` on a form would reset
179
+ `datePicker.locale`, `timePicker.format`, `breadcrumbs.separator` to their defaults, with no error).
180
+ Merging is section by section: only the keys you name are replaced. No action needed — a single
181
+ root-level call behaves exactly as before, and nested provision was neither documented nor usable
182
+ safely. The merge runs through a newly exported helper, `inheritDsConfig(config)`, which reads the
183
+ nearest ancestor config (`skipSelf`, `optional`) and shallow-merges per top-level section; call it from
184
+ within an injection context if you need the same behaviour in your own factory provider or directive
185
+ metadata. This is what makes `dsReserveMessages` composable.
186
+
187
+ - **BREAKING (layout): `reserveMessage` now defaults to `false` on every field.** It shipped default-on
188
+ in 0.7.0; the reserved row is right for a form that validates and wrong for the many forms that never
189
+ show a message, where it added ~23px of dead space under every control and made a normal 16px field
190
+ stack read as a ~39px hole. The resolution chain is unchanged — per-field input, then
191
+ `DS_CONFIG.field.reserveMessage`, then the default — only the final fallback flipped, so all 14
192
+ message-bearing fields follow (`ds-input`, `ds-textarea`, `ds-select`, `ds-autocomplete`,
193
+ `ds-multi-select`, `ds-checkbox`, `ds-radio`, `ds-radio-group`, `ds-switch`, `ds-slider`,
194
+ `ds-date-picker`, `ds-time-picker`, `ds-color-picker`, `ds-otp-input`). **To restore 0.7.0 behaviour
195
+ exactly, one line:** `provideDsConfig({ field: { reserveMessage: true } })`. Per form or per field,
196
+ bind `[reserveMessage]="true"`. Two clean-ups this enables: existing `[reserveMessage]="false"`
197
+ bindings are now redundant and can be deleted, and any tighter sub-stack added to absorb the reserved
198
+ gap should go back to the normal stack spacing.
199
+
200
+ - **`ds-time-picker` matches the field family: the clock glyph moved to the trailing edge, the value
201
+ weight dropped to regular, and the trigger gap narrowed.** The glyph rendered BEFORE the value at 14px
202
+ while every sibling field (`ds-date-picker`, `ds-select`, `ds-input`) puts its affordance last at 16px, so
203
+ a date + time row read as two mirrored controls; the trigger also carried `--font-weight-medium` against
204
+ the family's regular, and an 8px gap against 4px. Purely visual — set
205
+ `--ds-time-picker-value-weight: var(--font-weight-medium)` to keep the old weight.
206
+
207
+ - **`fullWidth` on `ds-date-picker` now pushes the calendar glyph to the trailing edge.** Stretching the
208
+ trigger left the value + glyph packed at the left (the glyph sat 122px short of the right edge on a 274px
209
+ field), so a full-width date field did not line up with the time picker or a `ds-select` beside it.
210
+
211
+ - **Overlay panels now enter FROM their trigger edge instead of always sliding downward.** A panel below
212
+ its trigger still slides down into place; one placed above now rises, and a side-placed panel comes in
213
+ horizontally — `ds-scale-in` likewise grows out of the anchored edge. Previously every panel, including
214
+ a tooltip sitting above its trigger, animated top-down. Purely visual; no API change.
215
+
216
+ ### Fixed
217
+
218
+ - **`dsTooltip` now describes the element that actually takes focus, so a tooltip on a non-focusable
219
+ host reaches a screen reader.** It set `aria-describedby` on its host unconditionally. That is right
220
+ when the host is the control, but `ds-menu-item` carries `role="none"` and puts the real `<button>`
221
+ inside, so the description landed on an element the user never focuses: a disabled menu item showed
222
+ its "why" to sighted keyboard users and to nobody else. The directive now records the target of the
223
+ `focusin` event — which bubbles, so it IS whatever took focus — and describes that. A pointer-only
224
+ open still uses the host, where no screen reader is involved. Deliberately not implemented by
225
+ searching the host's subtree for something focusable: that would put the tooltip inside another
226
+ component's internal DOM and hard-code a list of what counts as focusable.
227
+
228
+ - **`ds-pagination`'s rows-per-page dropdown no longer follows the app's field defaults.** The internal
229
+ `ds-select` was rendered without a `reserveMessage` binding, so it inherited whatever the app had set —
230
+ and a page-size dropdown shows neither hint nor error, so it had nothing to reserve. With the row
231
+ reserved the pager measured 54.8px instead of 32 and, because the `nav` centres its children, the
232
+ select's control sat ~11px above the page buttons' baseline. It is now pinned off inside the template,
233
+ which also makes it immune in the other direction: an app that opts back in with
234
+ `provideDsConfig({ field: { reserveMessage: true } })` or wraps a region in `dsReserveMessages` no
235
+ longer re-breaks every pager inside it. A consumer that collapsed the row with a global
236
+ `ds-pagination ds-field-message { display: none }` can drop that rule.
237
+
238
+ - **`ds-stat`'s card now fills a stretched host, so a KPI row renders equal-height tiles.** The host is
239
+ `display: block` and `.stat` carried no height, so in a `1fr` grid track the host stretched while the
240
+ visible surface stayed content-sized: three tiles where only two had a `caption` painted 102.1px inside
241
+ 126.9px hosts, leaving 24.8px of empty cell under the odd one out. It reads as a layout bug rather than
242
+ as a missing caption, and no token reached it — consumers were shipping
243
+ `ds-stat { height: 100%; .stat { height: 100% } }` from a global stylesheet against DS-internal markup.
244
+ A tile in an unstretched context is unaffected, since the host is still content-sized there.
245
+
246
+ - **`ds-app-layout` no longer scrolls the content back to top on a same-page URL change.**
247
+ `LayoutScrollService` reset the scroll on every router `NavigationEnd`, so a sort, page or filter change
248
+ that only rewrites the query string or fragment yanked the user to the top of the list. It now compares
249
+ the path (the part before `?` / `#`) and only resets when the path itself changes; `scrollToTop()` stays
250
+ public for a host that wants to reset explicitly, which is per-interaction and therefore more precise
251
+ than the old blanket reset.
252
+
253
+ - **`ds-table`'s header no longer desyncs when a host maps the "off" sort click back to its own default.**
254
+ Cycling past `desc` nulled `sortKey` internally; a server-paged host that cannot honour "unordered" pushes
255
+ its default key back, and on the *default* column that write is a no-op for Angular's binding diff — so the
256
+ table kept `sortKey === null`, leaving rows ordered while every header showed the neutral icon and
257
+ `aria-sort="none"`. The key now survives the cycle and `sortDir === null` alone means unsorted; rendering
258
+ is unchanged. **If your host reads `sortKey` to decide whether a sort is active, gate on `sortDir`
259
+ instead** — `sortKey` is now non-null after the third click (it names the column the user last touched),
260
+ so `if (sortKey) …` would keep sorting where it previously stopped.
261
+
262
+ - **A selected dropdown option no longer loses its tint to the hover/keyboard-active state.** In
263
+ `styles/_dropdown-overlay.scss` the `:hover` / `.is-active` branch out-ranked `.is-selected` on
264
+ specificity, so it repainted the row to `--surface-secondary` while keeping the selected label colour —
265
+ and because the panel seeds `.is-active` on the selected option when it opens, it showed at REST too, not
266
+ only under the cursor. A brand that gives the selected row a dark fill got unreadable text. The neutral
267
+ branch is now scoped with `:not(.is-selected)` and the selected row has its own hover/active step
268
+ (`--primary-muted`).
269
+
270
+ - **A read-only `ds-modal` no longer draws an empty footer strip.** `.actions` rendered its `border-top`
271
+ and padding even with nothing projected into `[actions]`; it now hides when empty, the same guard the
272
+ card already used for `.impact`.
273
+
274
+ - **`ds-docs`-style à la carte consumers were missing the overlay-panel entrance.** `styles/overlay-motion`
275
+ is now imported by the docs app itself, so portaled panels animate there as they do for consumers of the
276
+ bundled `styles/ds` entry.
277
+
278
+ - **Dialogs opened through `ModalService` no longer carry the `ds-overlay-pane` panel class.**
279
+ `ModalService.open()` — and therefore `confirm()` — tagged the CDK overlay pane with `ds-overlay-pane`,
280
+ which layered the shared overlay-panel entrance onto the modal on top of its own card/backdrop
281
+ animation; the class is dropped, so `styles/overlay-motion` no longer applies to the pane and the modal
282
+ plays only its own `--ds-modal-*` entrance.
283
+
11
284
  ## 0.7.0 — 2026-07-30
12
285
 
13
286
  ### Changed
@@ -50,6 +323,12 @@ While the package is on `0.x`, minor releases may contain breaking changes.
50
323
  `-pad-y` / `-content-max-width` / `-height` → `--ds-app-layout-*`). Behaviour is unchanged — rename the
51
324
  references (see `migrations/`). A consumer still on 0.6.3's `ds-app-shell` must migrate.
52
325
 
326
+ - **Retroactive note: `TableComponent` gained four more members (`total`, `sortingOrder`,
327
+ `animateHeight`, `scrollToTopOnPageChange`), and most other component classes changed too**, so a
328
+ consumer that extends a DS class (unsupported — `design-system.md` § Components) can collide on a
329
+ name here as well, exactly as in 0.6.3. Same resolution: rename the subclass's own member, or add
330
+ `override` where the base's semantics genuinely match.
331
+
53
332
  ### Added
54
333
 
55
334
  - **New override tokens for two baked-in weights: `--ds-sidenav-item-label-weight` and
@@ -279,6 +558,15 @@ While the package is on `0.x`, minor releases may contain breaking changes.
279
558
  - **`ds-toast` now slides up from below into place as it enters** (previously it dropped in from
280
559
  slightly above). The exit animation is unchanged — the toast still slides up as it fades out.
281
560
  Visual/motion only; no API change.
561
+ - **Retroactive note: the new `ds-table` column API grew `TableComponent`'s member surface by ~76
562
+ names, which breaks a consumer that extends the class.** Everything above is additive for anyone
563
+ using the `<ds-table>` element. Subclassing a DS component is unsupported (`design-system.md`
564
+ § Components), but where it happens the new names collide — TS4114 demands an `override` modifier,
565
+ TS2416 fires where the signature differs. Collisions seen in the wild: `zebra`, `columnOrder`,
566
+ `orderedColumns`, `visibleColumns`, `toggleColumn`, `onColumnDrop`, `moveColumn`, `resetColumns`,
567
+ `columnFilters`, `exportCsv`, `onResizeMove`, `onResizeEnd`. Rename the subclass's own member, or
568
+ add `override` where the base's semantics genuinely match (`zebra` must then adopt the base's
569
+ `booleanAttribute` transform). Build after upgrading — the compiler enumerates every collision.
282
570
 
283
571
  ### Fixed
284
572