@ids-group-ltd/ids-design-system 0.12.0 → 0.12.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.
- package/CHANGELOG.md +568 -52
- package/fesm2022/ids-group-ltd-ids-design-system-components-accordion.mjs +2 -2
- package/fesm2022/ids-group-ltd-ids-design-system-components-accordion.mjs.map +1 -1
- package/fesm2022/ids-group-ltd-ids-design-system-components-alert.mjs +2 -2
- package/fesm2022/ids-group-ltd-ids-design-system-components-alert.mjs.map +1 -1
- package/fesm2022/ids-group-ltd-ids-design-system-components-app-layout.mjs +2 -2
- package/fesm2022/ids-group-ltd-ids-design-system-components-app-layout.mjs.map +1 -1
- package/fesm2022/ids-group-ltd-ids-design-system-components-auth-layout.mjs +4 -4
- package/fesm2022/ids-group-ltd-ids-design-system-components-auth-layout.mjs.map +1 -1
- package/fesm2022/ids-group-ltd-ids-design-system-components-autocomplete.mjs +10 -13
- package/fesm2022/ids-group-ltd-ids-design-system-components-autocomplete.mjs.map +1 -1
- package/fesm2022/ids-group-ltd-ids-design-system-components-avatar-group.mjs +2 -2
- package/fesm2022/ids-group-ltd-ids-design-system-components-avatar-group.mjs.map +1 -1
- package/fesm2022/ids-group-ltd-ids-design-system-components-avatar.mjs +2 -2
- package/fesm2022/ids-group-ltd-ids-design-system-components-avatar.mjs.map +1 -1
- package/fesm2022/ids-group-ltd-ids-design-system-components-badge.mjs +2 -2
- package/fesm2022/ids-group-ltd-ids-design-system-components-badge.mjs.map +1 -1
- package/fesm2022/ids-group-ltd-ids-design-system-components-banner.mjs +2 -2
- package/fesm2022/ids-group-ltd-ids-design-system-components-banner.mjs.map +1 -1
- package/fesm2022/ids-group-ltd-ids-design-system-components-bottom-sheet.mjs +2 -2
- package/fesm2022/ids-group-ltd-ids-design-system-components-bottom-sheet.mjs.map +1 -1
- package/fesm2022/ids-group-ltd-ids-design-system-components-breadcrumbs.mjs +2 -2
- package/fesm2022/ids-group-ltd-ids-design-system-components-breadcrumbs.mjs.map +1 -1
- package/fesm2022/ids-group-ltd-ids-design-system-components-button.mjs +2 -2
- package/fesm2022/ids-group-ltd-ids-design-system-components-button.mjs.map +1 -1
- package/fesm2022/ids-group-ltd-ids-design-system-components-calendar-day.mjs +2 -2
- package/fesm2022/ids-group-ltd-ids-design-system-components-calendar-day.mjs.map +1 -1
- package/fesm2022/ids-group-ltd-ids-design-system-components-card.mjs +2 -2
- package/fesm2022/ids-group-ltd-ids-design-system-components-card.mjs.map +1 -1
- package/fesm2022/ids-group-ltd-ids-design-system-components-checkbox.mjs +2 -2
- package/fesm2022/ids-group-ltd-ids-design-system-components-checkbox.mjs.map +1 -1
- package/fesm2022/ids-group-ltd-ids-design-system-components-color-picker.mjs +10 -7
- package/fesm2022/ids-group-ltd-ids-design-system-components-color-picker.mjs.map +1 -1
- package/fesm2022/ids-group-ltd-ids-design-system-components-date-picker.mjs +13 -9
- package/fesm2022/ids-group-ltd-ids-design-system-components-date-picker.mjs.map +1 -1
- package/fesm2022/ids-group-ltd-ids-design-system-components-description-list.mjs +2 -2
- package/fesm2022/ids-group-ltd-ids-design-system-components-description-list.mjs.map +1 -1
- package/fesm2022/ids-group-ltd-ids-design-system-components-drawer.mjs +2 -2
- package/fesm2022/ids-group-ltd-ids-design-system-components-drawer.mjs.map +1 -1
- package/fesm2022/ids-group-ltd-ids-design-system-components-dropzone.mjs +2 -2
- package/fesm2022/ids-group-ltd-ids-design-system-components-dropzone.mjs.map +1 -1
- package/fesm2022/ids-group-ltd-ids-design-system-components-empty-state.mjs +2 -2
- package/fesm2022/ids-group-ltd-ids-design-system-components-empty-state.mjs.map +1 -1
- package/fesm2022/ids-group-ltd-ids-design-system-components-field-message.mjs +2 -2
- package/fesm2022/ids-group-ltd-ids-design-system-components-field-message.mjs.map +1 -1
- package/fesm2022/ids-group-ltd-ids-design-system-components-filter-bar.mjs +2 -2
- package/fesm2022/ids-group-ltd-ids-design-system-components-filter-bar.mjs.map +1 -1
- package/fesm2022/ids-group-ltd-ids-design-system-components-icon-button.mjs +2 -2
- package/fesm2022/ids-group-ltd-ids-design-system-components-icon-button.mjs.map +1 -1
- package/fesm2022/ids-group-ltd-ids-design-system-components-input.mjs +2 -2
- package/fesm2022/ids-group-ltd-ids-design-system-components-input.mjs.map +1 -1
- package/fesm2022/ids-group-ltd-ids-design-system-components-list.mjs +2 -2
- package/fesm2022/ids-group-ltd-ids-design-system-components-list.mjs.map +1 -1
- package/fesm2022/ids-group-ltd-ids-design-system-components-loading-overlay.mjs +2 -2
- package/fesm2022/ids-group-ltd-ids-design-system-components-loading-overlay.mjs.map +1 -1
- package/fesm2022/ids-group-ltd-ids-design-system-components-menu.mjs +12 -5
- package/fesm2022/ids-group-ltd-ids-design-system-components-menu.mjs.map +1 -1
- package/fesm2022/ids-group-ltd-ids-design-system-components-modal.mjs +6 -6
- package/fesm2022/ids-group-ltd-ids-design-system-components-modal.mjs.map +1 -1
- package/fesm2022/ids-group-ltd-ids-design-system-components-multi-select.mjs +10 -13
- package/fesm2022/ids-group-ltd-ids-design-system-components-multi-select.mjs.map +1 -1
- package/fesm2022/ids-group-ltd-ids-design-system-components-number-stepper.mjs +2 -2
- package/fesm2022/ids-group-ltd-ids-design-system-components-number-stepper.mjs.map +1 -1
- package/fesm2022/ids-group-ltd-ids-design-system-components-otp-input.mjs +2 -2
- package/fesm2022/ids-group-ltd-ids-design-system-components-otp-input.mjs.map +1 -1
- package/fesm2022/ids-group-ltd-ids-design-system-components-pagination.mjs +2 -2
- package/fesm2022/ids-group-ltd-ids-design-system-components-pagination.mjs.map +1 -1
- package/fesm2022/ids-group-ltd-ids-design-system-components-password-rules.mjs +2 -2
- package/fesm2022/ids-group-ltd-ids-design-system-components-password-rules.mjs.map +1 -1
- package/fesm2022/ids-group-ltd-ids-design-system-components-popover.mjs +15 -7
- package/fesm2022/ids-group-ltd-ids-design-system-components-popover.mjs.map +1 -1
- package/fesm2022/ids-group-ltd-ids-design-system-components-progress.mjs +2 -2
- package/fesm2022/ids-group-ltd-ids-design-system-components-progress.mjs.map +1 -1
- package/fesm2022/ids-group-ltd-ids-design-system-components-radio-group.mjs +21 -8
- package/fesm2022/ids-group-ltd-ids-design-system-components-radio-group.mjs.map +1 -1
- package/fesm2022/ids-group-ltd-ids-design-system-components-search.mjs +2 -2
- package/fesm2022/ids-group-ltd-ids-design-system-components-search.mjs.map +1 -1
- package/fesm2022/ids-group-ltd-ids-design-system-components-segmented.mjs +2 -2
- package/fesm2022/ids-group-ltd-ids-design-system-components-segmented.mjs.map +1 -1
- package/fesm2022/ids-group-ltd-ids-design-system-components-select.mjs +10 -13
- package/fesm2022/ids-group-ltd-ids-design-system-components-select.mjs.map +1 -1
- package/fesm2022/ids-group-ltd-ids-design-system-components-sidenav-footer.mjs +2 -2
- package/fesm2022/ids-group-ltd-ids-design-system-components-sidenav-footer.mjs.map +1 -1
- package/fesm2022/ids-group-ltd-ids-design-system-components-sidenav.mjs +15 -8
- package/fesm2022/ids-group-ltd-ids-design-system-components-sidenav.mjs.map +1 -1
- package/fesm2022/ids-group-ltd-ids-design-system-components-skeleton.mjs +2 -2
- package/fesm2022/ids-group-ltd-ids-design-system-components-skeleton.mjs.map +1 -1
- package/fesm2022/ids-group-ltd-ids-design-system-components-slider.mjs +2 -2
- package/fesm2022/ids-group-ltd-ids-design-system-components-slider.mjs.map +1 -1
- package/fesm2022/ids-group-ltd-ids-design-system-components-split-button.mjs +15 -5
- package/fesm2022/ids-group-ltd-ids-design-system-components-split-button.mjs.map +1 -1
- package/fesm2022/ids-group-ltd-ids-design-system-components-stat.mjs +2 -2
- package/fesm2022/ids-group-ltd-ids-design-system-components-stat.mjs.map +1 -1
- package/fesm2022/ids-group-ltd-ids-design-system-components-stepper.mjs +2 -2
- package/fesm2022/ids-group-ltd-ids-design-system-components-stepper.mjs.map +1 -1
- package/fesm2022/ids-group-ltd-ids-design-system-components-switch.mjs +2 -2
- package/fesm2022/ids-group-ltd-ids-design-system-components-switch.mjs.map +1 -1
- package/fesm2022/ids-group-ltd-ids-design-system-components-table-columns.mjs +428 -0
- package/fesm2022/ids-group-ltd-ids-design-system-components-table-columns.mjs.map +1 -0
- package/fesm2022/ids-group-ltd-ids-design-system-components-table-export.mjs +186 -0
- package/fesm2022/ids-group-ltd-ids-design-system-components-table-export.mjs.map +1 -0
- package/fesm2022/ids-group-ltd-ids-design-system-components-table-resize.mjs +227 -0
- package/fesm2022/ids-group-ltd-ids-design-system-components-table-resize.mjs.map +1 -0
- package/fesm2022/ids-group-ltd-ids-design-system-components-table.mjs +304 -437
- package/fesm2022/ids-group-ltd-ids-design-system-components-table.mjs.map +1 -1
- package/fesm2022/ids-group-ltd-ids-design-system-components-tabs.mjs +2 -2
- package/fesm2022/ids-group-ltd-ids-design-system-components-tabs.mjs.map +1 -1
- package/fesm2022/ids-group-ltd-ids-design-system-components-tag.mjs +2 -2
- package/fesm2022/ids-group-ltd-ids-design-system-components-tag.mjs.map +1 -1
- package/fesm2022/ids-group-ltd-ids-design-system-components-textarea.mjs +2 -2
- package/fesm2022/ids-group-ltd-ids-design-system-components-textarea.mjs.map +1 -1
- package/fesm2022/ids-group-ltd-ids-design-system-components-time-picker.mjs +12 -9
- package/fesm2022/ids-group-ltd-ids-design-system-components-time-picker.mjs.map +1 -1
- package/fesm2022/ids-group-ltd-ids-design-system-components-timeline.mjs +2 -2
- package/fesm2022/ids-group-ltd-ids-design-system-components-timeline.mjs.map +1 -1
- package/fesm2022/ids-group-ltd-ids-design-system-components-toast.mjs +9 -7
- package/fesm2022/ids-group-ltd-ids-design-system-components-toast.mjs.map +1 -1
- package/fesm2022/ids-group-ltd-ids-design-system-components-toggle-button.mjs +2 -2
- package/fesm2022/ids-group-ltd-ids-design-system-components-toggle-button.mjs.map +1 -1
- package/fesm2022/ids-group-ltd-ids-design-system-components-tree.mjs +2 -2
- package/fesm2022/ids-group-ltd-ids-design-system-components-tree.mjs.map +1 -1
- package/fesm2022/ids-group-ltd-ids-design-system-components-w3w.mjs +2 -2
- package/fesm2022/ids-group-ltd-ids-design-system-components-w3w.mjs.map +1 -1
- package/fesm2022/ids-group-ltd-ids-design-system-components.mjs +27 -1
- package/fesm2022/ids-group-ltd-ids-design-system-components.mjs.map +1 -1
- package/fesm2022/ids-group-ltd-ids-design-system-core.mjs +12 -4
- package/fesm2022/ids-group-ltd-ids-design-system-core.mjs.map +1 -1
- package/fesm2022/ids-group-ltd-ids-design-system-icons.mjs +2 -38
- package/fesm2022/ids-group-ltd-ids-design-system-icons.mjs.map +1 -1
- package/fesm2022/ids-group-ltd-ids-design-system.mjs +3 -0
- package/fesm2022/ids-group-ltd-ids-design-system.mjs.map +1 -1
- package/migrations/0.10.0.json +1 -1
- package/migrations/0.10.1.json +1 -1
- package/migrations/0.10.2.json +1 -30
- package/migrations/0.11.1.json +0 -23
- package/migrations/0.11.3.json +1 -1
- package/migrations/0.11.4.json +27 -7
- package/migrations/0.12.0.json +30 -2
- package/migrations/0.12.1.json +341 -0
- package/migrations/0.12.2.json +291 -0
- package/migrations/0.5.0.json +0 -54
- package/migrations/0.5.1.json +3 -1
- package/migrations/0.7.0.json +0 -11
- package/migrations/0.9.0.json +22 -3
- package/migrations/0.9.1.json +1 -1
- package/package.json +25 -1
- package/styles/_check-box.scss +91 -0
- package/styles/_check-mark.scss +59 -0
- package/styles/_clear-button.scss +28 -0
- package/styles/_dropdown-overlay.scss +12 -2
- package/styles/_field-group-segment.scss +4 -1
- package/styles/_focus.scss +103 -50
- package/styles/_link.scss +4 -2
- package/styles/_table-controls.scss +66 -0
- package/styles/_tokens.scss +20 -0
- package/styles/_typography.scss +6 -0
- package/themes/_semantic.scss +7 -8
- package/types/ids-group-ltd-ids-design-system-components-auth-layout.d.ts +2 -2
- package/types/ids-group-ltd-ids-design-system-components-menu.d.ts +3 -0
- package/types/ids-group-ltd-ids-design-system-components-radio-group.d.ts +8 -4
- package/types/ids-group-ltd-ids-design-system-components-sidenav.d.ts +9 -2
- package/types/ids-group-ltd-ids-design-system-components-split-button.d.ts +3 -2
- package/types/ids-group-ltd-ids-design-system-components-table-columns.d.ts +43 -0
- package/types/ids-group-ltd-ids-design-system-components-table-export.d.ts +48 -0
- package/types/ids-group-ltd-ids-design-system-components-table-resize.d.ts +79 -0
- package/types/ids-group-ltd-ids-design-system-components-table.d.ts +196 -155
- package/types/ids-group-ltd-ids-design-system-components.d.ts +26 -1
- package/types/ids-group-ltd-ids-design-system-core.d.ts +17 -4
- package/types/ids-group-ltd-ids-design-system.d.ts +3 -0
package/CHANGELOG.md
CHANGED
|
@@ -8,6 +8,542 @@ While the package is on `0.x`, minor releases may contain breaking changes.
|
|
|
8
8
|
|
|
9
9
|
## Unreleased
|
|
10
10
|
|
|
11
|
+
## 0.12.2 — 2026-09-09
|
|
12
|
+
|
|
13
|
+
### Breaking
|
|
14
|
+
|
|
15
|
+
- **`--ds-table-hscroll-bottom` is `--ds-table-sticky-scrollbar-offset`.** The knob now carries the
|
|
16
|
+
name of the feature it belongs to, beside `stickyScrollbar` itself and the new
|
|
17
|
+
`[stickyScrollbarOffset]` input; the old spelling named neither the feature nor the edge it moves.
|
|
18
|
+
It is inert under the old name, and a stylesheet that still sets it stops offsetting the bar with
|
|
19
|
+
nothing said. Rename the declaration and the value carries over unchanged — except where the value
|
|
20
|
+
was a negative offset equal to your scroll container's bottom padding, which the table measures
|
|
21
|
+
and cancels itself now, so that one is deleted rather than renamed
|
|
22
|
+
(delete list: table-hscroll-bottom-workaround).
|
|
23
|
+
|
|
24
|
+
### Added
|
|
25
|
+
|
|
26
|
+
- **`ds-sidenav-group` takes a `routerLink`, so a group can be a destination as well as a
|
|
27
|
+
container.** Unset — the default, and what every existing group does — the header only expands,
|
|
28
|
+
unchanged. Set it and the header becomes a link that navigates, and the caret splits off into a
|
|
29
|
+
button of its own, because one control cannot both go somewhere and stay put to open something.
|
|
30
|
+
The link takes the whole header's look, so the row still reads as one control, and it carries the
|
|
31
|
+
active state when its route is the current one.
|
|
32
|
+
|
|
33
|
+
```html
|
|
34
|
+
<ds-sidenav-group label="Reports" icon="chart" expandable routerLink="/reports">
|
|
35
|
+
<ds-sidenav-item label="Daily" routerLink="/reports/daily" />
|
|
36
|
+
</ds-sidenav-group>
|
|
37
|
+
```
|
|
38
|
+
|
|
39
|
+
It takes the same shapes a router link takes anywhere, a string or a command array. **It does
|
|
40
|
+
nothing without `expandable`** — a group that cannot open has no caret to split off, so the header
|
|
41
|
+
stays a plain label and the link is ignored with nothing said. On a group that does opt in, the
|
|
42
|
+
header element changes from a `button` to an `a` — the active state above is a contextual
|
|
43
|
+
`.active` class it carries — and gains a `.group-header-row` wrapper beside a
|
|
44
|
+
`.group-caret-button`, with
|
|
45
|
+
`.group-caret` now sitting inside that button rather than directly in the header; a stylesheet of
|
|
46
|
+
yours reaching `.group-header` by class still lands, one that qualifies it with `button` does
|
|
47
|
+
not.
|
|
48
|
+
|
|
49
|
+
- **`ds-table` takes `[stickyScrollbarOffset]`, and `DS_CONFIG.table.stickyScrollbarOffset` sets it
|
|
50
|
+
for every table.** Where the sticky horizontal scrollbar comes to rest, as any CSS length.
|
|
51
|
+
Unset — the default — each table measures its own scroll container's bottom padding and cancels
|
|
52
|
+
it, which is what puts the bar on the edge the reader sees; set this for a scrollport whose
|
|
53
|
+
reachable edge is somewhere else, and set it in the config when that is true of a whole app rather
|
|
54
|
+
than of one table. `--ds-table-sticky-scrollbar-offset` still out-ranks both, for a rule that has
|
|
55
|
+
to reach one table from a stylesheet.
|
|
56
|
+
|
|
57
|
+
```html
|
|
58
|
+
<ds-table
|
|
59
|
+
[stickyScrollbarOffset]="'-3rem'"
|
|
60
|
+
[stickyScrollbar]="true"
|
|
61
|
+
[columns]="cols"
|
|
62
|
+
[data]="rows" />
|
|
63
|
+
```
|
|
64
|
+
|
|
65
|
+
### Changed
|
|
66
|
+
|
|
67
|
+
- **An expanded `ds-table` row opens with a reveal instead of appearing at full height.** The
|
|
68
|
+
panel's cell animates its `grid-template-rows` from `0fr` to `1fr`, and a new
|
|
69
|
+
`.expand-panel-inner` wrapper between the cell and your projected expand template clips the
|
|
70
|
+
overflow so the content wipes into place rather than snapping open. The reveal runs over
|
|
71
|
+
`--duration-base` at `--ease-standard`; set those to retune its speed and curve. Under
|
|
72
|
+
`prefers-reduced-motion: reduce` the panel appears fully open with no reveal. Because that
|
|
73
|
+
wrapper now sits between the `<td>` and the projected template, a rule of yours that reached the
|
|
74
|
+
template as a direct child of the cell no longer matches — reach it through `.expand-panel-inner`,
|
|
75
|
+
or drop the child combinator.
|
|
76
|
+
|
|
77
|
+
- **The skeleton shimmer reads as a wave now, not a wash.** It travels diagonally, down and to the
|
|
78
|
+
right at 45°, so it arrives at the top of one placeholder and the bottom of another instead of
|
|
79
|
+
sweeping every row in step. Two waves cross per period — a main one and a quieter one exactly
|
|
80
|
+
between two mains — which fills the wait a single band left without making the main wave hurry.
|
|
81
|
+
Neither has a flat core: each peaks at a point and is ramp either side, so a pass arrives and
|
|
82
|
+
leaves rather than switching. The tone is one soft step darker than the base, unchanged: a shadow
|
|
83
|
+
moving over the placeholders, not a light switched on over them.
|
|
84
|
+
It is seamless, and the reason is one number. A repeating gradient still paints into a finite
|
|
85
|
+
image which the browser tiles, and an angled gradient meets itself across a tile edge only when
|
|
86
|
+
the tile advances its phase by a whole period: at 135° a square tile of side S advances it by
|
|
87
|
+
S / √2, so the tile has to be period × √2. Left at `auto` the tile was the positioning area — the
|
|
88
|
+
viewport, under `fixed` — and every tile boundary showed as a hard line straight across the page.
|
|
89
|
+
Measured against tiles of period / √2, of period, and one oversized no-repeat image: all three
|
|
90
|
+
seam, this one does not.
|
|
91
|
+
|
|
92
|
+
Four hooks, all with defaults — `--ds-skeleton-wave-period` (56rem),
|
|
93
|
+
`--ds-skeleton-wave-duration` (3400ms), `--ds-skeleton-wave-angle` (135deg) and
|
|
94
|
+
`--ds-skeleton-wave-echo-color`. **`--ds-skeleton-wave-duration` replaces the shimmer's old
|
|
95
|
+
dependency on `--duration-loop-slow`**, so a brand that retuned that global no longer reaches the
|
|
96
|
+
skeleton — set the skeleton hook instead. The loop is 3400ms where it was 1400ms, and the pass no
|
|
97
|
+
longer rests between crossings. **`--ds-skeleton-wave-angle` retunes the gradient's direction
|
|
98
|
+
only**: the tile size and the loop's travel are fixed to the 45° diagonal, so an angle far from
|
|
99
|
+
the default tiles visibly. Change it for a small adjustment, not for a new axis.
|
|
100
|
+
|
|
101
|
+
- **Two classes gained members — only matters if you SUBCLASS one.** `TableComponent` gained
|
|
102
|
+
`showsLoadingSpace`, which decides whether a table that is still loading and has no rows yet holds
|
|
103
|
+
a body open instead of collapsing onto its header, and `publishHeadHeight`, which measures the
|
|
104
|
+
header and publishes its height for the scrim to inset against, `scrollAncestor`, which finds the
|
|
105
|
+
scrollport a sticky offset inside the table resolves against, `hasAnyColumnFilter`, which decides
|
|
106
|
+
whether the column-filter panel is rendered at all, `isFilterPanelOpen`, which tells a header
|
|
107
|
+
button whether the panel showing belongs to it, and the new `stickyScrollbarOffset` input with its
|
|
108
|
+
`stickyScrollbarOffsetResolved`. `SidenavGroupComponent` gained the
|
|
109
|
+
new `routerLink` input and `headerNavigates`, the computed that decides whether the header splits
|
|
110
|
+
into a link and a caret. Only `routerLink` is public API and that is no protection for the rest:
|
|
111
|
+
`private` and `protected` collide with TS2415 exactly as a public name does, so a member of yours
|
|
112
|
+
sharing one of those names stops the build. Nothing changes for a consumer who only uses the
|
|
113
|
+
elements — no existing input, output or token changed name or type.
|
|
114
|
+
|
|
115
|
+
- **A fullscreen `ds-modal` is a full-height panel now, so `--modal-h-fullscreen` reads as a target
|
|
116
|
+
and no longer as a cap.** The class used to set the token as a `max-height`, which let a short
|
|
117
|
+
body shrink the panel; it sets the height itself now, still clipped by the modal's own 90dvh
|
|
118
|
+
ceiling. A modal you sized through that token gets `min(your value, 90dvh)` — set it below the
|
|
119
|
+
ceiling if you want the panel shorter, and expect the extra room to go to the scrolling body with
|
|
120
|
+
the footer at the bottom of the screen.
|
|
121
|
+
|
|
122
|
+
- **`ds-date-picker` focuses like a field, not like a button.** `--ds-date-picker-focus-shadow`
|
|
123
|
+
falls back to `--ds-field-focus-shadow` instead of `--ds-control-focus-shadow`, so the trigger
|
|
124
|
+
draws the single soft field halo the inputs draw and follows the `data-focus` switch, which it
|
|
125
|
+
used to ignore. A brand that retunes the control family no longer reaches the date picker — retune
|
|
126
|
+
the field family, or set `--ds-date-picker-focus-shadow` outright. `ds-time-picker` still resolves
|
|
127
|
+
the control family, so the two now focus differently.
|
|
128
|
+
|
|
129
|
+
- **Five classes that carried no styling are gone from the DOM — only matters if YOUR stylesheet
|
|
130
|
+
reached one.** `ds-autocomplete`'s trigger no longer takes `.open` or `.error`,
|
|
131
|
+
`ds-multi-select`'s trigger no longer takes `.readonly`, and `ds-tabs`' count badge is
|
|
132
|
+
`class="badge"` where it was `class="badge neutral count"`. This library never styled any of the
|
|
133
|
+
five, so none of its own rules move; a rule of yours keyed off one stops matching, silently. Every
|
|
134
|
+
state they reported is still on the element:
|
|
135
|
+
`.autocomplete-trigger:has(input[aria-expanded="true"])` for open, the host's
|
|
136
|
+
`[data-field-state="error"]` for error, `.field-trigger[aria-readonly="true"]` for read-only, and
|
|
137
|
+
`.badge` on its own for the badge.
|
|
138
|
+
|
|
139
|
+
- **The `ds-progress` warning bar is a yellow.** `--ds-progress-bar-color-warning` falls back to
|
|
140
|
+
`--yellow-500` rather than to `--warning-hover`, which mixed the warning hue toward black in the
|
|
141
|
+
light theme and toward white in the dark one — one bar read olive, the other pale. Both themes
|
|
142
|
+
paint the same yellow now. A brand that recoloured the bar through `--warning-hover` no longer
|
|
143
|
+
reaches it; set `--ds-progress-bar-color-warning`. `--warning-hover` itself is unchanged and still
|
|
144
|
+
used elsewhere.
|
|
145
|
+
|
|
146
|
+
### Fixed
|
|
147
|
+
|
|
148
|
+
- **A `ds-table` loading in `overlay` mode with no rows keeps a body.** The tbody was empty, so the
|
|
149
|
+
table collapsed onto its header and the spinner floated over nothing. It now holds one
|
|
150
|
+
`aria-hidden` spacer row's worth of height, built from the same padding and line height a real row
|
|
151
|
+
uses, so it tracks density. Only `[loading]="'overlay'"` with zero rows is affected — `skeleton`
|
|
152
|
+
draws its own rows and `[loading]="true"` resolves to `skeleton` when there is nothing to show.
|
|
153
|
+
A test that asserts an empty tbody during an overlay load now sees that one row.
|
|
154
|
+
|
|
155
|
+
- **The `ds-table` loading scrim starts below the header from the first frame.** The header height
|
|
156
|
+
was read once per load and before layout, so the first frame fell back to a 40px guess under a
|
|
157
|
+
taller header and the blur began mid-header. It is measured after render and re-measured whenever
|
|
158
|
+
the header resizes, so a header that wraps or a density change moves the scrim with it.
|
|
159
|
+
`--ds-table-head-h` still overrides the measurement.
|
|
160
|
+
|
|
161
|
+
- **The `ds-table` selection checkbox stops twitching when the mark changes.** The box sat on the
|
|
162
|
+
text baseline, so the header row's height moved by a fraction of a pixel as the select-all box
|
|
163
|
+
swapped between its tick and its indeterminate bar. It is centred against the line box now. This
|
|
164
|
+
reaches the table's header and row checkboxes and the `dsTableColumns` panel's per-column
|
|
165
|
+
checkboxes; `ds-checkbox` itself lays the box out as a flex item and never showed it. A
|
|
166
|
+
`::ng-deep` nudge you added to compensate for the old sit is now that much out.
|
|
167
|
+
|
|
168
|
+
- **`ds-date-picker`'s calendar glyph matches the value it sits beside.** It rendered two pixels
|
|
169
|
+
taller than the digits' cap height and overhung them top and bottom.
|
|
170
|
+
|
|
171
|
+
- **Clicking above or below the digits in `ds-date-picker` places the caret instead of opening the
|
|
172
|
+
calendar.** The text input only covered the value's own line box, so the band either side of it
|
|
173
|
+
fell through to the trigger. It spans the field's height now.
|
|
174
|
+
|
|
175
|
+
- **`ds-dropzone` shows the hand cursor once files are listed.** The zone kept the arrow, which read
|
|
176
|
+
as "this is finished, there is nothing to click", while the whole zone had stayed clickable the
|
|
177
|
+
entire time. Nothing about what a click does has changed.
|
|
178
|
+
|
|
179
|
+
- **`dsTableColumns` draws a styled panel and a styled header button.** The panel's checkboxes, drag
|
|
180
|
+
handles, move buttons and `Reset to default` link came out as the browser's own widgets and the
|
|
181
|
+
button that opens the panel as a bordered grey rectangle, because the rules for `.col-picker`,
|
|
182
|
+
`.col-picker-row`, `.col-picker-option`, `.col-drag`, `.col-move`, `.col-move-btn`, `.col-reset`
|
|
183
|
+
and `.col-picker-btn` were scoped to `ds-table` while the elements they name sit in views of their
|
|
184
|
+
own. Each of those classes is styled from the view that renders it now. Markup, class names and
|
|
185
|
+
API are unchanged, but a stylesheet of yours that reached one of them by a bare class name shared
|
|
186
|
+
the element with nothing and now competes with a scoped rule — qualify your selector, or reach for
|
|
187
|
+
the token the class reads.
|
|
188
|
+
|
|
189
|
+
- **A `ds-table` sticky horizontal scrollbar rests on the edge the reader can see.** Inside a scroll
|
|
190
|
+
container with bottom padding the bar settled one padding-bottom short of that edge and drew over
|
|
191
|
+
the rows beneath it, because a sticky `bottom` resolves against the scrollport's content box. The
|
|
192
|
+
table measures that padding off its scroll ancestor, cancels it, and re-measures when the
|
|
193
|
+
container resizes, so a padding that moves with a media query moves the bar with it.
|
|
194
|
+
`--ds-table-sticky-scrollbar-offset` still overrides the measurement outright — keep it for a
|
|
195
|
+
scrollport whose reachable edge is not its padding edge, and drop a negative value written to
|
|
196
|
+
cancel your own container's padding, which now offsets the bar a second time
|
|
197
|
+
(delete list: table-hscroll-bottom-workaround).
|
|
198
|
+
|
|
199
|
+
- **`clearable` on `ds-autocomplete` and `ds-multi-select` draws the clear button the rest of the
|
|
200
|
+
field family draws.** Both rendered the `.clear-btn` markup with no rule able to reach it, so the
|
|
201
|
+
× came out as the browser's default button — a grey bordered rectangle with a square corner and a
|
|
202
|
+
default cursor — next to the properly drawn chips it sits beside. `ds-select`'s rule is shared by
|
|
203
|
+
all three now: chromeless, `--icon-default`, `--ds-radius-inner`, `--space-0-5` of padding and the
|
|
204
|
+
press feedback, over a `--surface-secondary` hover. `ds-select` itself is unchanged, and `ds-input`
|
|
205
|
+
keeps its own filled-disc clear button, which is a different control on purpose
|
|
206
|
+
(delete list: picker-clear-button-workaround).
|
|
207
|
+
|
|
208
|
+
- **A `ds-table` column filter opens on the first click.** The first click on a filter button only
|
|
209
|
+
built the panel and the second one opened it, because the handler raised the condition that
|
|
210
|
+
renders the panel and then read the panel back in the same synchronous line, before change
|
|
211
|
+
detection had created it. The panel's existence now follows the columns' own filter configuration,
|
|
212
|
+
the way the row-actions menu and the clipped-cell text popover already did, so it is there before
|
|
213
|
+
the first click arrives. This reaches `filterMode` set to anything but `'none'`, both the built-in
|
|
214
|
+
`filter: 'set'` panel and a projected `dsHeaderFilter`, and the keyboard as much as the pointer —
|
|
215
|
+
one Enter on the button opens it. A table with no filterable column renders no panel at all.
|
|
216
|
+
|
|
217
|
+
- **A `ds-table` column filter button says whether its panel is open.** It announced
|
|
218
|
+
`aria-haspopup="dialog"` and never `aria-expanded`, so a screen reader was told a dialog was
|
|
219
|
+
available but never that it had appeared. The attribute is on every filter button now and reads
|
|
220
|
+
`true` only on the column whose panel is showing.
|
|
221
|
+
|
|
222
|
+
- **A `ds-table` bulk-action bar rests `--bulk-bar-offset` above the edge the reader can see.**
|
|
223
|
+
Inside a scroll container with bottom padding it floated that offset PLUS the padding above the
|
|
224
|
+
edge, because a sticky `bottom` resolves against the scrollport's content box — the same reason
|
|
225
|
+
the sticky horizontal scrollbar settled short. The table measures its scroll container's bottom
|
|
226
|
+
padding once and both subtract it, so the gap is the offset you set whatever the container's
|
|
227
|
+
padding is. Only a table with row selection inside a padded scroll container moves; the token
|
|
228
|
+
itself is unchanged.
|
|
229
|
+
|
|
230
|
+
- **A panel re-opened straight after being dismissed can be closed again.** Dismissing an overlay
|
|
231
|
+
disposes it only after its exit animation, so re-opening within that window let the OLD panel's
|
|
232
|
+
disposal clear the state belonging to the NEW one: the component held no reference to the panel on
|
|
233
|
+
screen, `close()` therefore did nothing, and neither Escape nor a click outside would dismiss it —
|
|
234
|
+
while `aria-expanded` reported it collapsed. Reachable by dismissing and re-opening quickly, and
|
|
235
|
+
in `ds-table` by moving from one column filter to another. Measured in `ds-date-picker`,
|
|
236
|
+
`ds-color-picker`, `ds-time-picker` and `ds-popover` — and so in everything `ds-popover` carries:
|
|
237
|
+
`ds-table`'s column filter, row-actions menu and clipped-cell text, `ds-split-button`,
|
|
238
|
+
`ds-filter-bar`'s overflow panel and `ds-sidenav-footer`'s search. `ds-select`,
|
|
239
|
+
`ds-autocomplete` and `ds-multi-select` were already immune and are unchanged in behaviour.
|
|
240
|
+
|
|
241
|
+
### What you can now DELETE
|
|
242
|
+
|
|
243
|
+
| your workaround | why it is unnecessary | replace with |
|
|
244
|
+
| --- | --- | --- |
|
|
245
|
+
| `ds-table .check` — a margin or `transform` nudging the selection box off the text baseline | the box is centred against the line box now, so the nudge is an offset of its own | nothing |
|
|
246
|
+
| `--ds-table-hscroll-bottom: -` — a negative offset equal to your scroll container's bottom padding | the table measures that padding and cancels it itself, so the value offsets the sticky scrollbar a second time — and the token it sits on is renamed, so this one is deleted rather than carried over | nothing |
|
|
247
|
+
| `ds-autocomplete .clear-btn` (or the `ds-multi-select` one) — your own rule giving the clear × a border, background, radius or size | both draw ds-select's clear button themselves now, so your rule fights it | nothing |
|
|
248
|
+
|
|
249
|
+
## 0.12.1 — 2026-09-05
|
|
250
|
+
|
|
251
|
+
### Breaking
|
|
252
|
+
|
|
253
|
+
- **`ds-table`'s data-grid features are directives now, so a table that does not use them stops
|
|
254
|
+
carrying them.** Reordering, the column picker and resizing left the component; a table with none
|
|
255
|
+
of them costs **35 647 → 16 410 B gzip, −54%**, and `@angular/cdk/drag-drop` goes with the drag
|
|
256
|
+
handle. Each feature is one import and one attribute away, and two of the moved inputs changed
|
|
257
|
+
shape on the way:
|
|
258
|
+
|
|
259
|
+
```html
|
|
260
|
+
<!-- was -->
|
|
261
|
+
<ds-table [reorderableColumns]="true" [resizableColumns]="true" [exportButton]="true" />
|
|
262
|
+
|
|
263
|
+
<!-- now: add the directive to the component's imports, and its attribute here -->
|
|
264
|
+
<ds-table dsTableColumns reorderableColumns dsTableResize dsTableExport />
|
|
265
|
+
```
|
|
266
|
+
|
|
267
|
+
Every switch above reads as a boolean attribute, so its bare presence turns it on and
|
|
268
|
+
`[reorderableColumns]="true"` is the same thing written longer. Only `[dsTableExport]="false"`
|
|
269
|
+
earns a value, and it turns the built-in button off while keeping the feature.
|
|
270
|
+
|
|
271
|
+
| feature | directive | class, and where it lives | its inputs |
|
|
272
|
+
| --- | --- | --- | --- |
|
|
273
|
+
| reorder + the column picker | `dsTableColumns` | `DsTableColumns`, `…/table-columns` | `reorderableColumns`, `[(hiddenKeys)]`, `[(columnOrder)]` |
|
|
274
|
+
| column resizing | `dsTableResize` | `DsTableResize`, `…/table-resize` | none — the bare attribute is the whole switch |
|
|
275
|
+
| CSV export | `dsTableExport` | `DsTableExport`, `…/table-export` | `exportFilename`, `exportFetcher`, `(exportFailed)` |
|
|
276
|
+
|
|
277
|
+
**`exportButton` is gone as an input** — the directive's own presence renders the button, and
|
|
278
|
+
`[dsTableExport]="false"` keeps the feature while hiding the built-in control. `runExport()`,
|
|
279
|
+
`exporting()` and `exportCsv()` stay on the table, because their documentation promises a button
|
|
280
|
+
elsewhere on the page can drive them; they now delegate to the directive, and calling one with no
|
|
281
|
+
directive present logs a dev-mode warning rather than doing nothing. **Binding a moved input
|
|
282
|
+
without adding its directive does not compile**: `reorderableColumns`, `[(hiddenKeys)]`,
|
|
283
|
+
`[(columnOrder)]`, `resizableColumns` and `[(columnWidths)]` are gone from `ds-table` with no
|
|
284
|
+
passthrough, so the template fails the build rather than quietly doing nothing. Two of them do not
|
|
285
|
+
come back as bindings at all — `dsTableResize` declares no inputs and no outputs, so
|
|
286
|
+
`[(columnWidths)]`, `[columnWidths]` and `(columnWidthsChange)` compile nowhere: resizing can no
|
|
287
|
+
longer be toggled by an expression, and the widths are reachable only through a
|
|
288
|
+
`viewChild(DsTableResize)`. `dsTableColumns` keeps the other three under their old names and
|
|
289
|
+
defaults, and `(hiddenKeysChange)` and `(columnOrderChange)` still fire on the same element, so
|
|
290
|
+
those bindings survive once the attribute is there. The handle itself is unchanged: the same
|
|
291
|
+
keyboard steps and minimum width, the same markup, the same `col-*` classes, and no custom
|
|
292
|
+
property added or removed.
|
|
293
|
+
|
|
294
|
+
`persistLayout` and `storageKey` stay on the table, under the same storage key and the same
|
|
295
|
+
`{ order, widths, hidden }` shape, so a layout saved by an earlier version still restores — a
|
|
296
|
+
part whose directive is absent is simply not applied. Saving works the other way round now: only
|
|
297
|
+
the slices the present directives own are written, where every save used to carry all three. A
|
|
298
|
+
table that takes `dsTableResize` and not `dsTableColumns` rewrites an existing entry with widths
|
|
299
|
+
alone on its first save and drops the reader's stored order and hidden columns, and `persistLayout`
|
|
300
|
+
with a `storageKey` and neither directive writes nothing at all. Keep both directives on a table
|
|
301
|
+
whose layout you persist.
|
|
302
|
+
|
|
303
|
+
- **A column declared `hidden: true` renders unless `dsTableColumns` is on the table.** Column
|
|
304
|
+
visibility is the directive's stage now — `ds-table` reads neither `hidden` nor `hideable` without
|
|
305
|
+
it. `TableColumn` is unchanged, both fields still declared and still typed, so a table that sets
|
|
306
|
+
them compiles exactly as before and shows every column. Two structural consequences ride along. A
|
|
307
|
+
table with hideable columns and no `rowActions` used to grow a trailing utility column to carry the
|
|
308
|
+
picker button; without the directive that header cell and its body cells are gone, so a rule that
|
|
309
|
+
counts columns lands one off. And with the directive the button renders unconditionally, where it
|
|
310
|
+
used to need at least one `hideable` column or `reorderableColumns` — a table that takes
|
|
311
|
+
`dsTableColumns` for reordering alone gains the utility column plus a "Choose columns" panel whose
|
|
312
|
+
checkboxes are all disabled. Add the directive wherever a column is declared `hidden` or
|
|
313
|
+
`hideable`.
|
|
314
|
+
|
|
315
|
+
- **A focused `ds-checkbox`, `ds-radio` or `ds-switch` rings the whole row, label included, instead
|
|
316
|
+
of the glyph.** Ringing the glyph put a brand ring concentric with the brand ring the CHECKED state
|
|
317
|
+
already draws — three bands through two gaps, a target rather than two states a keyboard user has
|
|
318
|
+
to tell apart while moving through a group. The row is also what the pointer already hits, since
|
|
319
|
+
the label carries the hit area. A control with no label has no row to speak of, so there the ring
|
|
320
|
+
keeps its distance instead (`--space-1-5` rather than the usual 2px offset). It is keyboard-only:
|
|
321
|
+
the row matches `:has(:focus-visible)`, so clicking a checkbox with the pointer leaves no ring
|
|
322
|
+
behind. A `ds-table` selection checkbox has no row to ring, so it rings its own box.
|
|
323
|
+
|
|
324
|
+
- **Every hand-written `outline: none` in the library became `focus.own-indicator`.** The declaration
|
|
325
|
+
is the same everywhere except in forced colours, where it is now skipped. Windows High Contrast
|
|
326
|
+
drops `box-shadow`, so a field whose shell rings with the halo had nothing left once its inner
|
|
327
|
+
control was silenced — the one mode where an indicator is mandatory was the one mode without one.
|
|
328
|
+
If you silence a DS control in your own stylesheet, wrap it the same way:
|
|
329
|
+
`@media not (forced-colors: active) { outline: none; }`.
|
|
330
|
+
|
|
331
|
+
- **Every focus ring on a control is an `outline` now, not a box-shadow, and its gap is genuinely
|
|
332
|
+
see-through.** A shadow cannot leave a hole: the gap had to be painted with a guessed colour, and
|
|
333
|
+
that guess was a coloured rim everywhere it was wrong — a control standing on a tinted band, a
|
|
334
|
+
photo or a card of another shade got a surface-coloured band around it rather than its own ground.
|
|
335
|
+
`outline-offset` does not paint its gap at all, so the ring now floats over whatever the control
|
|
336
|
+
actually sits on. Two things follow. A negative offset draws the ring INSIDE the element, which is
|
|
337
|
+
how a row inside a clipping panel keeps an indicator that `overflow: hidden` used to eat — `ds-menu`
|
|
338
|
+
and the dropdown panels do this. And the ring no longer competes with `box-shadow`: a focused card
|
|
339
|
+
keeps its elevation, where before the two signals fought for one property. A state carried partly
|
|
340
|
+
by a shadow — the selected segment, the active pill, the sidenav item's rail — still drops that
|
|
341
|
+
shadow while focused, deliberately, because its fill and label colour go on saying which one it is.
|
|
342
|
+
— Restyle the ring through the new `--focus-ring-width` (2px, the WCAG 2.4.13 floor for a
|
|
343
|
+
perimeter indicator), plus `--focus-ring-color` and `--focus-ring-offset`, which are unchanged. Components author it through one mixin,
|
|
344
|
+
`focus.ring($offset)`, so there is a single place to change it.
|
|
345
|
+
— If you set `--focus-ring-inner` to a colour to get a visible ring back, remove it: the token no
|
|
346
|
+
longer reaches a control's ring. It still composes the field halo that `data-focus="ring"` opts into.
|
|
347
|
+
— Watch for an `outline: none` of your own on a DS control. It used to remove nothing, because the
|
|
348
|
+
ring was a shadow; it now removes the indicator outright, and nothing warns.
|
|
349
|
+
|
|
350
|
+
- **Thirteen `--ds-<component>-focus-shadow` tokens are gone**, on button, icon-button, card,
|
|
351
|
+
checkbox, radio, switch, tabs, toast, breadcrumbs, pagination, sidenav-item, sidenav-group and
|
|
352
|
+
menu-item. Each resolved to `--ds-control-focus-shadow`, which controls no longer read. Set
|
|
353
|
+
`--focus-ring-color`, `--focus-ring-width` or `--focus-ring-offset` on the component's own scope
|
|
354
|
+
instead. Field tokens — `--ds-input-focus-shadow` and its siblings — are unchanged, because fields
|
|
355
|
+
keep the soft halo. An override of a removed token still parses and cascades and changes nothing,
|
|
356
|
+
so this fails silently.
|
|
357
|
+
|
|
358
|
+
- **`data-focus="field"` and `data-focus="outline"` are removed** from the one-place focus switch.
|
|
359
|
+
Both described swapping one box-shadow for another, which no longer describes anything a control
|
|
360
|
+
does. `ring`, `edge` and `inset` keep their meaning, and `edge` is the tight-ring answer that
|
|
361
|
+
`field` was reached for. An unknown value matches nothing and is ignored in silence.
|
|
362
|
+
|
|
363
|
+
### Added
|
|
364
|
+
|
|
365
|
+
- **The check mark overshoots as it lands, and its motion is now four tokens.** A tick that scaled
|
|
366
|
+
in on a flat ease read as a state flag; it now arrives on `--ease-spring` over 180ms and leaves on
|
|
367
|
+
`--ease-accelerate` over 120ms, so it settles rather than snaps. The timing is a motion ROLE —
|
|
368
|
+
`--ds-motion-check-enter-duration`, `--ds-motion-check-enter-easing`, `--ds-motion-check-exit-duration`,
|
|
369
|
+
`--ds-motion-check-exit-easing` — with per-scope hooks `--ds-check-mark-*` beneath it, so a dense
|
|
370
|
+
option list can stay calm while forms overshoot. To put the previous motion back, set the four
|
|
371
|
+
tokens to the linear timing they replaced. Both durations resolve through the `--duration-*`
|
|
372
|
+
scale, which `prefers-reduced-motion` already zeroes, so the mark goes instant on its own.
|
|
373
|
+
- **The tick and the indeterminate bar are painted as a mask over `currentcolor`, not as a hardcoded
|
|
374
|
+
white stroke.** One path serves a filled box and a bare row — white on the accent fill, the row's
|
|
375
|
+
own colour on a surface — and under `forced-colors: active` it resolves to `CanvasText`, so in
|
|
376
|
+
Windows High Contrast a checked or indeterminate mark stays distinct from the forced fill of the
|
|
377
|
+
box it sits in, where before the two came out the same colour. This is the mark in `ds-checkbox`,
|
|
378
|
+
in `ds-table`'s select-all, row and column-filter boxes, in a picker panel's option ticks, and in
|
|
379
|
+
`ds-autocomplete` and `ds-multi-select`. Nothing to change on your side: a colour override of your
|
|
380
|
+
own is unaffected, and forced-colors mode discards colour overrides either way.
|
|
381
|
+
|
|
382
|
+
- **Every option mark in a picker panel is now the SAME mark as a checkbox's,** and animates with
|
|
383
|
+
it: the selected row in `ds-select` and single-mode `ds-autocomplete`, the option boxes in
|
|
384
|
+
multi-mode `ds-autocomplete`, and every box in a `ds-multi-select` panel — option rows, group-all
|
|
385
|
+
and select-all. Each was a `ds-icon name="check"` rendered only while selected, so it had no
|
|
386
|
+
resting state to move from and popped in. The indeterminate bar animates on the same tokens now,
|
|
387
|
+
instead of appearing as a separate element. The mark is painted as a mask over `currentColor`,
|
|
388
|
+
which is what lets one path serve a filled box (white on the accent) and a bare option row
|
|
389
|
+
(accent on the surface). `--ds-option-check-color` still picks its colour.
|
|
390
|
+
|
|
391
|
+
- **A picker panel's option box is drawn at the checkbox's own border weight.** It used
|
|
392
|
+
`--border-width-strong` where `ds-checkbox` and `ds-radio` read `--check-bw`, so the same control
|
|
393
|
+
shipped at two thicknesses; the panel boxes in `ds-multi-select` and multi-mode `ds-autocomplete`
|
|
394
|
+
are 1px now, on the unchanged 20px `--check-size`.
|
|
395
|
+
- **The typing area beside an autocomplete's chips is 40px, not 80px.** `--ds-autocomplete-input-minw`
|
|
396
|
+
is a floor, so in the default `width="fill"` the input still stretches across the row and only the
|
|
397
|
+
chip case changes; under `width="content"` it is what an empty field measures. Set the hook back to
|
|
398
|
+
`80px` to keep the old footprint.
|
|
399
|
+
- **A multi-select panel's "Select all" row clips its label like the option rows do.**
|
|
400
|
+
`.select-all-label` carried no clip at all, so a narrow panel wrapped that one row to two lines
|
|
401
|
+
beside single-line options. The per-group "All of …" row is not wrapped in an element, so it is
|
|
402
|
+
not clipped and a long group name still wraps there.
|
|
403
|
+
- **`ds-radio` accepts `[deselectable]`,** which lets a checked STANDALONE radio be cleared by
|
|
404
|
+
clicking it again. Off by default and ignored inside `ds-radio-group`, where clearing the one
|
|
405
|
+
selected option would leave the group with no value through a gesture the group cannot see.
|
|
406
|
+
|
|
407
|
+
### Changed
|
|
408
|
+
|
|
409
|
+
- **A date field is as wide as its date.** The trigger sized its input with the HTML `size`
|
|
410
|
+
attribute, which counts CHARACTERS — and a mask's slashes, spaces and dash are all narrower than a
|
|
411
|
+
digit, so a range reserved roughly two digits of dead space between the value and the calendar
|
|
412
|
+
button. The painted overlay now sits in the flow and measures the field with the real glyphs.
|
|
413
|
+
- **Mono type no longer ligates operators.** JetBrains Mono draws `===` as one triple-bar glyph and
|
|
414
|
+
`!=` as a struck equals, so any prose naming an operator showed something other than the characters
|
|
415
|
+
it was discussing. `--ds-t-mono-ligatures` puts them back for a consumer who wants them.
|
|
416
|
+
- **`ds-table` selects rows with the design system's checkbox, not the browser's.** Its
|
|
417
|
+
`<input type="checkbox">` was styled nowhere at all, so the OS drew it — no DS geometry, no DS
|
|
418
|
+
colours, no mark. The box is a shared partial now, so it cannot drift from `ds-checkbox`, and it
|
|
419
|
+
answers the same hooks: `--ds-checkbox-bg-color`, `--ds-checkbox-border-color`,
|
|
420
|
+
`--ds-checkbox-selected-bg-color` and their siblings reach a table's selection column where they
|
|
421
|
+
previously did nothing. The element is still an `<input type="checkbox">`, so a selector of your
|
|
422
|
+
own aimed at it still matches — but it is now competing with the library's own rule instead of
|
|
423
|
+
styling something nothing else touched, and the box sets `appearance: none`.
|
|
424
|
+
|
|
425
|
+
- **Three classes gained members — only matters if you SUBCLASS one.** `MenuComponent` gained
|
|
426
|
+
`anyIcon`, which it computes over its content children, `RadioComponent` gained `onClick`
|
|
427
|
+
alongside the new `deselectable` input, and `TableComponent` gained `anySelected`, a computed
|
|
428
|
+
over the selection set, the anchors the table's opt-in features render into, and the seam they
|
|
429
|
+
write through. A subclass that declares any of those names stops building, whether or not the
|
|
430
|
+
member is public API.
|
|
431
|
+
|
|
432
|
+
**`TableComponent` also LOST the data-grid half**, and how you hear about it depends on how the
|
|
433
|
+
subclass was written: `columnOrder`, `hiddenKeys`, `columnWidths`, `reorderableColumns`,
|
|
434
|
+
`resizableColumns`, `exportButton` and their handlers moved to `dsTableColumns`, `dsTableResize`
|
|
435
|
+
and `dsTableExport`. A member you marked `override` fails the build, because there is no base
|
|
436
|
+
member left to override; one you declared without the modifier still compiles, overrides nothing
|
|
437
|
+
and runs never.
|
|
438
|
+
|
|
439
|
+
Three new classes come with those directives, and all three are internal: `DsTableLayout` is
|
|
440
|
+
internal, the seam a feature registers with; `TableColumnsPanelComponent` is internal, the
|
|
441
|
+
column panel; `TableColumnsTriggerComponent` is internal, its header button; and
|
|
442
|
+
`TableExportButtonComponent` is internal, the toolbar button. None is API, none appears in the
|
|
443
|
+
component reference, and each is created imperatively — they are named here only so a name
|
|
444
|
+
collision in a subclass is greppable from the first release that has them.
|
|
445
|
+
|
|
446
|
+
|
|
447
|
+
- **The focus ring eases in instead of appearing at full strength.** Only its colour moves — the
|
|
448
|
+
ring's geometry is already in place, so nothing shifts and the indicator lands where it will stay.
|
|
449
|
+
`outline-offset` is deliberately not animated: an expanding ring lags the caret on a fast Tab, and
|
|
450
|
+
the indicator is a keyboard user's only signal of where they are. It runs as an `animation` rather
|
|
451
|
+
than a transition, because `transition` is a single property and a component that declares its own
|
|
452
|
+
list would have had it replaced for as long as the element held focus — a focused button would have
|
|
453
|
+
lost its background easing. The duration is `--duration-fast`, which the library already zeroes
|
|
454
|
+
under `prefers-reduced-motion: reduce`, so a reduced-motion user sees the ring appear instantly
|
|
455
|
+
with no separate opt-out to wire up.
|
|
456
|
+
|
|
457
|
+
- **`ds-split-button` with an empty `menuItems` disables its chevron instead of opening an empty
|
|
458
|
+
menu.** The template carried no guard, so a split button configured with nothing to list still
|
|
459
|
+
opened a panel with nothing in it — a chevron is a promise that there is more, and an empty panel
|
|
460
|
+
reads as a broken control. The trigger is now disabled whenever `menuItems` is empty, and a
|
|
461
|
+
development build warns once and names `ds-button` as the control for a single action. It is
|
|
462
|
+
disabled rather than hidden, so the button keeps its geometry: a `ds-split-button` whose items
|
|
463
|
+
arrive asynchronously shows a disabled chevron until they do and enables itself when they land.
|
|
464
|
+
The panel can only ever be the `ds-menu` built from `menuItems` — nothing projects into it, and
|
|
465
|
+
anything else composes from `ds-button` and `ds-popover`. Content you project into
|
|
466
|
+
`ds-split-button` itself still lands on the main button, as before.
|
|
467
|
+
|
|
468
|
+
### Fixed
|
|
469
|
+
|
|
470
|
+
- **A `ds-table` column filter's value list draws proper checkbox boxes.** That list renders in an
|
|
471
|
+
overlay, outside the element that declares the box's `--ds-checkbox-*` resolvers — and an
|
|
472
|
+
unresolved custom property inside a `border` invalidates the whole declaration at computed-value
|
|
473
|
+
time, which left a box with no border and no size. The shared box carries each resolver's own
|
|
474
|
+
default as its fallback now, so it paints wherever it is projected, including into an overlay of
|
|
475
|
+
your own. No token name and no default changed, and there is nothing to change on your side.
|
|
476
|
+
|
|
477
|
+
- **The bulk-action bar vanished exactly when every row was selected.** It was gated on the header
|
|
478
|
+
checkbox's INDETERMINATE predicate — "some rows, but not all" — so selecting the last row hid the
|
|
479
|
+
bar with the selection still live, which is when a bulk action is most likely. It answers the
|
|
480
|
+
selection being non-empty now — the selection set itself, not the rows on screen, so the bar also
|
|
481
|
+
stays up where it used to disappear: select rows on page one and page forward and it holds, and it
|
|
482
|
+
holds when a filter hides every selected row. The selection is still live and still actionable,
|
|
483
|
+
which is the point of the bar.
|
|
484
|
+
|
|
485
|
+
- **The skeleton shimmer is one wave across the screen again, and it no longer stutters.** Every
|
|
486
|
+
`ds-skeleton` shows the slice of a single viewport-wide band passing over its own position, so a
|
|
487
|
+
page of placeholders reads as one light moving across it rather than as N loops running side by
|
|
488
|
+
side. The band is two tones of the same surface — colour washing over the placeholders, not a
|
|
489
|
+
highlight shone on them. It replaces a per-element `mask-position` slide of a 200vw mask, which on
|
|
490
|
+
a narrow skeleton parked the band off the element for most of the loop, flicked it through, and
|
|
491
|
+
restarted on a hard cut. The wave is anchored with `background-attachment: fixed`, which resolves
|
|
492
|
+
against the nearest transformed, filtered or `will-change: transform` ancestor rather than the
|
|
493
|
+
viewport — so skeletons inside an animated drawer or a transform-based layout wave locally on that
|
|
494
|
+
ancestor instead of joining the page-wide one.
|
|
495
|
+
|
|
496
|
+
- **A focused first or last `ds-accordion-item` drew a square ring inside the rounded box.** An
|
|
497
|
+
outline follows its own element's radius, and the rounded corner belongs to `ds-accordion`, not to
|
|
498
|
+
the header button. The first and last header take that corner now; the rows between stay square,
|
|
499
|
+
because there is no corner there to follow.
|
|
500
|
+
|
|
501
|
+
- **A `ds-date-picker` day outside the allowed range highlighted under the pointer as though it
|
|
502
|
+
could be picked.** The day button is only ever `aria-disabled`, never natively disabled, so its
|
|
503
|
+
hover rule still matched and offered an unselectable date. Hover now skips a disabled day; the
|
|
504
|
+
colour and cursor it already carried are unchanged.
|
|
505
|
+
|
|
506
|
+
- **Three fields answered focus with a one-pixel border tint and nothing else.** The sidenav
|
|
507
|
+
footer's search box, the table's column filter and the table's inline cell editor each turned the
|
|
508
|
+
outline off to make room for a border colour change — one pixel, under the WCAG 2.4.13 floor of a
|
|
509
|
+
2px perimeter, and on the cell editor the accent border is already its resting chrome, so focus
|
|
510
|
+
changed nothing at all. All three ring properly now and keep the tint as a second signal.
|
|
511
|
+
|
|
512
|
+
- **The search field inside a `ds-multi-select` panel showed no focus indicator at all.** It zeroed
|
|
513
|
+
its own outline and no ancestor painted one, so a keyboard user opening the panel and tabbing to
|
|
514
|
+
the filter had nothing on screen telling them where they were. The row around it rings now, drawn
|
|
515
|
+
inward because the panel clips, and the input is silenced so only one ring appears.
|
|
516
|
+
|
|
517
|
+
- **A focused `ds-icon-button` sitting flush inside a clipping box lost three sides of its ring.**
|
|
518
|
+
Seen first on the documentation sidebar's collapse toggle, then swept: a `ds-table` row sits flush
|
|
519
|
+
inside the horizontal scroller, and a collapsed `ds-sidenav` clips its own brand link. In each the
|
|
520
|
+
ring had zero room outward and read as sitting behind the control. Any box that clips can now flip
|
|
521
|
+
`--focus-ring-offset` negative on itself and everything focusable inside keeps a whole ring.
|
|
522
|
+
|
|
523
|
+
- **A `ds-menu` row without an icon started one icon-width left of its neighbours.** `.menu-item` is
|
|
524
|
+
a flex row with a gap, and an item that projected no icon collapsed its wrapper to zero width while
|
|
525
|
+
the gap stayed, so a mixed menu had two text axes and an unindented row read as a different kind of
|
|
526
|
+
thing. The menu decides it now rather than the item — an item cannot see its siblings — so one
|
|
527
|
+
item with an icon makes every item reserve the slot. A menu with no icons anywhere is unchanged and
|
|
528
|
+
stays flush to its padding. The new `--ds-menu-item-icon-size` sets the width the slot reserves.
|
|
529
|
+
|
|
530
|
+
- **`ds-split-button` answers a press on either half.** Both segments were missing the darken-plus-
|
|
531
|
+
micro-scale that every other button in the library gives a press, so the one control built from two
|
|
532
|
+
buttons was the one that felt dead under the finger. Each half now darkens through
|
|
533
|
+
`--ds-split-button-bg-color-active` (or `--ds-split-button-outline-bg-color-active` on the outline
|
|
534
|
+
variant) and scales by `--ds-split-button-press-scale`, with the same opt-in pressed halo hook the
|
|
535
|
+
button has (`--ds-split-button-pressed-shadow`, default none). The scale runs AWAY from the seam —
|
|
536
|
+
`transform-origin` is the inner edge on each half — because a centred scale pulls the pressed half's
|
|
537
|
+
inner edge inward and opens a hairline gap in the joint.
|
|
538
|
+
|
|
539
|
+
### What you can now DELETE
|
|
540
|
+
|
|
541
|
+
| your workaround | why it is unnecessary | replace with |
|
|
542
|
+
| --- | --- | --- |
|
|
543
|
+
| `::ng-deep ds-menu-item` — a left padding or margin added so icon-less rows line up with rows that have icons | the menu reserves the icon slot for every row as soon as one item carries an icon | nothing |
|
|
544
|
+
| `::ng-deep ds-split-button` — a hand-rolled `:active` darken or scale | both halves darken and scale on press, and the scale runs away from the seam so the joint stays closed | `--ds-split-button-bg-color-active`, `--ds-split-button-press-scale` |
|
|
545
|
+
| `::ng-deep .search` — a focus indicator added by hand to a picker's search box, a column filter, a cell editor or a clipped icon button | each of those draws the control ring itself now, and the ring is an `outline` drawn inside the element, so a clipping ancestor no longer eats it | nothing |
|
|
546
|
+
|
|
11
547
|
## 0.12.0 — 2026-09-04
|
|
12
548
|
|
|
13
549
|
### Added
|
|
@@ -250,6 +786,17 @@ this package ships under `migrations/`.
|
|
|
250
786
|
one of those lines has something new to say, so "Export failed" still stands until the reader
|
|
251
787
|
moves on, and everything after it is announced again.
|
|
252
788
|
|
|
789
|
+
### What you can now DELETE
|
|
790
|
+
|
|
791
|
+
None of this is required — skipping it leaves working code that is merely redundant. Each row is a
|
|
792
|
+
workaround this release made unnecessary. Generated from the `deleteList` in the release manifest
|
|
793
|
+
this package ships under `migrations/`.
|
|
794
|
+
|
|
795
|
+
| If you have | Delete it, because |
|
|
796
|
+
| --- | --- |
|
|
797
|
+
| a raised `--layer-toast` or `--layer-tooltip` | It never fixed toast-under-modal: overlay hosts live in the browser's top layer, which paints in the order hosts were shown and ignores z-index entirely. The library re-shows the toast host itself now. A layer-scale retune for your own stacking (or for browsers without popover support) is still load-bearing and stays. |
|
|
798
|
+
| a `--ds-table-head-h` override added so the loading scrim stops cutting into the header | The scrim measures the real header height now. Sizing the header itself with this token is its normal use and stays. |
|
|
799
|
+
|
|
253
800
|
## 0.11.3 — 2026-09-02
|
|
254
801
|
|
|
255
802
|
### Breaking
|
|
@@ -300,14 +847,14 @@ this package ships under `migrations/`.
|
|
|
300
847
|
overrides nothing and silently never runs. There is no public replacement to call — the countdown
|
|
301
848
|
is the region's own business now. Delete the override.
|
|
302
849
|
|
|
303
|
-
-
|
|
304
|
-
|
|
305
|
-
|
|
306
|
-
|
|
307
|
-
|
|
308
|
-
|
|
309
|
-
|
|
310
|
-
|
|
850
|
+
- **Four event bindings are silently dead, and there is no `<ds-dropdown>`.** `ds-banner` and
|
|
851
|
+
`ds-toast` emit `(closed)`, not `(dismissed)`; `ds-pagination` emits `(currentPageChange)`, not
|
|
852
|
+
`(pageChange)`; `ds-table` emits `(rowClicked)`, not `(rowClick)`. An unknown event binding
|
|
853
|
+
registers a DOM listener and never fires, so a handler on one of those four runs never, with
|
|
854
|
+
nothing in the console — check your templates for them. `<ds-dropdown>` is not a component of
|
|
855
|
+
this library; its work is `<ds-select>`, and an import naming the other one does not compile.
|
|
856
|
+
`components.md` names the shipped identifiers throughout, and carries `<ds-alert>` with its
|
|
857
|
+
`'neutral'` variant.
|
|
311
858
|
|
|
312
859
|
### Fixed
|
|
313
860
|
|
|
@@ -711,10 +1258,9 @@ this package ships under `migrations/`.
|
|
|
711
1258
|
component's own tokens. Its option row carries only `[disabled]` where `ds-select` sets
|
|
712
1259
|
`.is-disabled` beside it, which is why it still declares an `.option:disabled` of its own.
|
|
713
1260
|
|
|
714
|
-
- **
|
|
715
|
-
|
|
716
|
-
|
|
717
|
-
compile rather than passing a dead string.
|
|
1261
|
+
- **The `triggerDisplay` union is exported as `DsTriggerDisplay`** — `'full' | 'count' | 'labels'`.
|
|
1262
|
+
A variable typed against it fails to compile rather than passing a dead string, and each name says
|
|
1263
|
+
what the trigger shows, which is what matters once `labels` sits beside `count`.
|
|
718
1264
|
|
|
719
1265
|
- **Every single-line label clips through one mixin now.** Seven rules hand-rolled
|
|
720
1266
|
`overflow: hidden; text-overflow: ellipsis; white-space: nowrap` — the `ds-select` trigger text,
|
|
@@ -1028,36 +1574,6 @@ this package ships under `migrations/`.
|
|
|
1028
1574
|
container now, which drops whitespace-only text nodes outright, so the identifier renders flush and
|
|
1029
1575
|
the template stays free to be formatted for reading. No API change, and nothing to do on your side.
|
|
1030
1576
|
|
|
1031
|
-
- **Nine defects in six already-published manifests, and a repo upgraded before today may be holding
|
|
1032
|
-
the result.** The prose split above rewrote every item; this is the separate, smaller set where the
|
|
1033
|
-
DATA was wrong. It matters
|
|
1034
|
-
because these files are executed: your upgrade tooling read them, acted, and reported done.
|
|
1035
|
-
**Two changes had no item at all.** `0.9.0` never filed the six inputs whose declared type
|
|
1036
|
-
widened from `InputSignal` to
|
|
1037
|
-
`InputSignalWithTransform` (`min`/`max`/`maxLength` on `ds-input`, `min`/`max` on
|
|
1038
|
-
`ds-number-stepper`, `maxLength` on `ds-textarea`) — the TS2322 an explicit annotation hits and the
|
|
1039
|
-
TS2416 a subclass hits had no explanation anywhere. `0.10.0` never filed
|
|
1040
|
-
`ModalService.confirm({ tone: 'error' })` gaining the modal's error badge in the header.
|
|
1041
|
-
**Two instructions were wrong, so following them edited the wrong thing.** `0.7.1`’s à-la-carte
|
|
1042
|
-
`@use` lines were written as bare `styles/…` specifiers, which resolve only inside the library's own build and
|
|
1043
|
-
fail from an app; they are package-qualified now. And `0.7.1`’s modal `.title` was filed as a
|
|
1044
|
-
`class-rename` to `.heading` when no rename happened — it is a `behavior` item now, so anyone who
|
|
1045
|
-
renamed that class did so on our word and can put it back.
|
|
1046
|
-
**One `verify` certified a bug as correct.** `0.8.0` said an unset `sortMode` resolves to `server`.
|
|
1047
|
-
It resolves to `client`, so a server-paged table left unset sorts only the rows in hand — and the
|
|
1048
|
-
check passed anyway. That release’s item now says to declare `sortMode="server"` explicitly.
|
|
1049
|
-
**Three items searched too few file types.** `0.5.1`’s two `variant` remaps and `0.10.0`’s
|
|
1050
|
-
`floating` removal were marked template-only, so a `variant=` sitting in a stylesheet or a `.ts`,
|
|
1051
|
-
and the five dead floating-label tokens (`--field-h-floating` and the four `--field-floating-*`),
|
|
1052
|
-
were never looked for. Their `surface` now names style and TypeScript too.
|
|
1053
|
-
**What to do:** if your last upgrade ran before this release AND crossed one of those six versions,
|
|
1054
|
-
re-run just those items — `migrations/<version>.json` now carries them right, and nothing else in
|
|
1055
|
-
those files changed meaning. Also corrected: `0.10.2`’s two `maxVisibleChips` items now declare
|
|
1056
|
-
that they supersede `0.10.0#max-visible-chips-zero-inverted`, which an upgrade stepping through both
|
|
1057
|
-
had been applying for nothing.
|
|
1058
|
-
**Sixteen more rows** in the "What you can now DELETE" tables of
|
|
1059
|
-
0.6.1, 0.7.1, 0.8.0, 0.9.0, 0.10.0 and 0.10.3 — workarounds those releases made redundant and never
|
|
1060
|
-
listed.
|
|
1061
1577
|
|
|
1062
1578
|
### What you can now DELETE
|
|
1063
1579
|
|
|
@@ -1098,8 +1614,8 @@ workaround written against a hook that only landed in this release.
|
|
|
1098
1614
|
a single ring, and the reset stays scoped to the field element, so `clear-btn` and
|
|
1099
1615
|
`password-toggle` inside the same box keep their own rings; they are real tab stops.
|
|
1100
1616
|
- **Fourteen public override tokens are now listed in the token reference.** They were always
|
|
1101
|
-
overridable and nothing in the components changed
|
|
1102
|
-
|
|
1617
|
+
overridable and nothing in the components changed. Listed and described:
|
|
1618
|
+
`--ds-container-pad-x`, `--ds-multi-select-border-color`
|
|
1103
1619
|
(+`-focus`), `--ds-segmented-selected-bg-color` / `-label-color` / `--ds-segmented-radius`,
|
|
1104
1620
|
`--ds-time-picker-option-bg-color-selected` / `-text-color-selected` / `-bg-color-hover`,
|
|
1105
1621
|
`--ds-time-picker-trigger-bg-color` / `-border` / `-color`, `--ds-field-message-icon-offset` and
|
|
@@ -2204,8 +2720,7 @@ None of this is required — skipping it leaves working code that is merely redu
|
|
|
2204
2720
|
`--ds-*` tokens it named no longer exist** (`--ds-button-fg`, `--ds-sidenav-item-bg-hover`, the
|
|
2205
2721
|
whole `--ds-pagehdr-*` family, …), `ds-button` was described with its pre-2026-06 single `variant`
|
|
2206
2722
|
axis (`'primary' | 'secondary' | 'tertiary' | …`) instead of `color` × `variant`, and the topbar
|
|
2207
|
-
section
|
|
2208
|
-
topbar owns the gap below it and that pages must not add their own.
|
|
2723
|
+
section named a `--ds-topbar-margin-b` that this library does not define.
|
|
2209
2724
|
Every name in the body is now the shipped one, and the two paragraphs are rewritten from the
|
|
2210
2725
|
components' actual API.
|
|
2211
2726
|
|
|
@@ -2802,6 +3317,8 @@ skipping it leaves working code that is merely redundant.
|
|
|
2802
3317
|
| If you have | Delete it, because |
|
|
2803
3318
|
| --- | --- |
|
|
2804
3319
|
| `.button.button.button { … }` or rules against `.v-outline` / `.c-secondary` | `ds-button` reflects `[data-variant]` and `[data-color]` on the HOST. Use `ds-button[data-variant="outline"]` |
|
|
3320
|
+
| your own vertical-padding override on a `sm`/`lg` textarea (a `--ds-input-pad-y` retune or a local rule compensating the wrong padding) | sm/lg textareas rendered the md vertical padding; they are corrected now, so the compensation stacks on top of the fix. A deliberate global `--ds-input-pad-y` retune is a legitimate hook and stays. |
|
|
3321
|
+
| a `height`/`min-height` pinned on `ds-autocomplete`, `ds-multi-select`, `ds-color-picker`, `ds-number-stepper` or `ds-split-button` to make `--ds-field-height` "work" | Those six spelled their height as the raw `--hit-*` value, so the token did nothing for them; they read the field scale now. |
|
|
2805
3322
|
| `--radius-sm: 0` to square a checkbox | `--ds-checkbox-radius` |
|
|
2806
3323
|
| `.title.title { font-size }` inside a modal | `--ds-modal-title-font-size` |
|
|
2807
3324
|
| Pagination label type overrides — a rule on `ds-pagination` setting `--ds-pagination-label-*` | `--ds-pagination-label-*` |
|
|
@@ -3510,7 +4027,7 @@ workaround this release made unnecessary. Generated from the `deleteList` in `mi
|
|
|
3510
4027
|
### Changed
|
|
3511
4028
|
|
|
3512
4029
|
- **BREAKING: the control `size` scale is unified into one shared `DsSize` type.** The per-component
|
|
3513
|
-
size types (`InputSize`, `ButtonSize`, `SelectSize`, `
|
|
4030
|
+
size types (`InputSize`, `ButtonSize`, `SelectSize`, `CheckboxSize`, `RadioSize`,
|
|
3514
4031
|
`SwitchSize`, `SpinnerSize`, `TextareaSize`, `NumberStepperSize`, `DatePickerSize`, `TimePickerSize`,
|
|
3515
4032
|
`DrawerSize`, `IconButtonSize`, `AutocompleteSize`) are removed from the public API — import
|
|
3516
4033
|
`DsSize` instead (`type DsSize = 'sm' | 'md' | 'lg'`, exported from the package root). `AvatarSize`,
|
|
@@ -4043,17 +4560,16 @@ workaround this release made unnecessary. Generated from the `deleteList` in `mi
|
|
|
4043
4560
|
type-to-pick control; "combobox" survives only as the ARIA role — which the select-only
|
|
4044
4561
|
`ds-select` trigger also carries. Renames: selector `ds-combobox` → `ds-autocomplete`;
|
|
4045
4562
|
`ComboboxComponent` → `AutocompleteComponent`; exported types `ComboboxOption` /
|
|
4046
|
-
`
|
|
4047
|
-
`AutocompleteOptionGroup` / `AutocompleteSize` / `AutocompleteWidth`; public tokens
|
|
4563
|
+
`ComboboxSize` → `AutocompleteOption` / `AutocompleteSize`; public tokens
|
|
4048
4564
|
`--ds-combobox-focus-shadow` / `--ds-combobox-maxw` / `--ds-combobox-input-minw` →
|
|
4049
4565
|
`--ds-autocomplete-*`. Behavior unchanged.
|
|
4050
4566
|
- **`ds-dropdown` removed — use `ds-select`.** The two were near-identical select-only single
|
|
4051
4567
|
pickers (same trigger, same panel, same keyboard model); `ds-select` is the richer canonical
|
|
4052
4568
|
form field (`ControlValueAccessor`, `invalid` + `hint` via `ds-field-message`, `required` /
|
|
4053
4569
|
`optional`, per-option icons, group-level `disabled`). Migration: `<ds-dropdown>` →
|
|
4054
|
-
`<ds-select>`; `[error]` → `[invalid]`; `
|
|
4055
|
-
`[options]
|
|
4056
|
-
`
|
|
4570
|
+
`<ds-select>`; `[error]` → `[invalid]`; `DropdownOption` / `DropdownSize` → `SelectOption` /
|
|
4571
|
+
`SelectSize`. Groups go inline in `[options]`, which is what `ds-select` already took
|
|
4572
|
+
(`SelectItem = SelectOption | SelectOptionGroup`).
|
|
4057
4573
|
`readOnly` moved to `ds-select` (see Added).
|
|
4058
4574
|
- **Public token prefixes normalized to match the selector (not aliased).** Four components had
|
|
4059
4575
|
their `--ds-*` token name fragments hyphenated to align with the Angular selector; the old
|