@ids-group-ltd/ids-design-system 0.13.0 → 0.13.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 +656 -3
- package/components.md +32 -11
- package/docs/agent/INDEX.md +2 -0
- package/docs/agent/charts/ds-bar-chart.md +1 -1
- package/docs/agent/charts/ds-column-chart.md +1 -1
- package/docs/agent/charts/ds-config.md +12 -0
- package/docs/agent/charts/ds-donut-chart.md +2 -2
- package/docs/agent/charts/ds-funnel-chart.md +1 -1
- package/docs/agent/charts/ds-line-chart.md +3 -2
- package/docs/agent/feedback/ds-meter.md +11 -0
- package/docs/agent/feedback/ds-progress.md +4 -1
- package/docs/agent/forms/ds-button.md +1 -1
- package/docs/agent/forms/ds-icon-button.md +1 -1
- package/docs/agent/surfaces/ds-card.md +1 -1
- 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 +9 -4
- package/fesm2022/ids-group-ltd-ids-design-system-components-autocomplete.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 +100 -15
- package/fesm2022/ids-group-ltd-ids-design-system-components-bar-chart.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-button.mjs +3 -0
- 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 +47 -5
- package/fesm2022/ids-group-ltd-ids-design-system-components-chart-legend.mjs.map +1 -1
- package/fesm2022/ids-group-ltd-ids-design-system-components-chart-tooltip.mjs +155 -21
- package/fesm2022/ids-group-ltd-ids-design-system-components-chart-tooltip.mjs.map +1 -1
- package/fesm2022/ids-group-ltd-ids-design-system-components-color-picker.mjs +9 -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 +81 -18
- package/fesm2022/ids-group-ltd-ids-design-system-components-column-chart.mjs.map +1 -1
- package/fesm2022/ids-group-ltd-ids-design-system-components-date-picker.mjs +9 -4
- 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 +75 -23
- package/fesm2022/ids-group-ltd-ids-design-system-components-donut-chart.mjs.map +1 -1
- 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-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-funnel-chart.mjs +107 -19
- package/fesm2022/ids-group-ltd-ids-design-system-components-funnel-chart.mjs.map +1 -1
- package/fesm2022/ids-group-ltd-ids-design-system-components-line-chart.mjs +236 -31
- package/fesm2022/ids-group-ltd-ids-design-system-components-line-chart.mjs.map +1 -1
- 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-meter.mjs +61 -0
- package/fesm2022/ids-group-ltd-ids-design-system-components-meter.mjs.map +1 -0
- package/fesm2022/ids-group-ltd-ids-design-system-components-modal.mjs +4 -4
- 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 +9 -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-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 +1 -1
- package/fesm2022/ids-group-ltd-ids-design-system-components-pagination.mjs.map +1 -1
- package/fesm2022/ids-group-ltd-ids-design-system-components-progress.mjs +34 -10
- package/fesm2022/ids-group-ltd-ids-design-system-components-progress.mjs.map +1 -1
- package/fesm2022/ids-group-ltd-ids-design-system-components-select.mjs +9 -4
- package/fesm2022/ids-group-ltd-ids-design-system-components-select.mjs.map +1 -1
- package/fesm2022/ids-group-ltd-ids-design-system-components-table.mjs +2 -2
- package/fesm2022/ids-group-ltd-ids-design-system-components-table.mjs.map +1 -1
- package/fesm2022/ids-group-ltd-ids-design-system-components-time-picker.mjs +9 -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.mjs +119 -13
- package/fesm2022/ids-group-ltd-ids-design-system-components.mjs.map +1 -1
- package/fesm2022/ids-group-ltd-ids-design-system-core.mjs.map +1 -1
- package/fesm2022/ids-group-ltd-ids-design-system.mjs +1 -0
- package/fesm2022/ids-group-ltd-ids-design-system.mjs.map +1 -1
- package/migrations/0.13.1.json +236 -0
- package/migrations/0.13.2.json +269 -0
- package/package.json +9 -1
- package/styles/_chart-frame.scss +116 -4
- package/styles/_chart-interactive.scss +27 -7
- package/styles/_chart-motion.scss +61 -18
- package/styles/_dropdown-overlay.scss +9 -3
- package/styles/_focus.scss +10 -1
- package/styles/_overlay-motion.scss +11 -1
- package/styles/_tokens-charts.scss +5 -0
- package/types/ids-group-ltd-ids-design-system-components-autocomplete.d.ts +6 -1
- package/types/ids-group-ltd-ids-design-system-components-bar-chart.d.ts +87 -10
- package/types/ids-group-ltd-ids-design-system-components-button.d.ts +1 -0
- package/types/ids-group-ltd-ids-design-system-components-chart-legend.d.ts +25 -2
- package/types/ids-group-ltd-ids-design-system-components-chart-tooltip.d.ts +23 -3
- 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 +60 -9
- package/types/ids-group-ltd-ids-design-system-components-date-picker.d.ts +6 -1
- package/types/ids-group-ltd-ids-design-system-components-donut-chart.d.ts +53 -13
- package/types/ids-group-ltd-ids-design-system-components-funnel-chart.d.ts +73 -11
- package/types/ids-group-ltd-ids-design-system-components-line-chart.d.ts +116 -12
- package/types/ids-group-ltd-ids-design-system-components-meter.d.ts +36 -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-progress.d.ts +21 -3
- package/types/ids-group-ltd-ids-design-system-components-select.d.ts +6 -1
- package/types/ids-group-ltd-ids-design-system-components-time-picker.d.ts +6 -1
- package/types/ids-group-ltd-ids-design-system-components.d.ts +47 -5
- package/types/ids-group-ltd-ids-design-system-core.d.ts +40 -1
- package/types/ids-group-ltd-ids-design-system.d.ts +6 -5
package/CHANGELOG.md
CHANGED
|
@@ -1,5 +1,657 @@
|
|
|
1
1
|
## Unreleased
|
|
2
2
|
|
|
3
|
+
## 0.13.2 — 2026-09-15
|
|
4
|
+
|
|
5
|
+
### Added
|
|
6
|
+
|
|
7
|
+
- **`ds-line-chart` takes `annotations`, so a reading can be labelled without a pointer.** The
|
|
8
|
+
chart had tooltips and nothing else, which leaves a peak unreadable in a screenshot, a printed
|
|
9
|
+
page or a slide. An annotation names a `categoryIndex`, a `label` and optionally the `seriesId`
|
|
10
|
+
it belongs to — left out, the first plotted series.
|
|
11
|
+
|
|
12
|
+
```html
|
|
13
|
+
<ds-line-chart
|
|
14
|
+
[categories]="months"
|
|
15
|
+
[series]="series"
|
|
16
|
+
[annotations]="[{ categoryIndex: 5, label: 'Peak' }]" />
|
|
17
|
+
```
|
|
18
|
+
|
|
19
|
+
It sits above the reading, below it where the plot has no room — a peak is at the top, which is
|
|
20
|
+
exactly where a label clamped upward lands on its own marker — and anchors to its own edge within
|
|
21
|
+
48 view units of one rather than hanging outside the viewBox. A label whose series is hidden or
|
|
22
|
+
whose reading is `null` draws nothing, so a legend toggle takes its annotations with it.
|
|
23
|
+
|
|
24
|
+
It is drawn with a halo rather than a box (`paint-order: stroke`), so it survives crossing the
|
|
25
|
+
line and a gridline; `--ds-line-chart-annotation-color`, `-font-size`, `-weight`, `-halo-color`
|
|
26
|
+
and `-halo-width` set its look. The plot's own text is `aria-hidden`, so the labels are read out
|
|
27
|
+
of the chart's description instead — `Noted: Peak; Launch.` after the series sentences — rather
|
|
28
|
+
than twice from the plot and the annex table.
|
|
29
|
+
|
|
30
|
+
- **`ds-progress` takes a `target`, drawn as a hairline across the track.** A second point on the
|
|
31
|
+
same 0–100 scale, so a bar reads actual against a goal or a baseline in one glance instead of
|
|
32
|
+
standing alone. Clamped like `value`, ignored while `indeterminate`, and unset draws nothing —
|
|
33
|
+
every existing bar is unchanged.
|
|
34
|
+
|
|
35
|
+
```html
|
|
36
|
+
<ds-progress
|
|
37
|
+
[value]="62"
|
|
38
|
+
[target]="75"
|
|
39
|
+
ariaLabel="Resolved 62% against a 75% target" />
|
|
40
|
+
```
|
|
41
|
+
|
|
42
|
+
**Name the comparison in `ariaLabel`.** `role="progressbar"` announces one value and has no second
|
|
43
|
+
to carry, so the mark is visual only — a reader on a screen reader gets the target from the label
|
|
44
|
+
or not at all. `--ds-progress-target-color` and `--ds-progress-target-width` set its look.
|
|
45
|
+
|
|
46
|
+
- **`ds-progress` takes a `max`, so `value` can be the real count.** The bar read 0–100 only and
|
|
47
|
+
pinned `aria-valuemax="100"`, which made a caller convert their own numbers before us and put the
|
|
48
|
+
percentage into the accessible name in place of the measurement. `max` is the scale `value` and
|
|
49
|
+
`target` are read against; at its default of 100 they are percentages, so every existing bar is
|
|
50
|
+
unchanged, and `aria-valuemax` follows it.
|
|
51
|
+
|
|
52
|
+
```html
|
|
53
|
+
<ds-progress [value]="37" [max]="80" [target]="64" ariaLabel="Requests handled" />
|
|
54
|
+
```
|
|
55
|
+
|
|
56
|
+
That bar fills to 46.25% and reports `aria-valuenow="37"` of `aria-valuemax="80"` — "37 of 80"
|
|
57
|
+
rather than "46%". A `max` of zero or less falls back to 100, because a scale with no width has no
|
|
58
|
+
fraction to draw.
|
|
59
|
+
|
|
60
|
+
`ProgressComponent` grows by the `target` and `max` inputs; a subclass declaring either name stops
|
|
61
|
+
building until it renames the member or marks it `override`.
|
|
62
|
+
|
|
63
|
+
- **`ds-bar-chart` and `ds-column-chart` take `partOfWhole`, and it is what states each mark's share
|
|
64
|
+
of the total.** A share of a total is only a real quantity when the marks are parts of one whole.
|
|
65
|
+
Visitors per funnel stage, or response time per endpoint, sum to a number nobody can point at, and
|
|
66
|
+
a percentage of THAT is arithmetic dressed as a fact — so the charts no longer state one unless
|
|
67
|
+
you say the relationship holds:
|
|
68
|
+
|
|
69
|
+
```html
|
|
70
|
+
<ds-bar-chart partOfWhole caption="Spend by department, share of the budget" [data]="rows" />
|
|
71
|
+
```
|
|
72
|
+
|
|
73
|
+
With it set, the share appears in two places: the tooltip's second line, and a `Share of total`
|
|
74
|
+
column in the data table. The column is headed `Share of total` rather than `Share` because
|
|
75
|
+
`ds-bar-chart` already prints a percentage beside each row and that one is the share of the
|
|
76
|
+
LARGEST row — two different questions, each now labelled with the one it answers.
|
|
77
|
+
|
|
78
|
+
The cell is empty where there is no share to state: a lone mark, or a reading that is zero,
|
|
79
|
+
negative or non-finite. Negatives are left out of the total rather than subtracted from it.
|
|
80
|
+
|
|
81
|
+
- **Every chart takes `pinOnClick`, which holds a reading in place.** Clicking a mark keeps it, its
|
|
82
|
+
tooltip and — with `dimOthers` — the dimming of everything else, so the comparison survives the
|
|
83
|
+
pointer leaving the chart entirely. Hovering another mark does not move it; clicking another one
|
|
84
|
+
does. Clicking the pinned mark again, pressing outside it, or Escape releases it. Off by default:
|
|
85
|
+
a click is already the drill-down hook, and a mark left lit after the pointer has gone needs a
|
|
86
|
+
reader who knows why it is lit.
|
|
87
|
+
|
|
88
|
+
```html
|
|
89
|
+
<ds-column-chart interactive pinOnClick dimOthers [data]="points" />
|
|
90
|
+
```
|
|
91
|
+
|
|
92
|
+
A pinned mark carries a pushpin on an opaque disc — over the row's bar, the column, the middle of
|
|
93
|
+
the ring's arc, the middle of the funnel band — because the panel can sit anywhere on screen and
|
|
94
|
+
the reader needs to see WHICH mark is held. An `Unpin` button appears centred above the plot while
|
|
95
|
+
anything is pinned, so the way out is on screen rather than a key nobody was told about, and it is
|
|
96
|
+
centred because a corner competes with the donut's legend and the column chart's value labels.
|
|
97
|
+
|
|
98
|
+
The click output fires either way — pinning is a state, not a handler. On `ds-line-chart` the pin
|
|
99
|
+
hangs off the data markers rather than the plot, so Enter and Space pin from the keyboard too.
|
|
100
|
+
|
|
101
|
+
- **`ds-meter` — one track and one fill, for a measurement inside a table cell.** Every chart is a
|
|
102
|
+
block with a caption, a legend and an annex table; in a 60px cell that chrome is the whole cell,
|
|
103
|
+
so a micro-bar in a column had nothing to be built from. This is the mark on its own — no
|
|
104
|
+
caption, no legend, no tooltip, no table.
|
|
105
|
+
|
|
106
|
+
```html
|
|
107
|
+
<ds-meter [value]="row.rate" [max]="highestRate" />
|
|
108
|
+
```
|
|
109
|
+
|
|
110
|
+
`max` is the ceiling the column is read against, usually the column's own largest value, so the
|
|
111
|
+
longest bar fills its track and the rest are its share; at its default of 100, `value` is a
|
|
112
|
+
percentage. A value past `max` fills the track rather than overflowing, a negative one draws
|
|
113
|
+
nothing, and a `max` of zero or less falls back to 100.
|
|
114
|
+
|
|
115
|
+
**It is not `ds-progress`.** That reports how far a task has got and says so with
|
|
116
|
+
`role="progressbar"`, which a table of two hundred measurements would announce two hundred times.
|
|
117
|
+
A rate, a score or a count against a ceiling has no beginning and no completion. So the mark is
|
|
118
|
+
`aria-hidden` unless `ariaLabel` names it — leave it unset where the cell prints the figure
|
|
119
|
+
beside the bar, and set it where the bar is the only place the number appears.
|
|
120
|
+
|
|
121
|
+
The fill takes `--ds-meter-fill-color`, so a column is coloured once in a stylesheet rather than
|
|
122
|
+
once per row; the `color` input overrides it where the colour carries meaning.
|
|
123
|
+
`--ds-meter-height`, `--ds-meter-track-color` and `--ds-meter-radius` set the rest.
|
|
124
|
+
|
|
125
|
+
The bar is as wide as the box it sits in, so the column decides. A box sized to its content —
|
|
126
|
+
`width: 'content'` on `ds-table`, or a shrink-to-fit flex or grid item — is sized by what its
|
|
127
|
+
contents contribute intrinsically, and a bar that is 100% of its cell contributes nothing: one
|
|
128
|
+
alone in such a cell comes out 0px wide. The host carries a `min-inline-size` of `3rem` so it
|
|
129
|
+
cannot vanish, overridable through `--ds-meter-min-width`; give it a width of your own where the
|
|
130
|
+
bar should be a fixed size.
|
|
131
|
+
|
|
132
|
+
- **A `ds-bar-chart` row takes `segments`, which divide its bar without shortening it.** A row that
|
|
133
|
+
is a distribution had to become its own chart. The bar keeps its own length — the row's share of
|
|
134
|
+
the largest row — and the parts say what it is made of, so one plot answers both "which department
|
|
135
|
+
spends most" and "on what".
|
|
136
|
+
|
|
137
|
+
```html
|
|
138
|
+
<ds-bar-chart [data]="[{ label: 'Engineering', value: 412000, segments: [
|
|
139
|
+
{ label: 'Salaries', value: 291000 },
|
|
140
|
+
{ label: 'Tooling', value: 74000 },
|
|
141
|
+
] }]" />
|
|
142
|
+
```
|
|
143
|
+
|
|
144
|
+
The parts are sized against their OWN sum and always fill the bar: a set that does not add up to
|
|
145
|
+
`value` is a data error, and a gap left where the difference is would read as an unlabelled
|
|
146
|
+
category. They are categories rather than one series, so they take the categorical palette in
|
|
147
|
+
order and the row's `color` goes unused; `color` on a segment overrides its slot. Each part gets
|
|
148
|
+
its own row in the annex table under the row it belongs to. Pair the chart with `ds-chart-legend`
|
|
149
|
+
to name them — the parts carry no text of their own.
|
|
150
|
+
|
|
151
|
+
- **A `ds-bar-chart` row takes `detail`, a second reading printed under the label.** A row often
|
|
152
|
+
encodes a ratio — 12,400 visitors against 456 requests — and the bar can draw only one of the two
|
|
153
|
+
numbers, so the other had nowhere to go. It is passed already formatted, because the row knows
|
|
154
|
+
what its second number means and the chart does not, and it reaches the annex table too.
|
|
155
|
+
|
|
156
|
+
```html
|
|
157
|
+
<ds-bar-chart [data]="[{ label: 'Organic', value: 12400, detail: '456 requests · 3.7%' }]" />
|
|
158
|
+
```
|
|
159
|
+
|
|
160
|
+
- **`ds-line-chart` takes `max` and `maxSecondary`, which pin the value axis.** A panel that opens
|
|
161
|
+
one subject at a time derived a different axis for each, so two plots with the same gentle wiggle
|
|
162
|
+
could be four times apart in value with nothing on screen saying so. A fixed maximum is what makes
|
|
163
|
+
two renders comparable.
|
|
164
|
+
|
|
165
|
+
```html
|
|
166
|
+
<ds-line-chart [max]="5000" [categories]="months" [series]="series" />
|
|
167
|
+
```
|
|
168
|
+
|
|
169
|
+
Null, the default, keeps the derived axis, so every existing chart is unchanged. A maximum below
|
|
170
|
+
the data does not clip it — the larger of the two wins, because hiding a reading is worse than
|
|
171
|
+
more headroom than you asked for. `maxSecondary` does the same for the axis a series reaches with
|
|
172
|
+
`axis: 'secondary'`.
|
|
173
|
+
|
|
174
|
+
- **`ds-funnel-chart` takes `drop`, which says what its Drop column reports.** `'relative'`, the
|
|
175
|
+
default, is the share that leaked at that stage and is what the column always showed;
|
|
176
|
+
`'absolute'` is the COUNT that leaked, and `'none'` takes the column out. Both figures answer a
|
|
177
|
+
real question and they are not the same question: on a settlement funnel the share is a talking
|
|
178
|
+
point and the count is a re-targeting job. The count was recoverable by subtracting two rows, and
|
|
179
|
+
a reader should not have to.
|
|
180
|
+
|
|
181
|
+
```html
|
|
182
|
+
<ds-funnel-chart drop="absolute" [stages]="stages" />
|
|
183
|
+
```
|
|
184
|
+
|
|
185
|
+
- **Every chart takes `tooltipLingerMs`, and `DS_CONFIG.chart.tooltipLingerMs` sets it app-wide.**
|
|
186
|
+
How long the panel stays after the pointer leaves the mark. See the tooltip entry under Changed
|
|
187
|
+
for what the default does and when to raise it.
|
|
188
|
+
|
|
189
|
+
- **A pinned mark offers an `Unpin` control, and says which mark it is.** `ds-bar-chart`,
|
|
190
|
+
`ds-column-chart`, `ds-donut-chart` and `ds-funnel-chart` render a pill button above the plot
|
|
191
|
+
while a mark is pinned — Escape already released one, and a control that says so is what a reader
|
|
192
|
+
finds without knowing the key. `ds-donut-chart` and `ds-funnel-chart` also draw a pin glyph at the
|
|
193
|
+
pinned slice's or band's centre, so the plot itself carries which one is held rather than leaving
|
|
194
|
+
it to the panel; the glyph takes no pointer events. `--ds-chart-pin-size` sizes it, and the button
|
|
195
|
+
is `.pin-reset`.
|
|
196
|
+
|
|
197
|
+
The internal mark-state interface behind it — not exported from the package root — gains a
|
|
198
|
+
`release()`, and its factory implements it. Only a hand-written implementation of that interface
|
|
199
|
+
has one more method to satisfy.
|
|
200
|
+
|
|
201
|
+
- **A toggleable legend in `isolate` mode offers `None`.** Beside `All` and the per-series controls,
|
|
202
|
+
which left no way to clear the plot in one action.
|
|
203
|
+
|
|
204
|
+
### Changed
|
|
205
|
+
|
|
206
|
+
- **Turning a chart's frame off is an input now, not a stylesheet rule.** The frame still draws by
|
|
207
|
+
default. Switching it off took `ds-bar-chart { --ds-chart-frame-border-width: 0;
|
|
208
|
+
--ds-chart-frame-padding: 0 }` in a global sheet — a deep rule into a component's own chrome,
|
|
209
|
+
which is the shape of styling the rest of the library has been turning into inputs and tokens.
|
|
210
|
+
|
|
211
|
+
`frame` takes `'auto'` (the default, draws it) or `'none'`, and falls back to
|
|
212
|
+
`DS_CONFIG.chart.frame` when unset — whether charts live inside cards is one decision per app,
|
|
213
|
+
the same as `dataTable`:
|
|
214
|
+
|
|
215
|
+
```ts
|
|
216
|
+
provideDsConfig({ chart: { frame: 'none' } });
|
|
217
|
+
```
|
|
218
|
+
|
|
219
|
+
```html
|
|
220
|
+
<ds-donut-chart frame="none" [data]="slices" />
|
|
221
|
+
```
|
|
222
|
+
|
|
223
|
+
The two custom properties still size the frame and still work; a stylesheet zeroing them can drop
|
|
224
|
+
those declarations in favour of the config key. `ChartFrame` is exported from the package root.
|
|
225
|
+
|
|
226
|
+
- **The annex data table is off by default.** `dataTable` defaults to `'none'` rather than
|
|
227
|
+
`'toggle'`, on all five charts and in `DS_CONFIG.chart.dataTable`. A disclosure under every plot
|
|
228
|
+
is chrome the page did not ask for, and the page usually carries the numbers already.
|
|
229
|
+
|
|
230
|
+
It stays the non-visual route to the numbers where a page does NOT carry them, so turn it on
|
|
231
|
+
deliberately — per chart with `dataTable="toggle"`, or once for an app:
|
|
232
|
+
|
|
233
|
+
```ts
|
|
234
|
+
provideDsConfig({ chart: { dataTable: 'toggle' } });
|
|
235
|
+
```
|
|
236
|
+
|
|
237
|
+
- **A legend control isolates a series rather than hiding one, and `ds-chart-legend` says which.**
|
|
238
|
+
`mode` is `'isolate'` by default: choosing a series shows that one and hides the rest, which takes
|
|
239
|
+
one action instead of one per series on a crowded chart. `mode="toggle"` is the old behaviour —
|
|
240
|
+
hide one, leave the rest — for taking a dominant series out so the others can be read at a usable
|
|
241
|
+
scale. `ds-line-chart` forwards it as `legendMode`.
|
|
242
|
+
|
|
243
|
+
The two are different controls, not two looks: isolate is a single choice among many, so it
|
|
244
|
+
renders as a radio group running `All`, each series, `None`, and toggle renders as the checkboxes
|
|
245
|
+
it already did. That is what gives each the keyboard and screen-reader behaviour it should have.
|
|
246
|
+
One option is always chosen — `All` where the set is neither one series nor empty — because a
|
|
247
|
+
radio group with nothing selected cannot say whether it means "everything" or "not decided".
|
|
248
|
+
|
|
249
|
+
**If you set `legendFilters` on `ds-line-chart`, its legend changes shape.** Add
|
|
250
|
+
`legendMode="toggle"` to keep the checkboxes. `hiddenSeries` is unchanged in both modes, so a page
|
|
251
|
+
driving it from a URL parameter needs nothing.
|
|
252
|
+
|
|
253
|
+
- **A chart tooltip can be selected and dismissed with Escape, and reached with the pointer where
|
|
254
|
+
you ask for it.** The pane was inert and closed the instant the pointer left the mark, which left
|
|
255
|
+
it unreadable at high zoom, unselectable, and impossible to clear without moving the pointer away.
|
|
256
|
+
|
|
257
|
+
The pane takes the pointer now, and Escape closes the panel — it stays closed until the pointer
|
|
258
|
+
visits another mark, so a reader who clears the screen keeps it cleared. Reaching the panel is
|
|
259
|
+
`tooltipLingerMs`, which is `0`: the panel goes when the pointer does, because one left behind
|
|
260
|
+
sits over the plot the reader has moved on to. WCAG 1.4.13's hoverable clause only bites where the
|
|
261
|
+
panel holds something to reach — a link, a figure, a selectable string — so set
|
|
262
|
+
`[tooltipLingerMs]="140"` on those charts, or `DS_CONFIG.chart.tooltipLingerMs` for an app whose
|
|
263
|
+
tooltips all carry one. 140ms is what crossing the gap to a portaled panel takes at an ordinary
|
|
264
|
+
pointer speed.
|
|
265
|
+
|
|
266
|
+
If you styled `.ds-chart-tooltip-pane` with `pointer-events`, that rule now decides whether the
|
|
267
|
+
panel can be selected at all — the pane must stay `auto`.
|
|
268
|
+
|
|
269
|
+
- **A chart tooltip's second line is opt-in.** `0.13.1` gave every `ds-bar-chart` and
|
|
270
|
+
`ds-column-chart` tooltip a `18.6% of total` line whether or not the marks were parts of a whole.
|
|
271
|
+
It appears only under `partOfWhole` now. Set it on any chart whose categories genuinely divide one
|
|
272
|
+
total to keep the line; leave it off and the tooltip carries the label and the value, as before
|
|
273
|
+
`0.13.1`.
|
|
274
|
+
|
|
275
|
+
- **Exported class member surface grew — only matters if you SUBCLASS one of these.** `BarChartComponent`,
|
|
276
|
+
`ColumnChartComponent`, `DonutChartComponent`, `FunnelChartComponent` and `LineChartComponent` all
|
|
277
|
+
gain `pinOnClick` and the protected `onMarkClick`, which `LineChartComponent` spells
|
|
278
|
+
`onMarkerClick` beside its own `pinnedCategory` and `releaseCategoryPin`; `BarChartComponent` and
|
|
279
|
+
`ColumnChartComponent` also gain `partOfWhole` and the protected `valueClearance`; all five gain
|
|
280
|
+
`frame` and `frameResolved`; `LineChartComponent` gains `legendMode`; the
|
|
281
|
+
internal `ChartLegendComponent`, which the package root does not export, gains `mode`, `isolated`,
|
|
282
|
+
`isolate` and `showAll`; and the internal `ChartTooltipDirective`, also unexported there, gains
|
|
283
|
+
`dsChartTooltipExtraGap` and the private `detachEscape` and `closeOnEscape`.
|
|
284
|
+
|
|
285
|
+
All five also gain `tooltipLingerMs` and the private `tooltipLingerResolved`; `FunnelChartComponent`
|
|
286
|
+
gains `drop` and the protected `pinnedCenter`; `LineChartComponent` gains `max`, `maxSecondary`,
|
|
287
|
+
`annotations`, `placedAnnotations` and the protected `onPointerAnywhere`, `host`,
|
|
288
|
+
`cancelCategoryClear` and `pendingCategoryClear`; the internal legend also gains `groupName` and
|
|
289
|
+
`hideAll`.
|
|
290
|
+
|
|
291
|
+
Outside the charts: `ProgressComponent` gains `target`, `max` and the protected `scale`,
|
|
292
|
+
`clampedTarget`, `targetPercent` and `valuePercent`, and the internal message base the fields and
|
|
293
|
+
the button extend — unexported from the package root — gains a protected
|
|
294
|
+
`reserveFollowsFieldDefault`.
|
|
295
|
+
|
|
296
|
+
A subclass declaring any of those names collides. For a public or protected member the fix is
|
|
297
|
+
`override` or a rename; for a private one only a rename works, because TS2415 fires on the name
|
|
298
|
+
and `override` does not clear it.
|
|
299
|
+
|
|
300
|
+
### Fixed
|
|
301
|
+
|
|
302
|
+
- **`ds-line-chart` draws from axis to axis.** Its readings sat at the centre of a slot each, which
|
|
303
|
+
left an empty strip of plot against the value axis and another against the far edge — a gap that
|
|
304
|
+
reads as data the chart is withholding. The first reading is on the value axis now and the last
|
|
305
|
+
at the far edge, with the rest dividing the run evenly. The crosshair band is centred on its
|
|
306
|
+
reading and clamped at both ends, so the first and last are half-width and neither hangs over an
|
|
307
|
+
axis label.
|
|
308
|
+
|
|
309
|
+
- **A drag across a chart no longer selects its chrome.** Axis ticks, legend labels and the caption
|
|
310
|
+
a screen reader needs — clipped to a thin strip for everyone else — all came out selected, and the
|
|
311
|
+
selection painted as bars across the card over content that is not visibly there. The plot is
|
|
312
|
+
`user-select: none` now; the annex table, the funnel's stage table and the visible caption stay
|
|
313
|
+
selectable, because those carry numbers people copy.
|
|
314
|
+
|
|
315
|
+
- **Clicking a slice or a band no longer draws a rectangle around it.** Chromium focuses an SVG
|
|
316
|
+
shape when it is clicked even with no `tabindex` on it, and reports that focus as NOT
|
|
317
|
+
`:focus-visible` — so a rule keyed on `:focus-visible` never fired and the browser painted its
|
|
318
|
+
own outline instead. On a ring arc or a funnel band an outline is the BOUNDING BOX, which stood
|
|
319
|
+
off the shape and read as a selection nobody asked for. `ds-donut-chart`, `ds-funnel-chart` and
|
|
320
|
+
`ds-line-chart` marks now suppress it on `:focus`. The keyboard indicator is untouched: it is a
|
|
321
|
+
stroke that follows the silhouette, and it still paints under `:focus-visible`.
|
|
322
|
+
|
|
323
|
+
- **`ds-column-chart`'s tooltip clears the value printed above the column.** The panel is anchored
|
|
324
|
+
to the column and opened 12px above it, which is exactly where `showValues` prints the figure,
|
|
325
|
+
so the two overlapped. It now clears the text as well as the mark; with `showValues` off the gap
|
|
326
|
+
is unchanged.
|
|
327
|
+
|
|
328
|
+
- **`ds-button` ignores the app-wide `DS_CONFIG.field.reserveMessage`.** The button takes the same
|
|
329
|
+
message line a field does, and with it took the field-wide default: an app calling
|
|
330
|
+
`provideDsConfig({ field: { reserveMessage: true } })` gave EVERY button an empty message row,
|
|
331
|
+
which turns the host from `inline-flex` into a column with a gap. One app found 125 buttons
|
|
332
|
+
across 45 files changed box that way, and nothing in the build, the types or the release notes
|
|
333
|
+
reported it. `reserveMessage` exists so a field row does not shift its neighbours as a message
|
|
334
|
+
appears, and a button is not in that column.
|
|
335
|
+
|
|
336
|
+
A button reserves only where you ask it to, with `[reserveMessage]="true"`. Fields are unchanged:
|
|
337
|
+
`DS_CONFIG.field.reserveMessage` still reaches every one of them, `ds-field-group` included.
|
|
338
|
+
|
|
339
|
+
The decision lives on the internal `DsMessageBase`, the shared message base the fields and the
|
|
340
|
+
button extend, as a protected `reserveFollowsFieldDefault`. The package root does not export it; a
|
|
341
|
+
subclass reaching it through the deep entry point and declaring that name stops building until it
|
|
342
|
+
renames the member or marks it `override`.
|
|
343
|
+
|
|
344
|
+
- **Two legends on one page no longer fight over the same selection.** A legend's isolate controls
|
|
345
|
+
are radios, and every legend named the same group — so a page with more than one chart formed a
|
|
346
|
+
single document-wide group: choosing a series in one legend cleared the selection in the others,
|
|
347
|
+
and only the last-rendered legend showed one at all. Each legend now names its own group.
|
|
348
|
+
|
|
349
|
+
A legend also always shows exactly one control chosen. A leftover partial state left the group
|
|
350
|
+
with nothing checked; it settles on `All`.
|
|
351
|
+
|
|
352
|
+
- **`ds-line-chart` holds its height when the last series is switched off.** The empty message
|
|
353
|
+
reserved the plot-height token alone, and the plot is an SVG sized by its ratio against the card
|
|
354
|
+
width — so on any card wider than that token the message box came up short and the card jumped.
|
|
355
|
+
It reserves the canvas ratio now, with the token as the floor for a very narrow card.
|
|
356
|
+
|
|
357
|
+
### What you can now DELETE
|
|
358
|
+
|
|
359
|
+
| your workaround | why it is unnecessary | replace with |
|
|
360
|
+
| --- | --- | --- |
|
|
361
|
+
| `--ds-chart-frame-border-width: 0` with `--ds-chart-frame-padding: 0`, written to strip the frame off a chart inside a card | the frame is an input and an app-wide config key, so reaching into the component's chrome is no longer the route | `frame="none"`, or `provideDsConfig({ chart: { frame: 'none' } })` |
|
|
362
|
+
| `dataTable="none"` on a chart | the annex table is off by default, so the binding restates it | nothing — keep it only where the app-wide default is `'toggle'` and this one chart differs |
|
|
363
|
+
|
|
364
|
+
## 0.13.1 — 2026-09-14
|
|
365
|
+
|
|
366
|
+
### Added
|
|
367
|
+
|
|
368
|
+
- **A picker's panel can be styled without painting every other picker's.** Each portaled pane
|
|
369
|
+
carries its own class beside the shared `ds-dropdown-panel` and `ds-overlay-pane` —
|
|
370
|
+
`ds-select-panel`, `ds-multi-select-panel`, `ds-autocomplete-panel`, `ds-color-picker-panel`,
|
|
371
|
+
`ds-date-picker-panel`, `ds-time-picker-panel` — and every one of the six also takes a
|
|
372
|
+
`panelClass` input for a class of your own:
|
|
373
|
+
|
|
374
|
+
```html
|
|
375
|
+
<ds-autocomplete panelClass="search-panel" [options]="options" />
|
|
376
|
+
```
|
|
377
|
+
|
|
378
|
+
```scss
|
|
379
|
+
.ds-autocomplete-panel .option { font-size: 15px; }
|
|
380
|
+
```
|
|
381
|
+
|
|
382
|
+
The panel is portaled to `document.body`, outside the host, so a class on the pane is the only
|
|
383
|
+
route a consumer stylesheet has to ONE instance of it. `panelClass` takes a string or an array.
|
|
384
|
+
|
|
385
|
+
Two panes gain `ds-dropdown-panel` that did not carry it: the date picker's and the time picker's.
|
|
386
|
+
Neither changes appearance, because neither renders any of the class names the skin styles — no
|
|
387
|
+
option rows, no option groups, no list. A rule of yours written against `.ds-dropdown-panel` now
|
|
388
|
+
matches them, though, and so do the panel's custom properties.
|
|
389
|
+
|
|
390
|
+
`SelectComponent`, `MultiSelectComponent`, `AutocompleteComponent`, `ColorPickerComponent`,
|
|
391
|
+
`DatePickerComponent` and `TimePickerComponent` each grow by this one input. A subclass of any of
|
|
392
|
+
the six that declares its own `panelClass` stops building until it renames the member or marks it
|
|
393
|
+
`override`.
|
|
394
|
+
|
|
395
|
+
- **The dropdown panel's border and shadow, and the option's type, read `--ds-*` hooks.**
|
|
396
|
+
`--ds-dropdown-panel-border-color` and `--ds-dropdown-panel-shadow` join the five box hooks the
|
|
397
|
+
panel already had; `--ds-option-weight`, `--ds-option-font-size`, `--ds-option-line-height` and
|
|
398
|
+
`--ds-option-font-family` fill the row's `font` shorthand, which carried four literal values. All
|
|
399
|
+
six forward per instance, like every other dropdown-panel hook: set one on a host and it reaches
|
|
400
|
+
that host's pane, with no global rule. Defaults are today's values, so an untouched theme is
|
|
401
|
+
unchanged.
|
|
402
|
+
|
|
403
|
+
- **`--ds-modal-title-font-family`.** The title had weight, size and colour hooks but read
|
|
404
|
+
`--font-heading` literally, so a display face had no route in that did not involve outspecifying
|
|
405
|
+
the component's own rule from outside its encapsulation. Defaults to `--font-heading`.
|
|
406
|
+
|
|
407
|
+
- **`DS_CONFIG` takes a `chart` section.** Four inputs now resolve through it, because each is one
|
|
408
|
+
decision per APP rather than per plot: `valueFormat` — a number reads one way in a product, and a
|
|
409
|
+
formatter passed per chart drifts as soon as there are two screens; `dataTable` — whether the
|
|
410
|
+
numbers behind a plot have a non-visual route is an accessibility policy, not a per-chart taste;
|
|
411
|
+
and `emptyText` / `errorText`, which is where localisation lands.
|
|
412
|
+
|
|
413
|
+
```ts
|
|
414
|
+
providers: [
|
|
415
|
+
provideDsConfig({
|
|
416
|
+
chart: {
|
|
417
|
+
valueFormat: (value) => value.toLocaleString('de-DE'),
|
|
418
|
+
dataTable: 'visible',
|
|
419
|
+
},
|
|
420
|
+
}),
|
|
421
|
+
];
|
|
422
|
+
```
|
|
423
|
+
|
|
424
|
+
Precedence is the input, then the config, then the built-in default, so binding one on a single
|
|
425
|
+
chart still wins. The four inputs are typed `T | null` and default to `null` — that is what lets
|
|
426
|
+
a chart tell "not set" from an explicit value — and each chart exposes the settled value as
|
|
427
|
+
`dataTableResolved`, `emptyTextResolved`, `errorTextResolved` and `valueFormatResolved`. A
|
|
428
|
+
subclass that read the raw input now reads `null` until something binds it.
|
|
429
|
+
|
|
430
|
+
`ChartDataTable` and `ChartValueFormat` are exported from the package root.
|
|
431
|
+
|
|
432
|
+
The member surface of `BarChartComponent`, `ColumnChartComponent`, `DonutChartComponent`,
|
|
433
|
+
`FunnelChartComponent` and `LineChartComponent` grows by these four readbacks and by `dimOthers`,
|
|
434
|
+
all public. `ColumnChartComponent` also gains `tooltipAnchor` and the protected `onMarkEnter`,
|
|
435
|
+
`FunnelChartComponent` the protected `hitGapUnits`, and `LineChartComponent` `tooltipAnchor`, the
|
|
436
|
+
protected `cursorBottomY` and the private `readingAnchor`. `DonutChartComponent` LOSES the
|
|
437
|
+
protected `markStagger`.
|
|
438
|
+
|
|
439
|
+
A subclass that declares any of those names collides. For a public or protected member the fix is
|
|
440
|
+
`override` or a rename; for a PRIVATE one — `readingAnchor` — only a rename works, because TS2415
|
|
441
|
+
fires on the name itself and `override` does not clear it. A subclass that called `markStagger` no
|
|
442
|
+
longer compiles.
|
|
443
|
+
|
|
444
|
+
- **The tooltip is pinned to the mark, not to the cursor, and both charts that had a say now take
|
|
445
|
+
an option.** `ds-line-chart` gains `tooltipAnchor`: `'point'`, the default, pins the panel over
|
|
446
|
+
the highest reading in the category, so it stays still while the pointer travels within one band;
|
|
447
|
+
`'pointer'` follows the cursor. `ds-column-chart` gains the same input with `'mark'` and `'cell'`:
|
|
448
|
+
the box catching the pointer is the full-height category cell, so `'cell'` opened the panel at the
|
|
449
|
+
top of the plot rather than over the column it described. `'mark'` is the default and points at
|
|
450
|
+
the column.
|
|
451
|
+
|
|
452
|
+
```html
|
|
453
|
+
<ds-line-chart tooltipAnchor="pointer" [series]="series" [categories]="months" />
|
|
454
|
+
<ds-column-chart tooltipAnchor="cell" [data]="points" />
|
|
455
|
+
```
|
|
456
|
+
|
|
457
|
+
The internal `ChartActiveMark`, which the package root does not export, takes an optional third
|
|
458
|
+
argument on `enter` to name the element inside the hit box that the panel points at. An
|
|
459
|
+
implementation that omits it still satisfies the interface.
|
|
460
|
+
|
|
461
|
+
### Changed
|
|
462
|
+
|
|
463
|
+
- **A surface no longer travels on its way in.** `ds-overlay-pane` — every picker panel, the
|
|
464
|
+
popover, the menu submenu, the tooltip, the chart tooltip — plus `ds-alert`, `ds-banner` and
|
|
465
|
+
`ds-toast` defaulted to
|
|
466
|
+
`ds-slide-in`, which offsets the panel and slides it to its place. They now default to
|
|
467
|
+
`ds-fade-in`: the same duration and easing, no travel. The travel read as the panel jumping into
|
|
468
|
+
position, and on a panel that opens UPWARD it read as jumping up from below the trigger.
|
|
469
|
+
|
|
470
|
+
`ds-drawer` and `ds-bottom-sheet` keep `ds-slide-edge-in`, because sliding in from an edge is
|
|
471
|
+
what they are, and `ds-modal` keeps `ds-scale-in`. Any surface takes its old entrance back with
|
|
472
|
+
one declaration:
|
|
473
|
+
|
|
474
|
+
```scss
|
|
475
|
+
:root { --ds-overlay-enter-keyframes: ds-slide-in; }
|
|
476
|
+
ds-toast { --ds-toast-enter-keyframes: ds-slide-in; }
|
|
477
|
+
```
|
|
478
|
+
|
|
479
|
+
- **A chart mark arrives by GROWING from its own baseline, not by scaling about its centre.** A
|
|
480
|
+
column grows up out of the category axis and a bar row grows out from the value axis; a ring arc,
|
|
481
|
+
a funnel band and a line have no baseline to grow from and fade instead. The uniform
|
|
482
|
+
`scale(0.94)` this replaces moved every mark's baseline and read as the whole chart zooming in.
|
|
483
|
+
|
|
484
|
+
- **The mark cap is 3px on `ds-bar-chart` and `ds-column-chart`,** through the new
|
|
485
|
+
`--ds-chart-mark-cap-radius`, with `--ds-bar-chart-cap-radius` and `--ds-column-chart-cap-radius`
|
|
486
|
+
over it. The bar's end was a full pill (half the track height) and the column's top was
|
|
487
|
+
`--radius-sm`; one soft value for both keeps the cap from reading as a change of shape while a
|
|
488
|
+
mark grows in.
|
|
489
|
+
|
|
490
|
+
- **A gap between two marks now belongs to the marks either side of it.** `ds-funnel-chart`'s
|
|
491
|
+
inter-stage gaps are claimed half by the band above and half by the band below, through a
|
|
492
|
+
transparent stroke — the gap looks exactly as it did and stops being dead space that answers
|
|
493
|
+
nothing. `ds-bar-chart`'s row gap moved from `row-gap` on the list to padding on each row, for
|
|
494
|
+
the same reason: a reader aiming between two bars used to hit neither. That last one makes the
|
|
495
|
+
bar plot one full `--ds-bar-chart-row-gap` taller — 20px at the default — because the first row
|
|
496
|
+
now carries half a gap above it and the last half a gap below.
|
|
497
|
+
|
|
498
|
+
- **A tooltip now says what the chart does not already print.** On `ds-bar-chart` and
|
|
499
|
+
`ds-column-chart` it repeated the label and the value that sit beside the mark, which told the
|
|
500
|
+
reader nothing they were not looking at. Both now carry a second line — the mark's share of the
|
|
501
|
+
total, `18.6% of total`, arithmetic the reader should not have to do — and `ds-funnel-chart`
|
|
502
|
+
carries the drop into the stage, which the shape cannot show. A mark whose value is zero or
|
|
503
|
+
negative has no share of anything visible and gets no second line at all. `ds-donut-chart` gets
|
|
504
|
+
none either: its panel and its legend both already print the percentage. A projected
|
|
505
|
+
`#dsChartTooltip` template still replaces the lot.
|
|
506
|
+
|
|
507
|
+
- **`ds-line-chart`'s crosshair moves as one object and fades on the way in and out.** The band and
|
|
508
|
+
the cursor line are one group carrying a `translateX`, so following the pointer is a single
|
|
509
|
+
transform rather than an attribute write per shape. It is not transitioned: the crosshair belongs
|
|
510
|
+
under the pointer, and easing it there makes it arrive late over readings it was never on.
|
|
511
|
+
|
|
512
|
+
- **`ds-line-chart`'s crosshair covers both plots under `yAxisMode="stacked"`.** It stopped at the
|
|
513
|
+
upper plot's baseline, so the lower plot — same category, same pointer — had nothing marked at
|
|
514
|
+
all.
|
|
515
|
+
|
|
516
|
+
- **`ds-donut-chart` fades as one ring rather than slice by slice.** Arcs share their edges, and
|
|
517
|
+
two semi-transparent shapes butting up along one let the background through the seam — which
|
|
518
|
+
reads as the slice proportions shifting slightly as the fade ends. Compositing the ring first and
|
|
519
|
+
fading the result cannot do that. `staggerMs` therefore has no effect on this chart — one object
|
|
520
|
+
arrives, not five — and the input stays only for parity with the other four.
|
|
521
|
+
|
|
522
|
+
- **A chart keeps its height in every state.** An empty `data`, a failed request, or a legend that
|
|
523
|
+
switched the last series off used to shrink the chart to a line of text, which drags the page up
|
|
524
|
+
under the reader at exactly the moment they are being told something. The message now stands in a
|
|
525
|
+
box the size of the plot it replaces, on all five. What sizes that box differs by chart:
|
|
526
|
+
`ds-column-chart` and `ds-line-chart` use their `--ds-*-plot-height`, `ds-donut-chart` its
|
|
527
|
+
`--ds-donut-chart-size`, and `ds-bar-chart` and `ds-funnel-chart` reserve three rows or stages,
|
|
528
|
+
so a chart that normally draws ten rows still shrinks to that reserve.
|
|
529
|
+
|
|
530
|
+
- **Dimming the other marks is a separate opt-in, and it is off.** `dimOthers` fades the marks that
|
|
531
|
+
are not singled out: on `ds-bar-chart`, `ds-column-chart`, `ds-donut-chart` and `ds-funnel-chart`
|
|
532
|
+
that is every mark but the hovered or focused one, and on `ds-line-chart` — which has no mark
|
|
533
|
+
between two readings to hover — it follows the legend's highlight. It used to ride along with
|
|
534
|
+
`interactive`, and it is off by default because the fade costs the separation BETWEEN the faded
|
|
535
|
+
marks: in OKLab dE ×100, the worst pair of three dimmed series falls from 14.8 at full opacity to
|
|
536
|
+
2.1 at `--ds-chart-dim-opacity`'s default. It buys loudness for one mark and pays for it with the
|
|
537
|
+
rest of the chart. A chart that had the fade gets it back with one attribute.
|
|
538
|
+
|
|
539
|
+
```html
|
|
540
|
+
<ds-donut-chart interactive dimOthers [data]="slices" />
|
|
541
|
+
```
|
|
542
|
+
|
|
543
|
+
- **A hidden legend row is no longer struck through.** The unchecked box says what happened and the
|
|
544
|
+
muted label agrees with it; a strike-through says the label itself is wrong.
|
|
545
|
+
|
|
546
|
+
- **A legend's colour chips arrive with the marks they name.** They used to be solid from the first
|
|
547
|
+
frame while the plot was still fading in, which reads as two objects rather than one. The chip
|
|
548
|
+
now fades on the same curve and the same delay: `ds-chart-legend`'s swatch and, where the legend
|
|
549
|
+
toggles, its checkbox; `ds-donut-chart`'s legend swatch; and `ds-funnel-chart`'s stage-table
|
|
550
|
+
swatch. Nothing in your code changes, and a screenshot test that captures a chart mid-entrance
|
|
551
|
+
will differ.
|
|
552
|
+
|
|
553
|
+
- **A `title` input no longer leaves a native browser tooltip over the component.** `title` is a
|
|
554
|
+
global HTML attribute, so `<ds-modal title="Settings">` both fed the input AND left the attribute
|
|
555
|
+
in the DOM — and the browser then raised its own tooltip over the whole component, naming it
|
|
556
|
+
rather than whatever the pointer was resting on. Eleven components drop the attribute:
|
|
557
|
+
`ds-accordion-item`, `ds-alert`, `ds-banner`, `ds-bottom-sheet`, `ds-drawer`, `ds-empty-state`,
|
|
558
|
+
`ds-list-item`, `ds-modal`, `ds-modal-card`, `ds-page-header` and `ds-toast`. Each renders the
|
|
559
|
+
title as visible text and names itself through `aria-labelledby` where it needs a name, so
|
|
560
|
+
nothing is lost to assistive technology.
|
|
561
|
+
|
|
562
|
+
This wins over a `[attr.title]` of your own on those hosts — bind it and the attribute is still
|
|
563
|
+
removed. If you want a native tooltip there, put it on a wrapper or a projected child, or use
|
|
564
|
+
`dsTooltip`.
|
|
565
|
+
|
|
566
|
+
- **A chart tooltip no longer fights the pointer that opened it.** The panel opens under the
|
|
567
|
+
cursor, and the CDK pane it is portaled into takes pointer events by default — so the panel
|
|
568
|
+
covered the plot, the plot took a `pointerleave`, the chart cleared its hover, the panel closed,
|
|
569
|
+
the pointer landed on the plot again, and the whole thing flickered for as long as the cursor sat
|
|
570
|
+
there. The pane is `pointer-events: none` now; `pointer-events` on the panel alone never reached
|
|
571
|
+
it.
|
|
572
|
+
|
|
573
|
+
- **`ds-column-chart` answers the pointer near its column, not across the whole category slot.** A
|
|
574
|
+
column is capped at `--ds-column-chart-column-max-width` while its slot is a `1fr` share of the
|
|
575
|
+
plot, so on a wide chart the hover reached well past the mark on either side. The target is
|
|
576
|
+
`--ds-column-chart-column-max-width` plus one `--ds-column-chart-column-gap` — half the gap each
|
|
577
|
+
side, the rule the funnel's bands already follow — and it spans the category cell's FULL height:
|
|
578
|
+
the plot, the axis gap under it, and the label. Split across the plot and the label alone, the
|
|
579
|
+
axis gap answered for neither, so a pointer travelling between them crossed a band where the
|
|
580
|
+
tooltip closed and reopened. It never exceeds the slot, and where the column is narrower than its
|
|
581
|
+
cap the target is wider than the column itself.
|
|
582
|
+
|
|
583
|
+
`.plot-cell` is no longer a positioned box and no longer carries the `::after` that catches the
|
|
584
|
+
pointer; `.column` is and does. A rule of yours that positioned something against `.plot-cell`
|
|
585
|
+
now resolves against `.column`.
|
|
586
|
+
|
|
587
|
+
- **The legend's checkboxes are not permanently ringed.** `ds-chart-legend` applied the focus ring
|
|
588
|
+
unconditionally instead of under `:focus-visible`, so every legend row looked focused. The
|
|
589
|
+
library's global `:where(:focus-visible)` rule already rings them, so the component needs none of
|
|
590
|
+
its own.
|
|
591
|
+
|
|
592
|
+
- **A mark's colour change eases instead of jumping,** and a dimmed line fades again. Each mark
|
|
593
|
+
animated exactly one property, because a second `transition` on the same selector REPLACES the
|
|
594
|
+
first rather than adding to it: `ds-line-chart`'s line kept `stroke-width` and lost the dim fade,
|
|
595
|
+
its marker kept `r` and lost the same, and no mark eased its paint at all. Opacity, geometry and
|
|
596
|
+
colour now travel in ONE declaration wherever they share a selector — so recolouring a row,
|
|
597
|
+
pinning a palette slot, or adding a funnel stage and re-spreading the ramp all ease. If you
|
|
598
|
+
declare your own `transition` on a chart mark, name every property it was already easing.
|
|
599
|
+
|
|
600
|
+
- **A chart tooltip closes when the page scrolls.** CDK's reposition strategy watches `window` and
|
|
601
|
+
registered `cdkScrollable`s only, so an app's own `overflow: auto` container left the panel
|
|
602
|
+
pinned in space while the chart scrolled out from under it. `ds-line-chart` reopens on the next
|
|
603
|
+
pointer move; the other four reopen when the pointer leaves a mark and enters one again.
|
|
604
|
+
|
|
605
|
+
The internal `ChartTooltipDirective`, which the package root does not export, grows one PRIVATE
|
|
606
|
+
member, `detachScrollClose`. `@ids-group-ltd/ids-design-system/components/chart-tooltip` is the
|
|
607
|
+
only specifier that reaches the class; a subclass declaring that name must rename it, because
|
|
608
|
+
TS2415 fires on the collision and `override` does not clear it for a private member.
|
|
609
|
+
|
|
610
|
+
- **The helper behind a chart tooltip's second line is renamed.** The internal `describeStanding`,
|
|
611
|
+
which returned the rank alongside the share, is the internal `describeShare` now. Neither is
|
|
612
|
+
exported from the package root, but `@ids-group-ltd/ids-design-system/components` exports them,
|
|
613
|
+
so an import of the old name stops resolving. Rename it; the signature is unchanged.
|
|
614
|
+
|
|
615
|
+
### Fixed
|
|
616
|
+
|
|
617
|
+
- **`ds-table`'s pagination footer insets per side, so the summary lines up with column one.** The
|
|
618
|
+
footer read `--ds-table-cell-pad-x` alone while the cells resolve `--ds-table-cell-pad-left` and
|
|
619
|
+
`-right` separately. A table asking for a flush first column — `--ds-table-cell-pad-left: 0`
|
|
620
|
+
with `-right` set and `-x` unset — got a footer at the 16px default while the column sat at 0.
|
|
621
|
+
The footer now walks the same per-side chain; `-x` still works as the shorthand for both.
|
|
622
|
+
|
|
623
|
+
One gap is left: `density="compact"` retunes the cells' padding on the table element itself, and
|
|
624
|
+
the footer sits outside that element rather than inside it, so a compact table with no
|
|
625
|
+
`--ds-table-cell-pad-*` of its own still has 12px cells under a 16px footer. Set
|
|
626
|
+
`--ds-table-cell-pad-x: var(--space-3)` beside `density="compact"`, or keep a local rule on the
|
|
627
|
+
footer.
|
|
628
|
+
|
|
629
|
+
- **`ds-donut-chart`'s error state holds the plot's height.** It rendered the message as a bare
|
|
630
|
+
paragraph, so a failed request collapsed the ring's 180px to one line of text and dragged the
|
|
631
|
+
page up under the reader. It now stands in the same ring-sized box the no-data state already
|
|
632
|
+
used. The message carries `empty-text is-error` where it carried `empty is-error`, so a rule of
|
|
633
|
+
yours written against `.empty.is-error` inside this chart no longer matches.
|
|
634
|
+
|
|
635
|
+
- **A role token set on an app shell no longer outranks your rule on a portaled panel.** A panel
|
|
636
|
+
sits in `document.body`, so the component copies the roles it needs onto the pane as an inline
|
|
637
|
+
style. It decided what to copy by comparing the host with `:root` — and because custom properties
|
|
638
|
+
inherit, a shell setting `--ds-radius-panel` for its own chrome made every picker under it an
|
|
639
|
+
overrider, each pinning the shell's value inline. A rule on `.ds-overlay-pane`, which is the only
|
|
640
|
+
route a stylesheet has to a portaled panel, then lost to a value nobody wrote. The comparison is
|
|
641
|
+
now against the host's PARENT, so only a role the host declares itself travels.
|
|
642
|
+
|
|
643
|
+
If you were relying on an ancestor's role reaching a panel, set it on the component instead —
|
|
644
|
+
`ds-select { --ds-radius-panel: 8px }` still forwards — or use the panel's own hook, such as
|
|
645
|
+
`--ds-dropdown-panel-radius`, which is forwarded with no such test.
|
|
646
|
+
|
|
647
|
+
### What you can now DELETE
|
|
648
|
+
|
|
649
|
+
| your workaround | why it is unnecessary | replace with |
|
|
650
|
+
| --- | --- | --- |
|
|
651
|
+
| `.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` |
|
|
652
|
+
| `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` |
|
|
653
|
+
| `.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 |
|
|
654
|
+
|
|
3
655
|
## 0.13.0 — 2026-09-14
|
|
4
656
|
|
|
5
657
|
### Breaking
|
|
@@ -168,9 +820,10 @@
|
|
|
168
820
|
screen together. The update phase — a mark changing size — is unchanged and still runs on
|
|
169
821
|
`--ds-motion-chart-mark-duration`.
|
|
170
822
|
|
|
171
|
-
`staggerMs` spaces the arrivals out
|
|
172
|
-
|
|
173
|
-
|
|
823
|
+
`staggerMs` spaces the arrivals out. `0` is the default and means no stagger; `40` is the
|
|
824
|
+
documented step, and the total delay is capped at 300ms so a hundred-mark series does not take
|
|
825
|
+
three seconds to appear. `ds-donut-chart` takes the input for parity and ignores it: a ring
|
|
826
|
+
arrives as one object, so there is nothing to stagger. Measured on the docs card at `staggerMs="40"`: five columns
|
|
174
827
|
resolve to 0, 40, 80, 120 and 160ms.
|
|
175
828
|
|
|
176
829
|
```html
|