@ids-group-ltd/ids-design-system 0.12.3 → 0.13.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 +895 -6
- package/components.md +94 -2
- package/docs/agent/INDEX.md +12 -1
- package/docs/agent/charts/chart-colour-which-palette-a-chart-takes.md +9 -0
- package/docs/agent/charts/chart-frame-the-box-a-chart-draws-around-itself.md +12 -0
- package/docs/agent/charts/ds-bar-chart.md +15 -0
- package/docs/agent/charts/ds-column-chart.md +14 -0
- package/docs/agent/charts/ds-config.md +12 -0
- package/docs/agent/charts/ds-donut-chart.md +17 -0
- package/docs/agent/charts/ds-funnel-chart.md +16 -0
- package/docs/agent/charts/ds-line-chart.md +15 -0
- package/docs/agent/forms/ds-button.md +4 -2
- package/docs/agent/forms/ds-number-stepper.md +1 -0
- package/docs/agent/navigation/ds-sidenav-item.md +1 -0
- 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-autocomplete.mjs +25 -18
- package/fesm2022/ids-group-ltd-ids-design-system-components-autocomplete.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-bar-chart.mjs +177 -0
- package/fesm2022/ids-group-ltd-ids-design-system-components-bar-chart.mjs.map +1 -0
- 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 +58 -8
- package/fesm2022/ids-group-ltd-ids-design-system-components-button.mjs.map +1 -1
- package/fesm2022/ids-group-ltd-ids-design-system-components-chart-legend.mjs +43 -0
- package/fesm2022/ids-group-ltd-ids-design-system-components-chart-legend.mjs.map +1 -0
- package/fesm2022/ids-group-ltd-ids-design-system-components-chart-tooltip.mjs +212 -0
- package/fesm2022/ids-group-ltd-ids-design-system-components-chart-tooltip.mjs.map +1 -0
- package/fesm2022/ids-group-ltd-ids-design-system-components-checkbox.mjs +1 -0
- 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 -4
- package/fesm2022/ids-group-ltd-ids-design-system-components-color-picker.mjs.map +1 -1
- package/fesm2022/ids-group-ltd-ids-design-system-components-column-chart.mjs +196 -0
- package/fesm2022/ids-group-ltd-ids-design-system-components-column-chart.mjs.map +1 -0
- package/fesm2022/ids-group-ltd-ids-design-system-components-date-picker.mjs +18 -10
- package/fesm2022/ids-group-ltd-ids-design-system-components-date-picker.mjs.map +1 -1
- package/fesm2022/ids-group-ltd-ids-design-system-components-donut-chart.mjs +311 -0
- package/fesm2022/ids-group-ltd-ids-design-system-components-donut-chart.mjs.map +1 -0
- package/fesm2022/ids-group-ltd-ids-design-system-components-drawer.mjs +2 -1
- 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-group.mjs +69 -17
- package/fesm2022/ids-group-ltd-ids-design-system-components-field-group.mjs.map +1 -1
- package/fesm2022/ids-group-ltd-ids-design-system-components-filter-bar.mjs +1 -1
- package/fesm2022/ids-group-ltd-ids-design-system-components-filter-bar.mjs.map +1 -1
- package/fesm2022/ids-group-ltd-ids-design-system-components-funnel-chart.mjs +388 -0
- package/fesm2022/ids-group-ltd-ids-design-system-components-funnel-chart.mjs.map +1 -0
- package/fesm2022/ids-group-ltd-ids-design-system-components-input.mjs +10 -14
- package/fesm2022/ids-group-ltd-ids-design-system-components-input.mjs.map +1 -1
- package/fesm2022/ids-group-ltd-ids-design-system-components-line-chart.mjs +672 -0
- package/fesm2022/ids-group-ltd-ids-design-system-components-line-chart.mjs.map +1 -0
- package/fesm2022/ids-group-ltd-ids-design-system-components-list.mjs +2 -1
- package/fesm2022/ids-group-ltd-ids-design-system-components-list.mjs.map +1 -1
- package/fesm2022/ids-group-ltd-ids-design-system-components-modal.mjs +5 -5
- 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 -4
- 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 +1 -0
- package/fesm2022/ids-group-ltd-ids-design-system-components-otp-input.mjs.map +1 -1
- package/fesm2022/ids-group-ltd-ids-design-system-components-page-header.mjs +2 -2
- package/fesm2022/ids-group-ltd-ids-design-system-components-page-header.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-radio-group.mjs +2 -10
- package/fesm2022/ids-group-ltd-ids-design-system-components-radio-group.mjs.map +1 -1
- package/fesm2022/ids-group-ltd-ids-design-system-components-segmented.mjs +1 -0
- 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 +18 -10
- package/fesm2022/ids-group-ltd-ids-design-system-components-select.mjs.map +1 -1
- package/fesm2022/ids-group-ltd-ids-design-system-components-sidenav.mjs +18 -7
- package/fesm2022/ids-group-ltd-ids-design-system-components-sidenav.mjs.map +1 -1
- package/fesm2022/ids-group-ltd-ids-design-system-components-slider.mjs +1 -0
- package/fesm2022/ids-group-ltd-ids-design-system-components-slider.mjs.map +1 -1
- package/fesm2022/ids-group-ltd-ids-design-system-components-stat.mjs +4 -3
- package/fesm2022/ids-group-ltd-ids-design-system-components-stat.mjs.map +1 -1
- package/fesm2022/ids-group-ltd-ids-design-system-components-switch.mjs +1 -0
- package/fesm2022/ids-group-ltd-ids-design-system-components-switch.mjs.map +1 -1
- package/fesm2022/ids-group-ltd-ids-design-system-components-table-export.mjs +1 -1
- package/fesm2022/ids-group-ltd-ids-design-system-components-table-export.mjs.map +1 -1
- package/fesm2022/ids-group-ltd-ids-design-system-components-table.mjs +30 -71
- package/fesm2022/ids-group-ltd-ids-design-system-components-table.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 +1 -0
- 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 +10 -4
- package/fesm2022/ids-group-ltd-ids-design-system-components-time-picker.mjs.map +1 -1
- package/fesm2022/ids-group-ltd-ids-design-system-components-toast.mjs +2 -2
- package/fesm2022/ids-group-ltd-ids-design-system-components-toast.mjs.map +1 -1
- package/fesm2022/ids-group-ltd-ids-design-system-components-tooltip.mjs +31 -9
- package/fesm2022/ids-group-ltd-ids-design-system-components-tooltip.mjs.map +1 -1
- package/fesm2022/ids-group-ltd-ids-design-system-components.mjs +448 -12
- package/fesm2022/ids-group-ltd-ids-design-system-components.mjs.map +1 -1
- package/fesm2022/ids-group-ltd-ids-design-system-core.mjs +17 -1
- package/fesm2022/ids-group-ltd-ids-design-system-core.mjs.map +1 -1
- package/fesm2022/ids-group-ltd-ids-design-system-icons.mjs +3 -0
- package/fesm2022/ids-group-ltd-ids-design-system-icons.mjs.map +1 -1
- package/fesm2022/ids-group-ltd-ids-design-system.mjs +10 -1
- package/fesm2022/ids-group-ltd-ids-design-system.mjs.map +1 -1
- package/migrations/0.13.0.json +530 -0
- package/migrations/0.13.1.json +236 -0
- package/package.json +57 -1
- package/styles/_chart-data-table.scss +95 -0
- package/styles/_chart-frame.scss +68 -0
- package/styles/_chart-interactive.scss +51 -0
- package/styles/_chart-motion.scss +88 -0
- package/styles/_dropdown-overlay.scss +9 -3
- package/styles/_focus.scss +11 -2
- package/styles/_overlay-motion.scss +10 -1
- package/styles/_tokens-charts.scss +154 -39
- package/styles/_tokens.scss +17 -4
- package/themes/dark/_theme.scss +37 -29
- package/types/ids-group-ltd-ids-design-system-components-autocomplete.d.ts +17 -10
- package/types/ids-group-ltd-ids-design-system-components-bar-chart.d.ts +119 -0
- package/types/ids-group-ltd-ids-design-system-components-button.d.ts +37 -4
- package/types/ids-group-ltd-ids-design-system-components-chart-legend.d.ts +34 -0
- package/types/ids-group-ltd-ids-design-system-components-chart-tooltip.d.ts +84 -0
- package/types/ids-group-ltd-ids-design-system-components-color-picker.d.ts +6 -1
- package/types/ids-group-ltd-ids-design-system-components-column-chart.d.ts +125 -0
- package/types/ids-group-ltd-ids-design-system-components-date-picker.d.ts +10 -2
- package/types/ids-group-ltd-ids-design-system-components-donut-chart.d.ts +127 -0
- package/types/ids-group-ltd-ids-design-system-components-field-group.d.ts +52 -11
- package/types/ids-group-ltd-ids-design-system-components-funnel-chart.d.ts +128 -0
- package/types/ids-group-ltd-ids-design-system-components-input.d.ts +5 -7
- package/types/ids-group-ltd-ids-design-system-components-line-chart.d.ts +268 -0
- package/types/ids-group-ltd-ids-design-system-components-multi-select.d.ts +6 -1
- package/types/ids-group-ltd-ids-design-system-components-select.d.ts +11 -3
- package/types/ids-group-ltd-ids-design-system-components-sidenav.d.ts +16 -4
- package/types/ids-group-ltd-ids-design-system-components-table.d.ts +13 -28
- package/types/ids-group-ltd-ids-design-system-components-time-picker.d.ts +6 -1
- package/types/ids-group-ltd-ids-design-system-components-tooltip.d.ts +11 -1
- package/types/ids-group-ltd-ids-design-system-components.d.ts +171 -5
- package/types/ids-group-ltd-ids-design-system-core.d.ts +36 -2
- package/types/ids-group-ltd-ids-design-system.d.ts +9 -2
package/CHANGELOG.md
CHANGED
|
@@ -1,12 +1,901 @@
|
|
|
1
|
-
|
|
1
|
+
## Unreleased
|
|
2
2
|
|
|
3
|
-
|
|
3
|
+
## 0.13.1 — 2026-09-14
|
|
4
4
|
|
|
5
|
-
|
|
6
|
-
`fix` → patch, `feat` → minor, breaking change (API or visual) → major.
|
|
7
|
-
While the package is on `0.x`, minor releases may contain breaking changes.
|
|
5
|
+
### Added
|
|
8
6
|
|
|
9
|
-
|
|
7
|
+
- **A picker's panel can be styled without painting every other picker's.** Each portaled pane
|
|
8
|
+
carries its own class beside the shared `ds-dropdown-panel` and `ds-overlay-pane` —
|
|
9
|
+
`ds-select-panel`, `ds-multi-select-panel`, `ds-autocomplete-panel`, `ds-color-picker-panel`,
|
|
10
|
+
`ds-date-picker-panel`, `ds-time-picker-panel` — and every one of the six also takes a
|
|
11
|
+
`panelClass` input for a class of your own:
|
|
12
|
+
|
|
13
|
+
```html
|
|
14
|
+
<ds-autocomplete panelClass="search-panel" [options]="options" />
|
|
15
|
+
```
|
|
16
|
+
|
|
17
|
+
```scss
|
|
18
|
+
.ds-autocomplete-panel .option { font-size: 15px; }
|
|
19
|
+
```
|
|
20
|
+
|
|
21
|
+
The panel is portaled to `document.body`, outside the host, so a class on the pane is the only
|
|
22
|
+
route a consumer stylesheet has to ONE instance of it. `panelClass` takes a string or an array.
|
|
23
|
+
|
|
24
|
+
Two panes gain `ds-dropdown-panel` that did not carry it: the date picker's and the time picker's.
|
|
25
|
+
Neither changes appearance, because neither renders any of the class names the skin styles — no
|
|
26
|
+
option rows, no option groups, no list. A rule of yours written against `.ds-dropdown-panel` now
|
|
27
|
+
matches them, though, and so do the panel's custom properties.
|
|
28
|
+
|
|
29
|
+
`SelectComponent`, `MultiSelectComponent`, `AutocompleteComponent`, `ColorPickerComponent`,
|
|
30
|
+
`DatePickerComponent` and `TimePickerComponent` each grow by this one input. A subclass of any of
|
|
31
|
+
the six that declares its own `panelClass` stops building until it renames the member or marks it
|
|
32
|
+
`override`.
|
|
33
|
+
|
|
34
|
+
- **The dropdown panel's border and shadow, and the option's type, read `--ds-*` hooks.**
|
|
35
|
+
`--ds-dropdown-panel-border-color` and `--ds-dropdown-panel-shadow` join the five box hooks the
|
|
36
|
+
panel already had; `--ds-option-weight`, `--ds-option-font-size`, `--ds-option-line-height` and
|
|
37
|
+
`--ds-option-font-family` fill the row's `font` shorthand, which carried four literal values. All
|
|
38
|
+
six forward per instance, like every other dropdown-panel hook: set one on a host and it reaches
|
|
39
|
+
that host's pane, with no global rule. Defaults are today's values, so an untouched theme is
|
|
40
|
+
unchanged.
|
|
41
|
+
|
|
42
|
+
- **`--ds-modal-title-font-family`.** The title had weight, size and colour hooks but read
|
|
43
|
+
`--font-heading` literally, so a display face had no route in that did not involve outspecifying
|
|
44
|
+
the component's own rule from outside its encapsulation. Defaults to `--font-heading`.
|
|
45
|
+
|
|
46
|
+
- **`DS_CONFIG` takes a `chart` section.** Four inputs now resolve through it, because each is one
|
|
47
|
+
decision per APP rather than per plot: `valueFormat` — a number reads one way in a product, and a
|
|
48
|
+
formatter passed per chart drifts as soon as there are two screens; `dataTable` — whether the
|
|
49
|
+
numbers behind a plot have a non-visual route is an accessibility policy, not a per-chart taste;
|
|
50
|
+
and `emptyText` / `errorText`, which is where localisation lands.
|
|
51
|
+
|
|
52
|
+
```ts
|
|
53
|
+
providers: [
|
|
54
|
+
provideDsConfig({
|
|
55
|
+
chart: {
|
|
56
|
+
valueFormat: (value) => value.toLocaleString('de-DE'),
|
|
57
|
+
dataTable: 'visible',
|
|
58
|
+
},
|
|
59
|
+
}),
|
|
60
|
+
];
|
|
61
|
+
```
|
|
62
|
+
|
|
63
|
+
Precedence is the input, then the config, then the built-in default, so binding one on a single
|
|
64
|
+
chart still wins. The four inputs are typed `T | null` and default to `null` — that is what lets
|
|
65
|
+
a chart tell "not set" from an explicit value — and each chart exposes the settled value as
|
|
66
|
+
`dataTableResolved`, `emptyTextResolved`, `errorTextResolved` and `valueFormatResolved`. A
|
|
67
|
+
subclass that read the raw input now reads `null` until something binds it.
|
|
68
|
+
|
|
69
|
+
`ChartDataTable` and `ChartValueFormat` are exported from the package root.
|
|
70
|
+
|
|
71
|
+
The member surface of `BarChartComponent`, `ColumnChartComponent`, `DonutChartComponent`,
|
|
72
|
+
`FunnelChartComponent` and `LineChartComponent` grows by these four readbacks and by `dimOthers`,
|
|
73
|
+
all public. `ColumnChartComponent` also gains `tooltipAnchor` and the protected `onMarkEnter`,
|
|
74
|
+
`FunnelChartComponent` the protected `hitGapUnits`, and `LineChartComponent` `tooltipAnchor`, the
|
|
75
|
+
protected `cursorBottomY` and the private `readingAnchor`. `DonutChartComponent` LOSES the
|
|
76
|
+
protected `markStagger`.
|
|
77
|
+
|
|
78
|
+
A subclass that declares any of those names collides. For a public or protected member the fix is
|
|
79
|
+
`override` or a rename; for a PRIVATE one — `readingAnchor` — only a rename works, because TS2415
|
|
80
|
+
fires on the name itself and `override` does not clear it. A subclass that called `markStagger` no
|
|
81
|
+
longer compiles.
|
|
82
|
+
|
|
83
|
+
- **The tooltip is pinned to the mark, not to the cursor, and both charts that had a say now take
|
|
84
|
+
an option.** `ds-line-chart` gains `tooltipAnchor`: `'point'`, the default, pins the panel over
|
|
85
|
+
the highest reading in the category, so it stays still while the pointer travels within one band;
|
|
86
|
+
`'pointer'` follows the cursor. `ds-column-chart` gains the same input with `'mark'` and `'cell'`:
|
|
87
|
+
the box catching the pointer is the full-height category cell, so `'cell'` opened the panel at the
|
|
88
|
+
top of the plot rather than over the column it described. `'mark'` is the default and points at
|
|
89
|
+
the column.
|
|
90
|
+
|
|
91
|
+
```html
|
|
92
|
+
<ds-line-chart tooltipAnchor="pointer" [series]="series" [categories]="months" />
|
|
93
|
+
<ds-column-chart tooltipAnchor="cell" [data]="points" />
|
|
94
|
+
```
|
|
95
|
+
|
|
96
|
+
The internal `ChartActiveMark`, which the package root does not export, takes an optional third
|
|
97
|
+
argument on `enter` to name the element inside the hit box that the panel points at. An
|
|
98
|
+
implementation that omits it still satisfies the interface.
|
|
99
|
+
|
|
100
|
+
### Changed
|
|
101
|
+
|
|
102
|
+
- **A surface no longer travels on its way in.** `ds-overlay-pane` — every picker panel, the
|
|
103
|
+
popover, the menu submenu, the tooltip, the chart tooltip — plus `ds-alert`, `ds-banner` and
|
|
104
|
+
`ds-toast` defaulted to
|
|
105
|
+
`ds-slide-in`, which offsets the panel and slides it to its place. They now default to
|
|
106
|
+
`ds-fade-in`: the same duration and easing, no travel. The travel read as the panel jumping into
|
|
107
|
+
position, and on a panel that opens UPWARD it read as jumping up from below the trigger.
|
|
108
|
+
|
|
109
|
+
`ds-drawer` and `ds-bottom-sheet` keep `ds-slide-edge-in`, because sliding in from an edge is
|
|
110
|
+
what they are, and `ds-modal` keeps `ds-scale-in`. Any surface takes its old entrance back with
|
|
111
|
+
one declaration:
|
|
112
|
+
|
|
113
|
+
```scss
|
|
114
|
+
:root { --ds-overlay-enter-keyframes: ds-slide-in; }
|
|
115
|
+
ds-toast { --ds-toast-enter-keyframes: ds-slide-in; }
|
|
116
|
+
```
|
|
117
|
+
|
|
118
|
+
- **A chart mark arrives by GROWING from its own baseline, not by scaling about its centre.** A
|
|
119
|
+
column grows up out of the category axis and a bar row grows out from the value axis; a ring arc,
|
|
120
|
+
a funnel band and a line have no baseline to grow from and fade instead. The uniform
|
|
121
|
+
`scale(0.94)` this replaces moved every mark's baseline and read as the whole chart zooming in.
|
|
122
|
+
|
|
123
|
+
- **The mark cap is 3px on `ds-bar-chart` and `ds-column-chart`,** through the new
|
|
124
|
+
`--ds-chart-mark-cap-radius`, with `--ds-bar-chart-cap-radius` and `--ds-column-chart-cap-radius`
|
|
125
|
+
over it. The bar's end was a full pill (half the track height) and the column's top was
|
|
126
|
+
`--radius-sm`; one soft value for both keeps the cap from reading as a change of shape while a
|
|
127
|
+
mark grows in.
|
|
128
|
+
|
|
129
|
+
- **A gap between two marks now belongs to the marks either side of it.** `ds-funnel-chart`'s
|
|
130
|
+
inter-stage gaps are claimed half by the band above and half by the band below, through a
|
|
131
|
+
transparent stroke — the gap looks exactly as it did and stops being dead space that answers
|
|
132
|
+
nothing. `ds-bar-chart`'s row gap moved from `row-gap` on the list to padding on each row, for
|
|
133
|
+
the same reason: a reader aiming between two bars used to hit neither. That last one makes the
|
|
134
|
+
bar plot one full `--ds-bar-chart-row-gap` taller — 20px at the default — because the first row
|
|
135
|
+
now carries half a gap above it and the last half a gap below.
|
|
136
|
+
|
|
137
|
+
- **A tooltip now says what the chart does not already print.** On `ds-bar-chart` and
|
|
138
|
+
`ds-column-chart` it repeated the label and the value that sit beside the mark, which told the
|
|
139
|
+
reader nothing they were not looking at. Both now carry a second line — the mark's share of the
|
|
140
|
+
total, `18.6% of total`, arithmetic the reader should not have to do — and `ds-funnel-chart`
|
|
141
|
+
carries the drop into the stage, which the shape cannot show. A mark whose value is zero or
|
|
142
|
+
negative has no share of anything visible and gets no second line at all. `ds-donut-chart` gets
|
|
143
|
+
none either: its panel and its legend both already print the percentage. A projected
|
|
144
|
+
`#dsChartTooltip` template still replaces the lot.
|
|
145
|
+
|
|
146
|
+
- **`ds-line-chart`'s crosshair moves as one object and fades on the way in and out.** The band and
|
|
147
|
+
the cursor line are one group carrying a `translateX`, so following the pointer is a single
|
|
148
|
+
transform rather than an attribute write per shape. It is not transitioned: the crosshair belongs
|
|
149
|
+
under the pointer, and easing it there makes it arrive late over readings it was never on.
|
|
150
|
+
|
|
151
|
+
- **`ds-line-chart`'s crosshair covers both plots under `yAxisMode="stacked"`.** It stopped at the
|
|
152
|
+
upper plot's baseline, so the lower plot — same category, same pointer — had nothing marked at
|
|
153
|
+
all.
|
|
154
|
+
|
|
155
|
+
- **`ds-donut-chart` fades as one ring rather than slice by slice.** Arcs share their edges, and
|
|
156
|
+
two semi-transparent shapes butting up along one let the background through the seam — which
|
|
157
|
+
reads as the slice proportions shifting slightly as the fade ends. Compositing the ring first and
|
|
158
|
+
fading the result cannot do that. `staggerMs` therefore has no effect on this chart — one object
|
|
159
|
+
arrives, not five — and the input stays only for parity with the other four.
|
|
160
|
+
|
|
161
|
+
- **A chart keeps its height in every state.** An empty `data`, a failed request, or a legend that
|
|
162
|
+
switched the last series off used to shrink the chart to a line of text, which drags the page up
|
|
163
|
+
under the reader at exactly the moment they are being told something. The message now stands in a
|
|
164
|
+
box the size of the plot it replaces, on all five. What sizes that box differs by chart:
|
|
165
|
+
`ds-column-chart` and `ds-line-chart` use their `--ds-*-plot-height`, `ds-donut-chart` its
|
|
166
|
+
`--ds-donut-chart-size`, and `ds-bar-chart` and `ds-funnel-chart` reserve three rows or stages,
|
|
167
|
+
so a chart that normally draws ten rows still shrinks to that reserve.
|
|
168
|
+
|
|
169
|
+
- **Dimming the other marks is a separate opt-in, and it is off.** `dimOthers` fades the marks that
|
|
170
|
+
are not singled out: on `ds-bar-chart`, `ds-column-chart`, `ds-donut-chart` and `ds-funnel-chart`
|
|
171
|
+
that is every mark but the hovered or focused one, and on `ds-line-chart` — which has no mark
|
|
172
|
+
between two readings to hover — it follows the legend's highlight. It used to ride along with
|
|
173
|
+
`interactive`, and it is off by default because the fade costs the separation BETWEEN the faded
|
|
174
|
+
marks: in OKLab dE ×100, the worst pair of three dimmed series falls from 14.8 at full opacity to
|
|
175
|
+
2.1 at `--ds-chart-dim-opacity`'s default. It buys loudness for one mark and pays for it with the
|
|
176
|
+
rest of the chart. A chart that had the fade gets it back with one attribute.
|
|
177
|
+
|
|
178
|
+
```html
|
|
179
|
+
<ds-donut-chart interactive dimOthers [data]="slices" />
|
|
180
|
+
```
|
|
181
|
+
|
|
182
|
+
- **A hidden legend row is no longer struck through.** The unchecked box says what happened and the
|
|
183
|
+
muted label agrees with it; a strike-through says the label itself is wrong.
|
|
184
|
+
|
|
185
|
+
- **A legend's colour chips arrive with the marks they name.** They used to be solid from the first
|
|
186
|
+
frame while the plot was still fading in, which reads as two objects rather than one. The chip
|
|
187
|
+
now fades on the same curve and the same delay: `ds-chart-legend`'s swatch and, where the legend
|
|
188
|
+
toggles, its checkbox; `ds-donut-chart`'s legend swatch; and `ds-funnel-chart`'s stage-table
|
|
189
|
+
swatch. Nothing in your code changes, and a screenshot test that captures a chart mid-entrance
|
|
190
|
+
will differ.
|
|
191
|
+
|
|
192
|
+
- **A `title` input no longer leaves a native browser tooltip over the component.** `title` is a
|
|
193
|
+
global HTML attribute, so `<ds-modal title="Settings">` both fed the input AND left the attribute
|
|
194
|
+
in the DOM — and the browser then raised its own tooltip over the whole component, naming it
|
|
195
|
+
rather than whatever the pointer was resting on. Eleven components drop the attribute:
|
|
196
|
+
`ds-accordion-item`, `ds-alert`, `ds-banner`, `ds-bottom-sheet`, `ds-drawer`, `ds-empty-state`,
|
|
197
|
+
`ds-list-item`, `ds-modal`, `ds-modal-card`, `ds-page-header` and `ds-toast`. Each renders the
|
|
198
|
+
title as visible text and names itself through `aria-labelledby` where it needs a name, so
|
|
199
|
+
nothing is lost to assistive technology.
|
|
200
|
+
|
|
201
|
+
This wins over a `[attr.title]` of your own on those hosts — bind it and the attribute is still
|
|
202
|
+
removed. If you want a native tooltip there, put it on a wrapper or a projected child, or use
|
|
203
|
+
`dsTooltip`.
|
|
204
|
+
|
|
205
|
+
- **A chart tooltip no longer fights the pointer that opened it.** The panel opens under the
|
|
206
|
+
cursor, and the CDK pane it is portaled into takes pointer events by default — so the panel
|
|
207
|
+
covered the plot, the plot took a `pointerleave`, the chart cleared its hover, the panel closed,
|
|
208
|
+
the pointer landed on the plot again, and the whole thing flickered for as long as the cursor sat
|
|
209
|
+
there. The pane is `pointer-events: none` now; `pointer-events` on the panel alone never reached
|
|
210
|
+
it.
|
|
211
|
+
|
|
212
|
+
- **`ds-column-chart` answers the pointer near its column, not across the whole category slot.** A
|
|
213
|
+
column is capped at `--ds-column-chart-column-max-width` while its slot is a `1fr` share of the
|
|
214
|
+
plot, so on a wide chart the hover reached well past the mark on either side. The target is
|
|
215
|
+
`--ds-column-chart-column-max-width` plus one `--ds-column-chart-column-gap` — half the gap each
|
|
216
|
+
side, the rule the funnel's bands already follow — and it spans the category cell's FULL height:
|
|
217
|
+
the plot, the axis gap under it, and the label. Split across the plot and the label alone, the
|
|
218
|
+
axis gap answered for neither, so a pointer travelling between them crossed a band where the
|
|
219
|
+
tooltip closed and reopened. It never exceeds the slot, and where the column is narrower than its
|
|
220
|
+
cap the target is wider than the column itself.
|
|
221
|
+
|
|
222
|
+
`.plot-cell` is no longer a positioned box and no longer carries the `::after` that catches the
|
|
223
|
+
pointer; `.column` is and does. A rule of yours that positioned something against `.plot-cell`
|
|
224
|
+
now resolves against `.column`.
|
|
225
|
+
|
|
226
|
+
- **The legend's checkboxes are not permanently ringed.** `ds-chart-legend` applied the focus ring
|
|
227
|
+
unconditionally instead of under `:focus-visible`, so every legend row looked focused. The
|
|
228
|
+
library's global `:where(:focus-visible)` rule already rings them, so the component needs none of
|
|
229
|
+
its own.
|
|
230
|
+
|
|
231
|
+
- **A mark's colour change eases instead of jumping,** and a dimmed line fades again. Each mark
|
|
232
|
+
animated exactly one property, because a second `transition` on the same selector REPLACES the
|
|
233
|
+
first rather than adding to it: `ds-line-chart`'s line kept `stroke-width` and lost the dim fade,
|
|
234
|
+
its marker kept `r` and lost the same, and no mark eased its paint at all. Opacity, geometry and
|
|
235
|
+
colour now travel in ONE declaration wherever they share a selector — so recolouring a row,
|
|
236
|
+
pinning a palette slot, or adding a funnel stage and re-spreading the ramp all ease. If you
|
|
237
|
+
declare your own `transition` on a chart mark, name every property it was already easing.
|
|
238
|
+
|
|
239
|
+
- **A chart tooltip closes when the page scrolls.** CDK's reposition strategy watches `window` and
|
|
240
|
+
registered `cdkScrollable`s only, so an app's own `overflow: auto` container left the panel
|
|
241
|
+
pinned in space while the chart scrolled out from under it. `ds-line-chart` reopens on the next
|
|
242
|
+
pointer move; the other four reopen when the pointer leaves a mark and enters one again.
|
|
243
|
+
|
|
244
|
+
The internal `ChartTooltipDirective`, which the package root does not export, grows one PRIVATE
|
|
245
|
+
member, `detachScrollClose`. `@ids-group-ltd/ids-design-system/components/chart-tooltip` is the
|
|
246
|
+
only specifier that reaches the class; a subclass declaring that name must rename it, because
|
|
247
|
+
TS2415 fires on the collision and `override` does not clear it for a private member.
|
|
248
|
+
|
|
249
|
+
- **The helper behind a chart tooltip's second line is renamed.** The internal `describeStanding`,
|
|
250
|
+
which returned the rank alongside the share, is the internal `describeShare` now. Neither is
|
|
251
|
+
exported from the package root, but `@ids-group-ltd/ids-design-system/components` exports them,
|
|
252
|
+
so an import of the old name stops resolving. Rename it; the signature is unchanged.
|
|
253
|
+
|
|
254
|
+
### Fixed
|
|
255
|
+
|
|
256
|
+
- **`ds-table`'s pagination footer insets per side, so the summary lines up with column one.** The
|
|
257
|
+
footer read `--ds-table-cell-pad-x` alone while the cells resolve `--ds-table-cell-pad-left` and
|
|
258
|
+
`-right` separately. A table asking for a flush first column — `--ds-table-cell-pad-left: 0`
|
|
259
|
+
with `-right` set and `-x` unset — got a footer at the 16px default while the column sat at 0.
|
|
260
|
+
The footer now walks the same per-side chain; `-x` still works as the shorthand for both.
|
|
261
|
+
|
|
262
|
+
One gap is left: `density="compact"` retunes the cells' padding on the table element itself, and
|
|
263
|
+
the footer sits outside that element rather than inside it, so a compact table with no
|
|
264
|
+
`--ds-table-cell-pad-*` of its own still has 12px cells under a 16px footer. Set
|
|
265
|
+
`--ds-table-cell-pad-x: var(--space-3)` beside `density="compact"`, or keep a local rule on the
|
|
266
|
+
footer.
|
|
267
|
+
|
|
268
|
+
- **`ds-donut-chart`'s error state holds the plot's height.** It rendered the message as a bare
|
|
269
|
+
paragraph, so a failed request collapsed the ring's 180px to one line of text and dragged the
|
|
270
|
+
page up under the reader. It now stands in the same ring-sized box the no-data state already
|
|
271
|
+
used. The message carries `empty-text is-error` where it carried `empty is-error`, so a rule of
|
|
272
|
+
yours written against `.empty.is-error` inside this chart no longer matches.
|
|
273
|
+
|
|
274
|
+
- **A role token set on an app shell no longer outranks your rule on a portaled panel.** A panel
|
|
275
|
+
sits in `document.body`, so the component copies the roles it needs onto the pane as an inline
|
|
276
|
+
style. It decided what to copy by comparing the host with `:root` — and because custom properties
|
|
277
|
+
inherit, a shell setting `--ds-radius-panel` for its own chrome made every picker under it an
|
|
278
|
+
overrider, each pinning the shell's value inline. A rule on `.ds-overlay-pane`, which is the only
|
|
279
|
+
route a stylesheet has to a portaled panel, then lost to a value nobody wrote. The comparison is
|
|
280
|
+
now against the host's PARENT, so only a role the host declares itself travels.
|
|
281
|
+
|
|
282
|
+
If you were relying on an ancestor's role reaching a panel, set it on the component instead —
|
|
283
|
+
`ds-select { --ds-radius-panel: 8px }` still forwards — or use the panel's own hook, such as
|
|
284
|
+
`--ds-dropdown-panel-radius`, which is forwarded with no such test.
|
|
285
|
+
|
|
286
|
+
### What you can now DELETE
|
|
287
|
+
|
|
288
|
+
| your workaround | why it is unnecessary | replace with |
|
|
289
|
+
| --- | --- | --- |
|
|
290
|
+
| `.ds-overlay-pane .dropdown-panel .option` — a deep rule retyping dropdown rows | the row's weight, size, line-height and family are hooks that forward per instance | `--ds-option-weight`, `--ds-option-font-size`, `--ds-option-line-height`, `--ds-option-font-family` |
|
|
291
|
+
| `ds-modal .title.title` — a rule outspecifying the modal's own title rule only to set `font-family` | the title reads a family hook, which needs no specificity at all | `--ds-modal-title-font-family` |
|
|
292
|
+
| `.pagination-footer` — a local rule re-insetting the table's footer to match a per-side gutter | the footer resolves the same left/right chain the cells do | nothing, UNLESS the table is `density="compact"` and sets no `--ds-table-cell-pad-*` — there the footer is still 4px wider than the cells and the rule is still doing work |
|
|
293
|
+
|
|
294
|
+
## 0.13.0 — 2026-09-14
|
|
295
|
+
|
|
296
|
+
### Breaking
|
|
297
|
+
|
|
298
|
+
- **`ds-field-group` renders its chrome on an inner row, not on the host.** The border, radius,
|
|
299
|
+
focus ring and the divider between segments moved from `:host` to `.row`, because the group now
|
|
300
|
+
carries a message of its own and that line has to sit OUTSIDE the bordered box. A stylesheet that
|
|
301
|
+
reached `ds-field-group` to change its border, radius or padding now targets a box that no longer
|
|
302
|
+
has them.
|
|
303
|
+
|
|
304
|
+
```scss
|
|
305
|
+
/* before */ /* after — or better, use the tokens */
|
|
306
|
+
ds-field-group { border: 0; } ds-field-group .row { border: 0; }
|
|
307
|
+
```
|
|
308
|
+
|
|
309
|
+
Every `--ds-field-group-*` token is unchanged and still declared on the host, so an override
|
|
310
|
+
written through the tokens needs nothing. The host's own box is unchanged too while the group has
|
|
311
|
+
no message: measured in the docs app, the row stays 40px and the host stays 40px — it grows to
|
|
312
|
+
57px only once `error` or `hint` is bound.
|
|
313
|
+
|
|
314
|
+
- **`--ds-button-border` is `--ds-button-border-color`, and `--ds-button-border-disabled` is
|
|
315
|
+
`--ds-button-border-color-disabled`.** Both name a COLOUR, and since the width moved out to
|
|
316
|
+
`--ds-button-border-width` beside them the old names read like a `border` shorthand — set
|
|
317
|
+
`2px solid red` on one and nothing happens. The values and defaults are unchanged; only the
|
|
318
|
+
names moved.
|
|
319
|
+
|
|
320
|
+
```scss
|
|
321
|
+
/* before */ /* after */
|
|
322
|
+
ds-button { ds-button {
|
|
323
|
+
--ds-button-border: var(--brand); --ds-button-border-color: var(--brand);
|
|
324
|
+
} }
|
|
325
|
+
```
|
|
326
|
+
|
|
327
|
+
- **A `ds-button`, `ds-sidenav-item` or `ds-sidenav-group` link no longer claims to be a page it
|
|
328
|
+
is only inside of.** `aria-current` was derived from `routerLinkActive`, which matches by
|
|
329
|
+
PREFIX — so a "back to the section" link on `/case-studies/retail` announced
|
|
330
|
+
`aria-current="page"` for `/case-studies`, a page the reader was leaving rather than on. It now
|
|
331
|
+
says what ARIA means: an exact match announces `page`, a prefix match announces `true`, anything
|
|
332
|
+
else announces nothing. The `active` CLASS still matches by prefix, so nothing changes visually.
|
|
333
|
+
|
|
334
|
+
Only a screen reader hears the difference, which is why it went unnoticed for so long — on
|
|
335
|
+
`ds-button` the `active` class is painted by nothing at all. If a test asserted
|
|
336
|
+
`aria-current="page"` on a section link, it now reads `true`.
|
|
337
|
+
|
|
338
|
+
- **Thirty-one chart palette tokens are renamed, and an override written against an old name
|
|
339
|
+
stops applying in silence.** A custom property that no longer resolves is invalid at
|
|
340
|
+
computed-value time, so the whole declaration around it is dropped: `background:
|
|
341
|
+
var(--chart-cat-3)` paints nothing, a `:root` override of `--chart-cat-3` simply never reaches
|
|
342
|
+
the chart, and neither reports an error. Five groups:
|
|
343
|
+
|
|
344
|
+
- Categorical series — `--chart-cat-1` … `--chart-cat-8` become `--chart-categorical-1` …
|
|
345
|
+
`--chart-categorical-8`.
|
|
346
|
+
- Sequential ramp — `--chart-seq-1` … `--chart-seq-6` become `--chart-sequential-1` …
|
|
347
|
+
`--chart-sequential-6`.
|
|
348
|
+
- Divergent ramp — `--chart-div--3` … `--chart-div-3` become `--chart-divergent--3` …
|
|
349
|
+
`--chart-divergent-3`, signed suffix and all.
|
|
350
|
+
- Colours taking the `-color` the rest of the library carries — `--chart-axis-line`,
|
|
351
|
+
`--chart-axis-label`, `--chart-grid-line`, `--chart-cursor-line` and `--chart-tooltip-border`.
|
|
352
|
+
- Abbreviations spelled out — `--chart-axis-fs` becomes `--chart-axis-font-size`,
|
|
353
|
+
`--chart-line-w` becomes `--chart-line-width`, `--chart-line-w-bold` becomes
|
|
354
|
+
`--chart-line-width-bold`, `--chart-dot-r` becomes `--chart-dot-radius`, and
|
|
355
|
+
`--chart-dot-r-active` becomes `--chart-dot-radius-active`.
|
|
356
|
+
|
|
357
|
+
Three more are REMOVED rather than renamed, because no chart draws what they named and the
|
|
358
|
+
`--ds-chart-*` token each fed reached no rule: `--chart-axis-title`, `--chart-grid-line-strong`
|
|
359
|
+
and `--chart-tick-size`. Handle `--chart-grid-line-strong` before `--chart-grid-line`: the short
|
|
360
|
+
name is a prefix of the long one, and a prefix-blind sweep renames this one instead of deleting
|
|
361
|
+
it.
|
|
362
|
+
|
|
363
|
+
The sequential and divergent VALUES are unchanged in both themes; the eight categorical values are
|
|
364
|
+
not — they are retuned in this same release, so a rename there lands a different colour rather than
|
|
365
|
+
the same one under a new name. `--chart-bar-gap`, `--chart-hover-bg-color`, `--chart-tooltip-bg-color` and
|
|
366
|
+
`--chart-tooltip-text-color` keep their names. Recolouring a series
|
|
367
|
+
is better done through the `--ds-chart-` layer below than through the palette.
|
|
368
|
+
|
|
369
|
+
- **`DsFieldGroupContext` carries two more members, and a class that IMPLEMENTS it no longer
|
|
370
|
+
compiles.** The interface behind `DS_FIELD_GROUP` had one member, `sizeResolved`; it now also
|
|
371
|
+
declares `invalidResolved: () => boolean` and `messageId: () => string | null`, because a segment
|
|
372
|
+
has to read the group's RESOLVED error state — an `error` string counts, not only the `invalid`
|
|
373
|
+
flag — and has to add the group's one message to its own `aria-describedby`. Anyone who provides
|
|
374
|
+
`DS_FIELD_GROUP` from their own wrapper so that DS fields behave as segments inside it gets
|
|
375
|
+
TS2420 until both are supplied: a compile error, not a silent change.
|
|
376
|
+
|
|
377
|
+
```ts
|
|
378
|
+
providers: [{ provide: DS_FIELD_GROUP, useValue: {
|
|
379
|
+
sizeResolved: () => 'md',
|
|
380
|
+
invalidResolved: () => this.invalid(),
|
|
381
|
+
messageId: () => this.messageId(),
|
|
382
|
+
} satisfies DsFieldGroupContext }]
|
|
383
|
+
```
|
|
384
|
+
|
|
385
|
+
`() => false` and `() => null` reproduce the old behaviour exactly. Only a consumer who PROVIDES
|
|
386
|
+
the token is affected; injecting it to read the context is unchanged and gains two members.
|
|
387
|
+
|
|
388
|
+
- **`TableRowAction.label` is `string | ((row: T) => string)`, which breaks code that READS it.**
|
|
389
|
+
Writing an action is unaffected — a plain string still compiles. But `rowActionSelected` hands
|
|
390
|
+
back the action, and `event.action.label` is now a union: assigning it to a `string`, or calling
|
|
391
|
+
a string method on it, is a compile error rather than a silent wrong value.
|
|
392
|
+
|
|
393
|
+
```ts
|
|
394
|
+
const label = typeof event.action.label === 'string'
|
|
395
|
+
? event.action.label
|
|
396
|
+
: event.action.label(event.row);
|
|
397
|
+
```
|
|
398
|
+
|
|
399
|
+
Branch on `event.action.id` instead wherever the label was only standing in for the identity —
|
|
400
|
+
that is what `id` is for, and it stayed a `string`.
|
|
401
|
+
|
|
402
|
+
- **A `ds-stat` label clips to one line.** It wrapped freely before, so a two-word label took two
|
|
403
|
+
lines and made its tile taller than the ones beside it; it now truncates with an ellipsis and
|
|
404
|
+
discloses the full text in a tooltip on hover. There is no hook to put the wrapping back — the
|
|
405
|
+
value's `--ds-stat-value-white-space`, `--ds-stat-value-lines` and `--ds-stat-value-wrap` govern
|
|
406
|
+
the value alone. A label that was relying on two lines needs shortening, or a wider tile.
|
|
407
|
+
|
|
408
|
+
### Added
|
|
409
|
+
|
|
410
|
+
- **`LineChartPoint` is exported.** `(pointClicked)` on `ds-line-chart` has always emitted it, and
|
|
411
|
+
the type was reachable from nowhere — a consumer typing the handler had to restate the shape by
|
|
412
|
+
hand.
|
|
413
|
+
|
|
414
|
+
- **The focus ring on a chart mark is two tones, and it is drawn rather than outlined.** A white
|
|
415
|
+
stroke with a dark halo around it, because one tone is not enough: an accent ring disappears on a
|
|
416
|
+
mark of its own hue family, and a chart's marks are exactly the surfaces a ring has to survive.
|
|
417
|
+
Measured in Chrome on 2026-09-14, WCAG contrast against each of the eight categorical colours:
|
|
418
|
+
the white stroke runs 3.01 – 9.45 and the halo 1.83 – 5.75, so every series colour clears 3:1
|
|
419
|
+
against at least one tone, and the halo clears 17.32 against the chart's own surface.
|
|
420
|
+
`--ds-chart-focus-ring-color` and `--ds-chart-focus-halo-color` are the hooks.
|
|
421
|
+
|
|
422
|
+
`outline` is not the mechanism because on an SVG element it paints the BOUNDING BOX rather than
|
|
423
|
+
the silhouette — a donut slice would ring as a rectangle.
|
|
424
|
+
|
|
425
|
+
**Forced colours are handled explicitly.** `fill` and `stroke` are not remapped by Windows High
|
|
426
|
+
Contrast, so a chart keeps every series colour, they all resolve to the same one against the
|
|
427
|
+
forced background, and nothing reports a problem. Axes, gridlines and labels now take `CanvasText`
|
|
428
|
+
and the focus ring takes `Highlight` under `(forced-colors: active)`.
|
|
429
|
+
|
|
430
|
+
- **`ds-line-chart` takes `patterns`, a second encoding channel.** Each series gets a dash of its
|
|
431
|
+
own from a fixed list, in the same order as the palette slots, so the lines are told apart by
|
|
432
|
+
shape as well as by colour — WCAG technique G111. Slot 1 stays solid, so a single-series chart is
|
|
433
|
+
unchanged by turning it on. Off by default: the shipped palette clears the colour-blind
|
|
434
|
+
separation threshold on its own, and this is for monochrome print, a retuned palette, or a reader
|
|
435
|
+
who asks for it.
|
|
436
|
+
|
|
437
|
+
```html
|
|
438
|
+
<ds-line-chart patterns [series]="series" [categories]="months" />
|
|
439
|
+
```
|
|
440
|
+
|
|
441
|
+
The other four charts print a label beside every mark already — a bar's row, a column's category,
|
|
442
|
+
a donut's legend row, a funnel's stage — so colour is not what identifies a mark there.
|
|
443
|
+
|
|
444
|
+
- **A tap answers the way a hover does, and stays put.** Tapping a mark opens its tooltip and
|
|
445
|
+
LATCHES it: a touch fires `pointerleave` the instant the finger lifts, so without this the panel
|
|
446
|
+
would flash and vanish. The next tap outside the mark releases it. On `ds-line-chart` a tap
|
|
447
|
+
anywhere in the plot picks the category under the finger, the same as a pointer moving over it.
|
|
448
|
+
|
|
449
|
+
`ds-line-chart`'s markers carry a hit area rather than relying on the dot: a transparent
|
|
450
|
+
`non-scaling-stroke` of 24px on a fine pointer and 44px under `(pointer: coarse)`. Measured in
|
|
451
|
+
Chrome at a 390px viewport: the marker hit-tests 21px from its centre and misses at 25px, so the
|
|
452
|
+
touch target is 44px across whatever width the plot is scaled to — a stroke in viewBox units
|
|
453
|
+
would have been a different size on a narrow card than on a wide one. It is narrower on a fine
|
|
454
|
+
pointer because a 44px target on a dense chart swallows the neighbouring readings.
|
|
455
|
+
|
|
456
|
+
- **A mark that arrives and a mark that leaves are now two staged phases.** Removals run first, at
|
|
457
|
+
`--ds-motion-chart-mark-exit-duration`; additions wait that long and then run at
|
|
458
|
+
`--ds-motion-chart-mark-enter-duration`, so a vanishing mark and an arriving one are never on
|
|
459
|
+
screen together. The update phase — a mark changing size — is unchanged and still runs on
|
|
460
|
+
`--ds-motion-chart-mark-duration`.
|
|
461
|
+
|
|
462
|
+
`staggerMs` spaces the arrivals out. `0` is the default and means no stagger; `40` is the
|
|
463
|
+
documented step, and the total delay is capped at 300ms so a hundred-mark series does not take
|
|
464
|
+
three seconds to appear. `ds-donut-chart` takes the input for parity and ignores it: a ring
|
|
465
|
+
arrives as one object, so there is nothing to stagger. Measured on the docs card at `staggerMs="40"`: five columns
|
|
466
|
+
resolve to 0, 40, 80, 120 and 160ms.
|
|
467
|
+
|
|
468
|
+
```html
|
|
469
|
+
<ds-column-chart staggerMs="40" [data]="points" />
|
|
470
|
+
```
|
|
471
|
+
|
|
472
|
+
Every transition retargets rather than queues: a data change mid-animation continues from where
|
|
473
|
+
the mark actually is. Measured on the column chart's docs card — a bar caught at 163.4px when the
|
|
474
|
+
second change landed carried on to 169.6px, with no jump back to the first target.
|
|
475
|
+
|
|
476
|
+
`prefers-reduced-motion` needs nothing from the charts. The durations are tokens, the library's
|
|
477
|
+
global rule already zeroes them, and each mark then lands straight on its final size — measured
|
|
478
|
+
with the tokens zeroed: `animation-duration: 0s`, `animation-delay: 0s`, `opacity: 1`,
|
|
479
|
+
`transform: none`.
|
|
480
|
+
|
|
481
|
+
- **`ds-line-chart`'s legend can switch a series off.** `legendFilters` turns each entry into a
|
|
482
|
+
real `<input type="checkbox">` — keyboard-operable and correctly announced without inventing a
|
|
483
|
+
role — and `hiddenSeries` is a two-way `model`, so a page can drive the filter from a URL
|
|
484
|
+
parameter and read back what the reader chose. Hovering or focusing an entry dims every other
|
|
485
|
+
series to `--ds-chart-dim-opacity`.
|
|
486
|
+
|
|
487
|
+
```html
|
|
488
|
+
<ds-line-chart
|
|
489
|
+
legendFilters
|
|
490
|
+
[(hiddenSeries)]="hidden"
|
|
491
|
+
[series]="series"
|
|
492
|
+
[categories]="months" />
|
|
493
|
+
```
|
|
494
|
+
|
|
495
|
+
**The value axis does not move when a series is hidden.** `rescaleOnHide` opts into the other
|
|
496
|
+
behaviour, and it is off by default because a silent rescale turns a period-over-period
|
|
497
|
+
comparison into a different claim — measured on the docs card, hiding one series with the
|
|
498
|
+
default leaves the axis at `0 … 5K`, and with `rescaleOnHide` it becomes `0 … 1.6K`.
|
|
499
|
+
|
|
500
|
+
Switching every series off replaces the plot with `noVisibleSeriesText` — "All series are
|
|
501
|
+
hidden" by default — carried on a `role="status"` line, with the legend still rendered so the
|
|
502
|
+
reader can switch one back on. Without it the reader is left looking at an empty grid.
|
|
503
|
+
|
|
504
|
+
A legend without a filter is unchanged: `ds-line-chart` still draws one whenever there is more
|
|
505
|
+
than one series, and it is now `ds-chart-legend` rather than markup of its own.
|
|
506
|
+
|
|
507
|
+
- **Every chart answers a hover, a tap and a keyboard focus with a tooltip.** `ds-bar-chart`,
|
|
508
|
+
`ds-column-chart`, `ds-donut-chart` and `ds-funnel-chart` default to `tooltip="item"` — the mark
|
|
509
|
+
under the pointer, or the one holding focus. `ds-line-chart` defaults to `tooltip="axis"`: a
|
|
510
|
+
pointer names every series at the category under it, while tabbing to a marker names that series
|
|
511
|
+
alone, because focus is already on one reading. `tooltip="none"` turns it off.
|
|
512
|
+
|
|
513
|
+
The panel is portaled out of the chart's box, so a chart inside a small dashboard card is not
|
|
514
|
+
what clips it — with no room above the mark it flips below, then to either side, and is pushed
|
|
515
|
+
back on screen rather than cut. On a coarse pointer it clears the tap point by 48px instead of
|
|
516
|
+
12, so the panel is not under the finger.
|
|
517
|
+
|
|
518
|
+
```html
|
|
519
|
+
<ds-line-chart [series]="series" [categories]="months" tooltip="axis" />
|
|
520
|
+
<ds-donut-chart [data]="slices" tooltip="none" />
|
|
521
|
+
```
|
|
522
|
+
|
|
523
|
+
The content is a projected template, never a formatter string, so a tooltip can hold components
|
|
524
|
+
and markup rather than escaped text:
|
|
525
|
+
|
|
526
|
+
```html
|
|
527
|
+
<ds-column-chart [data]="points">
|
|
528
|
+
<ng-template #dsChartTooltip let-tip>
|
|
529
|
+
<strong>{{ tip.category }}</strong>
|
|
530
|
+
@for (entry of tip.entries; track entry.label) {
|
|
531
|
+
<p>{{ entry.label }}: {{ entry.formatted }}</p>
|
|
532
|
+
}
|
|
533
|
+
</ng-template>
|
|
534
|
+
</ds-column-chart>
|
|
535
|
+
```
|
|
536
|
+
|
|
537
|
+
Three tokens paint it — `--ds-chart-tooltip-bg-color`, `--ds-chart-tooltip-text-color` and
|
|
538
|
+
`--ds-chart-tooltip-border-color`. They were declared before this and reached no rule; they reach
|
|
539
|
+
one now. The panel carries `aria-hidden`, because every interactive mark already puts the same
|
|
540
|
+
label and value in its own accessible name and a screen reader would otherwise read each reading
|
|
541
|
+
twice.
|
|
542
|
+
|
|
543
|
+
- **Hovering or focusing one mark dims the others.** With `interactive` set on `ds-bar-chart`,
|
|
544
|
+
`ds-column-chart`, `ds-donut-chart` or `ds-funnel-chart`, the mark under the pointer or under
|
|
545
|
+
focus keeps its colour and every other mark drops to `--ds-chart-dim-opacity`, default `0.3` —
|
|
546
|
+
the highlight is a fade of the rest rather than a change to the thing being pointed at, so the
|
|
547
|
+
colour a reader is matching against the legend stays the colour it was. Without `interactive`
|
|
548
|
+
nothing dims: a chart nobody can click has no mark to single out.
|
|
549
|
+
|
|
550
|
+
```scss
|
|
551
|
+
/* a denser chart wants a deeper fade */
|
|
552
|
+
ds-donut-chart { --ds-chart-dim-opacity: 0.15; }
|
|
553
|
+
```
|
|
554
|
+
|
|
555
|
+
The fade runs on `--ds-motion-chart-state-duration` and `--ds-motion-chart-state-easing`, so a
|
|
556
|
+
consumer who slows or flattens chart state changes does it in one place for all four. Reduced
|
|
557
|
+
motion needs nothing from the chart — the library's global rule already zeroes every duration.
|
|
558
|
+
|
|
559
|
+
- **`ds-number-stepper` takes `--ds-number-stepper-field-width`.** The number between the two step
|
|
560
|
+
buttons is sized from the control's own box height — 1.25× it — which is right for two or three
|
|
561
|
+
digits and clips a five-digit quantity. The hook is that width, and the default is the value the
|
|
562
|
+
three sizes carried before, so nothing moved.
|
|
563
|
+
|
|
564
|
+
```scss
|
|
565
|
+
ds-number-stepper { --ds-number-stepper-field-width: 5ch; }
|
|
566
|
+
```
|
|
567
|
+
|
|
568
|
+
- **`ds-line-chart` highlights the category under the pointer.** A line has no mark between two
|
|
569
|
+
readings, so the hover target is the whole category: a band paints behind the plot and every
|
|
570
|
+
series' reading at that category grows to the active dot radius. The band is what survives a
|
|
571
|
+
finger covering it on touch, and the grown markers are what the tooltip will anchor to.
|
|
572
|
+
`--ds-chart-hover-bg-color` paints the band, `--ds-chart-cursor-line-color` the rule down its
|
|
573
|
+
centre and `--ds-chart-dot-radius-active` sizes the grown reading; all three were declared and
|
|
574
|
+
reached no rule until now. `--ds-line-chart-hover-bg-color`, `--ds-line-chart-cursor-line-color`
|
|
575
|
+
and `--ds-line-chart-dot-radius-active` override any of them for this chart alone. The band is
|
|
576
|
+
what survives a finger covering it, which a 1px rule on its own does not.
|
|
577
|
+
|
|
578
|
+
- **Every chart takes `error` and `errorText`.** A failed fetch had to render as `emptyText`, which
|
|
579
|
+
says "No data" when the truth is "could not load". The branch renders ahead of `loading` and
|
|
580
|
+
carries `role="status"`, so the message is announced when it replaces a spinner.
|
|
581
|
+
|
|
582
|
+
```html
|
|
583
|
+
<ds-bar-chart
|
|
584
|
+
[data]="rows"
|
|
585
|
+
[loading]="pending()"
|
|
586
|
+
[error]="failed()"
|
|
587
|
+
errorText="Could not reach the depot service" />
|
|
588
|
+
```
|
|
589
|
+
|
|
590
|
+
- **`BarChartRow` and `ColumnChartPoint` take an optional `id`.** Supplying it makes a reorder move
|
|
591
|
+
the DOM nodes instead of rewriting them; left out, the row keeps its position as its key, which is
|
|
592
|
+
what both charts did before. `DonutChartSlice` and `FunnelChartStage` already required one.
|
|
593
|
+
|
|
594
|
+
- **`ds-line-chart` takes `interactive` and emits `pointClicked`.** Every reading becomes a focusable
|
|
595
|
+
button carrying its series, its category and its value, so a click and a keyboard activation reach
|
|
596
|
+
the consumer the same way they already do on `ds-bar-chart`. A series drawn with
|
|
597
|
+
`showMarkers="false"` grows invisible markers when `interactive` is set, so there is something to
|
|
598
|
+
land on; they appear on hover and on focus.
|
|
599
|
+
|
|
600
|
+
```html
|
|
601
|
+
<ds-line-chart
|
|
602
|
+
interactive
|
|
603
|
+
[series]="series"
|
|
604
|
+
[categories]="months"
|
|
605
|
+
(pointClicked)="openMonth($event)" />
|
|
606
|
+
```
|
|
607
|
+
|
|
608
|
+
- **A `TableRowAction` can name itself per row, and can open a divider.** `label` takes
|
|
609
|
+
`(row) => string` as well as a string, so one action reads Pause on a live row and Resume on a
|
|
610
|
+
paused one under the SAME `id` — `rowActionSelected` still fires once with that id, instead of the
|
|
611
|
+
consumer declaring two actions whose `hidden` predicates have to be kept exact opposites by hand.
|
|
612
|
+
`divider: true` draws a line above an item, for the destructive tail that colour alone was
|
|
613
|
+
separating.
|
|
614
|
+
|
|
615
|
+
```ts
|
|
616
|
+
rowActions: TableRowAction<Run>[] = [
|
|
617
|
+
{ id: 'suspend', label: (row) => (row.active ? 'Pause' : 'Resume'), icon: 'refresh' },
|
|
618
|
+
{ id: 'delete', label: 'Delete', icon: 'trash', error: true, divider: true },
|
|
619
|
+
];
|
|
620
|
+
```
|
|
621
|
+
|
|
622
|
+
A divider on the FIRST item is ignored: a line at the top of a menu has nothing on one side of it.
|
|
623
|
+
Measured in the docs app across four rows — the label reads Pause on the active row and Resume on
|
|
624
|
+
the other three, and every menu renders exactly one divider, in document order between the last
|
|
625
|
+
ordinary item and Delete.
|
|
626
|
+
|
|
627
|
+
These are the last two of the four pieces asked for on 2026-08-18; `hidden` and `disabledReason`
|
|
628
|
+
shipped on 2026-08-21.
|
|
629
|
+
|
|
630
|
+
|
|
631
|
+
- **`ds-field-group` takes `error`, `hint` and `warning`, so the error it shows has words.** The
|
|
632
|
+
group suppresses its segments' own labels and message rows — they would break the glued line — and
|
|
633
|
+
until now it had nowhere for the text to go, which left colour as the only channel and 1.4.1
|
|
634
|
+
failing. It carries the same pair every field carries: `error` is a string that turns the state on
|
|
635
|
+
AND says what is wrong, `invalid` stays the flag for when the text lives in a form-level summary.
|
|
636
|
+
|
|
637
|
+
```html
|
|
638
|
+
<ds-field-group error="Введите сумму больше нуля">
|
|
639
|
+
<ds-select [options]="currencies" />
|
|
640
|
+
<ds-input grow [(value)]="amount" />
|
|
641
|
+
</ds-field-group>
|
|
642
|
+
```
|
|
643
|
+
|
|
644
|
+
It takes the rest of that base too: `reserveMessage` holds the message row's height while the
|
|
645
|
+
group is clean, so binding an error later does not push the form below it down, and
|
|
646
|
+
`messageIcon` overrides the glyph the state resolves to, or removes it with `false`.
|
|
647
|
+
|
|
648
|
+
**Every segment announces it, not just the first.** Each carries `aria-invalid` while the group is
|
|
649
|
+
in error and points at the one message through `aria-describedby`, so a reader who tabs straight to
|
|
650
|
+
the second segment hears it too — the group's border is not something a screen reader can see.
|
|
651
|
+
Measured in the docs app: both segments of an `error` group report `aria-invalid="true"` and the
|
|
652
|
+
same `aria-describedby`, and a `hint` group links the message without claiming an error.
|
|
653
|
+
|
|
654
|
+
The `invalid` input on every field already described this arrangement in its own documentation —
|
|
655
|
+
*"for when the text lives elsewhere, such as a form-level error summary or one message covering a
|
|
656
|
+
whole field group"*. The group was the half that had never been built.
|
|
657
|
+
|
|
658
|
+
- **`ds-button` forwards everything else a link can carry: `fragment`, `queryParams`,
|
|
659
|
+
`queryParamsHandling`, `target` and `rel`.** Each is a pass-through to the anchor the component
|
|
660
|
+
already renders, so a call-to-action with a destination modifier stays a `ds-button` instead of
|
|
661
|
+
falling back to a hand-written class.
|
|
662
|
+
|
|
663
|
+
```html
|
|
664
|
+
<ds-button [routerLink]="['/ai-solutions', slug]" fragment="enquiry">Talk to us</ds-button>
|
|
665
|
+
<ds-button [href]="demoUrl" target="_blank" rel="noopener">Open the demo</ds-button>
|
|
666
|
+
```
|
|
667
|
+
|
|
668
|
+
`fragment`, `queryParams` and `queryParamsHandling` belong to a `routerLink` destination and
|
|
669
|
+
dev-warn on any other; `target` and `rel` work on both link destinations and dev-warn on a plain
|
|
670
|
+
button.
|
|
671
|
+
|
|
672
|
+
- **`routerLink` accepts a `UrlTree`** on `ds-button`, `ds-sidenav-item` and `ds-sidenav-group`, so
|
|
673
|
+
the `UrlCreationOptions` with no input of their own — `relativeTo`, `preserveFragment` — are
|
|
674
|
+
reachable without waiting for one.
|
|
675
|
+
|
|
676
|
+
```ts
|
|
677
|
+
protected readonly enquiry = this.router.createUrlTree(['/ai-solutions', slug], {
|
|
678
|
+
fragment: 'enquiry',
|
|
679
|
+
});
|
|
680
|
+
```
|
|
681
|
+
|
|
682
|
+
- **`ariaCurrent` on `ds-button`, `ds-sidenav-item` and `ds-sidenav-group`, and
|
|
683
|
+
`routerLinkActiveOptions` on `ds-button`.** `ariaCurrent` overrides what the link announces,
|
|
684
|
+
including `null` for "announce nothing" and `'step'` or `'location'` where the link is not a
|
|
685
|
+
page. Left alone, the announcement follows the exact/prefix rule above and needs nothing from
|
|
686
|
+
the consumer.
|
|
687
|
+
|
|
688
|
+
`routerLinkActiveOptions` moves what the `active` CLASS matches — and, because the announcement
|
|
689
|
+
is written by the same directive, it also bounds the announcement: narrow it to
|
|
690
|
+
`{ exact: true }` and a prefix match is no longer active, so the link announces nothing at all
|
|
691
|
+
rather than `true`. Set it to change the highlight, and pass `ariaCurrent` alongside it if the
|
|
692
|
+
ancestor announcement still matters.
|
|
693
|
+
|
|
694
|
+
- **Ten classes grew their member surface, which breaks a subclass that declares the same name.**
|
|
695
|
+
Subclassing a DS component is unsupported (`design-system.md` § Components), so this reaches only
|
|
696
|
+
a consumer who does it — and there it is a build error, not a silent change. `ButtonComponent`
|
|
697
|
+
gained `fragment`, `queryParams`, `queryParamsHandling`, `target`, `rel`,
|
|
698
|
+
`routerLinkActiveOptions`, `ariaCurrent`, `linkModifiers` and `ariaCurrentResolved`;
|
|
699
|
+
`SidenavItemComponent` and `SidenavGroupComponent` each gained `ariaCurrent`, `noModifiers` and
|
|
700
|
+
`ariaCurrentResolved`; `TooltipDirective` gained `dsTooltipWhenClipped` and `tipText`;
|
|
701
|
+
`TableComponent` gained `actionLabel` and LOST `cellPopoverText`, `cellTextPopover`, `isClipped`,
|
|
702
|
+
`onCellClipClick` and `onHeaderEnter`, so a subclass that overrode one of the five now overrides
|
|
703
|
+
nothing. `FieldGroupComponent` gained `error`, `hint`,
|
|
704
|
+
`warning`, `messageIcon`, `reserveMessage`, `reserveMessageResolved`, `invalidResolved`,
|
|
705
|
+
`messageId`, `message`, `fieldMessage` and `uid` — it shares the fields' message base now;
|
|
706
|
+
`InputComponent` gained `groupMessage`, and `SelectComponent`, `AutocompleteComponent` and
|
|
707
|
+
`DatePickerComponent` gained `groupMessage` and `describedByIds`. Being public API or not is no protection:
|
|
708
|
+
`private` and `protected` collide with TS2415 exactly as a public name does.
|
|
709
|
+
|
|
710
|
+
`routerLink` also widened on the three navigating components — `string | readonly unknown[] |
|
|
711
|
+
null` became `DsRouterLink`, which adds `UrlTree`. Writing it is unaffected; code that READS the
|
|
712
|
+
value back, or overrides the input, has a new union member to handle.
|
|
713
|
+
- **`ds-stat` takes `--ds-stat-value-lines` and `--ds-stat-value-wrap`, which compose with the
|
|
714
|
+
`white-space` hook.** The three cover the shapes a KPI value actually needs: clip to one line
|
|
715
|
+
(the default), wrap freely, wrap and put the ellipsis on the line you name, or break a word wider
|
|
716
|
+
than the tile.
|
|
717
|
+
|
|
718
|
+
```scss
|
|
719
|
+
ds-stat { --ds-stat-value-white-space: normal; } /* wraps */
|
|
720
|
+
ds-stat { --ds-stat-value-white-space: normal; --ds-stat-value-lines: 2; } /* … then clips */
|
|
721
|
+
ds-stat { --ds-stat-value-white-space: normal; --ds-stat-value-wrap: anywhere; }
|
|
722
|
+
```
|
|
723
|
+
|
|
724
|
+
`--ds-stat-value-lines` only bites once the value wraps: a clamp on a `nowrap` box has nothing to
|
|
725
|
+
clamp. And wrapping alone does not keep a long value inside the card — a single word wider than
|
|
726
|
+
the tile still paints past the edge, which is what `--ds-stat-value-wrap: anywhere` is for.
|
|
727
|
+
|
|
728
|
+
Whatever is clipped is still readable: the label and the value each disclose their full text in a
|
|
729
|
+
tooltip on hover, and only when they are actually clipped, so a tile that fits shows no tip.
|
|
730
|
+
|
|
731
|
+
- **`dsTooltipWhenClipped`, so any host can disclose only what it is actually hiding.** With it the
|
|
732
|
+
tip opens only while the host shows less text than it holds, re-tested on every open — so it
|
|
733
|
+
appears and stops appearing as a column, panel or window is resized, with no observer to run. Left
|
|
734
|
+
with no `dsTooltip` text it discloses the host's own text, which is what makes it usable on
|
|
735
|
+
projected content.
|
|
736
|
+
|
|
737
|
+
```html
|
|
738
|
+
<span class="cell" dsTooltipWhenClipped [dsTooltip]="row.name">{{ row.name }}</span>
|
|
739
|
+
```
|
|
740
|
+
|
|
741
|
+
`isTextClipped(element)` is exported from `/core` behind it: true when the element, or anything it
|
|
742
|
+
renders, is showing less than it holds. Horizontal only — a clamped block hides whole lines and
|
|
743
|
+
its `scrollWidth` matches its `clientWidth`.
|
|
744
|
+
|
|
745
|
+
|
|
746
|
+
- **Five charts: `ds-bar-chart`, `ds-column-chart`, `ds-donut-chart`, `ds-funnel-chart` and
|
|
747
|
+
`ds-line-chart`.** Each takes a `caption`, a `summary` for the accessible name, a `loading`
|
|
748
|
+
skeleton sized to the real data so the chart does not resize when the numbers land, an `emptyText`
|
|
749
|
+
and a `valueFormat` — and each offers its numbers again as a table under a
|
|
750
|
+
`dataTable: 'toggle' | 'visible' | 'none'` disclosure, because a chart that only draws is a chart
|
|
751
|
+
a screen reader cannot read.
|
|
752
|
+
|
|
753
|
+
```html
|
|
754
|
+
<ds-bar-chart caption="Visitor funnel" [data]="rows" />
|
|
755
|
+
<ds-line-chart [categories]="months" [series]="series" yAxisMode="rounded" />
|
|
756
|
+
```
|
|
757
|
+
|
|
758
|
+
The two that carry real geometry are worth knowing about. `ds-funnel-chart` has a `shape`, and it
|
|
759
|
+
defaults to `'area'` — the silhouette with the stage boundaries moved so each band's AREA is
|
|
760
|
+
proportional to its value, the honest encoding that still leaves a tail you can put a label on.
|
|
761
|
+
`'width'` reads every boundary off the values, which collapses the tail of a steep funnel below a
|
|
762
|
+
labellable width. `'taper'` encodes NOTHING: the silhouette is fixed whatever the data, so editing
|
|
763
|
+
the values moves the table under it and never the shape — reach for it only where the numbers are
|
|
764
|
+
read from that table. `ds-line-chart` has a `yAxisMode` that only matters once a series sets
|
|
765
|
+
`axis: 'secondary'`: `'rounded'` and `'exact'` share one set of gridlines and differ in whether the
|
|
766
|
+
second axis rounds its step up or ends on its largest reading, `'independent'` grids each axis on
|
|
767
|
+
its own, and `'stacked'` draws two plots sharing the category axis.
|
|
768
|
+
|
|
769
|
+
All five take `interactive`, and it is the keyboard switch rather than the click switch: the click
|
|
770
|
+
output — `rowClicked`, `pointClicked`, `sliceClicked`, `stageClicked` and `ds-line-chart`'s own
|
|
771
|
+
`pointClicked` — fires with or without the flag. With it set, every mark joins the tab order as a
|
|
772
|
+
`role="button"` answering Enter and Space, and the container announces itself as a `group` rather
|
|
773
|
+
than an `img`; that swap is load-bearing rather than cosmetic, because `role="img"` makes a
|
|
774
|
+
browser treat everything inside as presentational, and a focusable mark inside one is not
|
|
775
|
+
reachable at all.
|
|
776
|
+
|
|
777
|
+
`ds-donut-chart` is the exception, and deliberately: its arcs take the keyboard route only when
|
|
778
|
+
`legend="none"`. Where a legend is drawn, its rows already carry the route, and making both
|
|
779
|
+
focusable would give a four-slice chart eight tab stops for four things.
|
|
780
|
+
|
|
781
|
+
The focus ring on an SVG mark is a drawn stroke, not an `outline` — an outline on an SVG element
|
|
782
|
+
paints its BOUNDING BOX rather than its silhouette, so a funnel stage would ring as a flat bar
|
|
783
|
+
across its trapezoid. `--ds-funnel-chart-focus-color` and `--ds-funnel-chart-focus-width`,
|
|
784
|
+
`--ds-line-chart-focus-color` and `--ds-line-chart-focus-width`, and
|
|
785
|
+
`--ds-donut-chart-focus-color` and `--ds-donut-chart-focus-width` set it, each falling back to
|
|
786
|
+
`--focus-ring-color` and `--focus-ring-width`. Under forced colours the outline is kept instead,
|
|
787
|
+
where `stroke` is not remapped.
|
|
788
|
+
|
|
789
|
+
**Each chart draws its own frame** — border, radius, padding and an `--surface-default` background
|
|
790
|
+
— which is unusual in this library, where a component resists owning chrome. A chart earns the
|
|
791
|
+
exception because it is read as an object rather than as a block of text: a plot, its axes, a
|
|
792
|
+
legend and an annex table all run into the page without an edge. One already sitting in a card
|
|
793
|
+
drops it with `--ds-chart-frame-border-width: 0` and `--ds-chart-frame-padding: 0`.
|
|
794
|
+
|
|
795
|
+
`ds-donut-chart` also takes `maxSlices`, which caps the legend: past it the smallest slices are
|
|
796
|
+
summed into one named by `otherLabel`, on the neutral eighth palette colour. Off by default —
|
|
797
|
+
grouping changes what the chart says, so it is the consumer's call — and the tail is summed rather
|
|
798
|
+
than dropped, so the total never moves.
|
|
799
|
+
|
|
800
|
+
Two geometry rules are worth knowing because they are not preferences. `ds-donut-chart` holds its
|
|
801
|
+
centre content to the square that fits inside the hole, so a long `centerLabel` wraps instead of
|
|
802
|
+
running out over the ring, and the text carries a halo of the chart's own background — at
|
|
803
|
+
`thickness: 1` it sits on the slices, where no single text colour is readable against three
|
|
804
|
+
different hues. And `ds-bar-chart` keeps a label far closer to its own bar than to the next row,
|
|
805
|
+
because levelling the two makes the eye group a bar with the label BELOW it and read every row off
|
|
806
|
+
by one.
|
|
807
|
+
|
|
808
|
+
|
|
809
|
+
- **Chart colour is three families, and reaching for the wrong one is the usual chart bug.** The
|
|
810
|
+
eight `--ds-chart-series-N-color` hooks are CATEGORICAL — they separate marks that are DIFFERENT
|
|
811
|
+
THINGS, such as donut slices or line series. A bar chart's rows are not different things; they are
|
|
812
|
+
one series measured five times, and painting them from a categorical palette says five categories
|
|
813
|
+
where there is one. So a single series has hooks of its own, and ordered stages have a third set:
|
|
814
|
+
|
|
815
|
+
```scss
|
|
816
|
+
/* different things */ --ds-chart-series-1-color … --ds-chart-series-8-color
|
|
817
|
+
/* one thing, measured often */ --ds-chart-series-default-color + --ds-chart-series-accent-color
|
|
818
|
+
/* ordered stages of one */ --ds-chart-ramp-1-color … --ds-chart-ramp-8-color
|
|
819
|
+
```
|
|
820
|
+
|
|
821
|
+
`ds-bar-chart` takes the single-series pair: every row shares `--ds-chart-series-default-color`, and
|
|
822
|
+
setting `color` on one row marks the one the reader should land on — usually
|
|
823
|
+
`var(--ds-chart-series-accent-color)`. There is no accent flag, because the accent is a colour and a
|
|
824
|
+
boolean would only be a less flexible way of setting one. `ds-funnel-chart` takes the ramp, spread
|
|
825
|
+
across however many stages there are, with the last stage leaving it for the accent.
|
|
826
|
+
`ds-donut-chart`, `ds-line-chart` and `ds-column-chart` take the categorical set — a column often IS
|
|
827
|
+
a separate thing (revenue by region), and where a column chart is instead one quantity over time,
|
|
828
|
+
`color` puts every column on the single-series colour in one pass.
|
|
829
|
+
|
|
830
|
+
The categorical eight are retuned with this: led by coral and teal, each clearing 3:1 on white for
|
|
831
|
+
WCAG 1.4.11 and at least dE 15 from every other under normal, deuteranope and protanope vision. No
|
|
832
|
+
hue sits between 35 and 130 — a yellow or a lime is high-luminance by nature, and dragging one down
|
|
833
|
+
to clear the contrast floor turns it to mustard. Slot 8 is a neutral rather than a ninth hue: every
|
|
834
|
+
eighth HUE that clears the floor lands within dE 4 of one of the other seven under some colour-vision
|
|
835
|
+
deficiency, so the honest eighth is one that has no hue to collide with.
|
|
836
|
+
|
|
837
|
+
### Changed
|
|
838
|
+
|
|
839
|
+
- **`--ds-chart-line-width-bold` now reaches a rule.** Highlighting one `ds-line-chart` series —
|
|
840
|
+
from the legend, or from a mark — thickens it to that width as well as dimming the others, so the
|
|
841
|
+
highlight survives a monochrome print and a reader who cannot tell the two hues apart.
|
|
842
|
+
|
|
843
|
+
- **A chart's generated description leads with what the chart says, not with how it is drawn.** The
|
|
844
|
+
order is now: what it is and its scale, the trend, the extremes, then where the numbers are —
|
|
845
|
+
`"Visits by month, 3 points, 1,620 to 2,410. Rising throughout. Highest in Nov at 2,410, lowest
|
|
846
|
+
in Sep at 1,620. Full values in the table below."` It used to recite first-to-last and then the
|
|
847
|
+
extremes, which is a recital of the encoding, and blind readers rank that lowest of the four
|
|
848
|
+
levels of chart description — the encoding is the one thing a screen-reader user cannot use.
|
|
849
|
+
|
|
850
|
+
The trend is named rather than implied: a series that only ever rises reads "Rising throughout",
|
|
851
|
+
one that dips on the way up reads "Rising overall", and one that returns to its starting value
|
|
852
|
+
reads "Ending where it started".
|
|
853
|
+
|
|
854
|
+
The closing pointer follows the table: a chart at `dataTable="none"` no longer promises a table
|
|
855
|
+
that is not rendered. `summary` still overrides the whole sentence.
|
|
856
|
+
|
|
857
|
+
- **An `interactive` chart is one tab stop, not one per mark.** Arrow keys walk the marks, Home and
|
|
858
|
+
End reach the extremes, and the ends wrap the way `ds-radio-group`'s do. `ds-line-chart` keeps one
|
|
859
|
+
stop PER SERIES, so a two-series plot is two stops and each line is a strand the arrows walk;
|
|
860
|
+
measured on the docs card, twelve markers now expose two tab stops instead of twelve.
|
|
861
|
+
|
|
862
|
+
WCAG 2.1.1's Understanding is explicit that not every mouse-operable control has to be separately
|
|
863
|
+
focusable, and that is the permission this rests on. Nothing in the API changed — a page that
|
|
864
|
+
bound `interactive` and an output needs no edit — but a test that counted `[tabindex="0"]` inside
|
|
865
|
+
a chart will now see one per series.
|
|
866
|
+
|
|
867
|
+
|
|
868
|
+
### Fixed
|
|
869
|
+
|
|
870
|
+
- **A disabled field is no longer announced as invalid.** Every field bound `aria-invalid` from its
|
|
871
|
+
error state alone, so a control that was disabled AND carried an error told a screen reader
|
|
872
|
+
"invalid" about something the reader cannot act on. Nothing on screen changed — the error paint
|
|
873
|
+
already excluded disabled — which is why it went unseen.
|
|
874
|
+
|
|
875
|
+
The belief that a natively disabled control made the attribute inert is wrong, and that is what
|
|
876
|
+
kept the defect narrow in the record: measured in Chrome's accessibility tree, a disabled
|
|
877
|
+
`<input aria-invalid="true">` reports `invalid=true` and is NOT ignored. Disabling removes an
|
|
878
|
+
element from the tab order, not from the tree. So this reached all fifteen fields, not the two
|
|
879
|
+
first reported.
|
|
880
|
+
|
|
881
|
+
The rule lives in one place — the shared message resolver — rather than in fifteen templates: a
|
|
882
|
+
disabled control is neither submitted nor validated, the same reasoning `_field-state.scss`
|
|
883
|
+
already uses to keep the error paint off it. The message TEXT still shows: a refused field may
|
|
884
|
+
still need to say why.
|
|
885
|
+
|
|
886
|
+
### What you can now DELETE
|
|
887
|
+
|
|
888
|
+
| your workaround | why it is unnecessary | replace with |
|
|
889
|
+
| --- | --- | --- |
|
|
890
|
+
| `class="btn` — a hand-written button class kept only for controls that need `fragment`, `queryParams`, `target` or `rel` | those reach `ds-button` now, so the control can move with the rest | `ds-button` with the matching input |
|
|
891
|
+
| `[routerLink]="'/path?a=1#b'"` — a query or hash folded into the link string | the string was percent-encoded into the path and never worked; the inputs carry them properly | `[queryParams]` and `fragment` |
|
|
892
|
+
| importing `RouterLink` in your own component to write `[queryParams]` on a `<ds-button>` | that put a second `RouterLink` on the host, disagreeing with the anchor's about the destination | the component's own inputs |
|
|
893
|
+
| `ds-stat { --ds-stat-value-white-space: normal; }` written only to stop a long value painting over the tile beside it | the value clips by default, so it no longer escapes its card | nothing — keep the hook only where you want the value wrapped and the tile taller |
|
|
894
|
+
| `ds-stat .value { overflow: hidden; text-overflow: ellipsis; }` — your own clip on the value | the component clips it, and with `overflow: clip` plus a clip margin, so descenders survive where `hidden` shaved them | nothing |
|
|
895
|
+
| `.cell-text-pop` — a rule sizing or colouring the table's full-value popover | the popover is gone; a clipped cell opens a tooltip instead | `--ds-tooltip-*`, if the panel needs changing at all |
|
|
896
|
+
| `--ds-chart-axis-title-color` | no chart draws an axis title, so the token reached no rule and setting it changed nothing | nothing |
|
|
897
|
+
| `--ds-chart-grid-line-strong-color` | no chart draws a strong gridline, so the token reached no rule | nothing |
|
|
898
|
+
| `--ds-chart-tick-size` | no chart draws tick marks on its axes, so the token reached no rule | nothing |
|
|
10
899
|
|
|
11
900
|
## 0.12.3 — 2026-09-10
|
|
12
901
|
|