@ids-group-ltd/ids-design-system 0.13.1 → 0.13.3
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 +626 -0
- package/components.md +17 -9
- package/docs/agent/INDEX.md +1 -1
- package/docs/agent/charts/ds-column-chart.md +3 -2
- package/docs/agent/charts/ds-line-chart.md +2 -1
- package/docs/agent/feedback/ds-bar.md +13 -0
- 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-bar-chart.mjs +81 -13
- package/fesm2022/ids-group-ltd-ids-design-system-components-bar-chart.mjs.map +1 -1
- package/fesm2022/ids-group-ltd-ids-design-system-components-bar.mjs +95 -0
- package/fesm2022/ids-group-ltd-ids-design-system-components-bar.mjs.map +1 -0
- 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 +198 -50
- package/fesm2022/ids-group-ltd-ids-design-system-components-chart-tooltip.mjs.map +1 -1
- package/fesm2022/ids-group-ltd-ids-design-system-components-chart.mjs +973 -0
- package/fesm2022/ids-group-ltd-ids-design-system-components-chart.mjs.map +1 -0
- package/fesm2022/ids-group-ltd-ids-design-system-components-column-chart.mjs +172 -111
- package/fesm2022/ids-group-ltd-ids-design-system-components-column-chart.mjs.map +1 -1
- package/fesm2022/ids-group-ltd-ids-design-system-components-donut-chart.mjs +86 -15
- package/fesm2022/ids-group-ltd-ids-design-system-components-donut-chart.mjs.map +1 -1
- package/fesm2022/ids-group-ltd-ids-design-system-components-funnel-chart.mjs +87 -12
- 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 +193 -98
- package/fesm2022/ids-group-ltd-ids-design-system-components-line-chart.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.mjs +233 -33
- package/fesm2022/ids-group-ltd-ids-design-system-components.mjs.map +1 -1
- package/fesm2022/ids-group-ltd-ids-design-system-core.mjs +1 -1
- package/fesm2022/ids-group-ltd-ids-design-system-core.mjs.map +1 -1
- package/fesm2022/ids-group-ltd-ids-design-system.mjs +2 -1
- package/fesm2022/ids-group-ltd-ids-design-system.mjs.map +1 -1
- package/migrations/0.13.2.json +269 -0
- package/migrations/0.13.3.json +211 -0
- package/package.json +17 -9
- package/styles/_chart-frame.scss +117 -10
- package/styles/_chart-interactive.scss +12 -3
- package/styles/_overlay-motion.scss +7 -6
- package/styles/_tokens-charts.scss +29 -5
- package/styles/_tokens.scss +1 -1
- package/types/ids-group-ltd-ids-design-system-components-bar-chart.d.ts +68 -5
- package/types/ids-group-ltd-ids-design-system-components-bar.d.ts +63 -0
- package/types/ids-group-ltd-ids-design-system-components-button.d.ts +3 -2
- 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 +21 -4
- package/types/ids-group-ltd-ids-design-system-components-chart.d.ts +543 -0
- package/types/ids-group-ltd-ids-design-system-components-column-chart.d.ts +125 -37
- package/types/ids-group-ltd-ids-design-system-components-donut-chart.d.ts +43 -4
- package/types/ids-group-ltd-ids-design-system-components-funnel-chart.d.ts +52 -4
- package/types/ids-group-ltd-ids-design-system-components-line-chart.d.ts +90 -23
- package/types/ids-group-ltd-ids-design-system-components.d.ts +91 -16
- package/types/ids-group-ltd-ids-design-system-core.d.ts +73 -6
- package/types/ids-group-ltd-ids-design-system.d.ts +7 -6
- package/docs/agent/feedback/ds-progress.md +0 -7
- package/fesm2022/ids-group-ltd-ids-design-system-components-progress.mjs +0 -41
- package/fesm2022/ids-group-ltd-ids-design-system-components-progress.mjs.map +0 -1
- package/types/ids-group-ltd-ids-design-system-components-progress.d.ts +0 -22
package/CHANGELOG.md
CHANGED
|
@@ -1,5 +1,631 @@
|
|
|
1
1
|
## Unreleased
|
|
2
2
|
|
|
3
|
+
## 0.13.3 — 2026-09-17
|
|
4
|
+
|
|
5
|
+
### Breaking
|
|
6
|
+
|
|
7
|
+
- **`ds-progress` and `ds-meter` are one component, `ds-bar`.** They were the same drawing — the
|
|
8
|
+
same 6px pill track, the same fill, the same clamping — under two names, and the only thing that
|
|
9
|
+
genuinely differed between them is now an input. `ds-meter` shipped in `0.13.2` and existed for
|
|
10
|
+
that one release.
|
|
11
|
+
|
|
12
|
+
```html
|
|
13
|
+
<ds-bar [value]="68" ariaLabel="Manifest upload progress" />
|
|
14
|
+
```
|
|
15
|
+
|
|
16
|
+
**For a progress bar the rename is the whole upgrade.** `value`, `max`, `variant`,
|
|
17
|
+
`indeterminate`, `target` and `ariaLabel` keep their names and their defaults, and `semantics`
|
|
18
|
+
defaults to `'progress'` — so a renamed `ds-progress` behaves exactly as it did.
|
|
19
|
+
`ProgressComponent` and `MeterComponent` are both `BarComponent`, and `ProgressVariant` is
|
|
20
|
+
`BarVariant` — all from `@ids-group-ltd/ids-design-system/components/bar`. A subclass of either
|
|
21
|
+
old class stops building; there is one class to extend now, and it carries every member both of
|
|
22
|
+
them had.
|
|
23
|
+
|
|
24
|
+
**A renamed `ds-meter` needs one more edit.** It was `aria-hidden` unless `ariaLabel` named it;
|
|
25
|
+
`ds-bar` announces as a progress bar by default. Add `semantics="none"` where the figure is
|
|
26
|
+
printed beside the bar, or `semantics="meter"` where the bar is the only place the measurement
|
|
27
|
+
appears. Nothing errors and nothing looks different — the change is entirely in what a screen
|
|
28
|
+
reader says, which is what the input exists to control.
|
|
29
|
+
|
|
30
|
+
**`ds-bar-chart` is a different component and is NOT renamed.** `ds-bar` is a prefix of it, so a
|
|
31
|
+
find-and-replace without a word boundary will corrupt every chart in the app.
|
|
32
|
+
|
|
33
|
+
- **The `--ds-progress-*` and `--ds-meter-*` tokens are `--ds-bar-*`.** `-height`,
|
|
34
|
+
`-track-color`, `-target-color`, `-target-width` and `-min-width` keep their suffix.
|
|
35
|
+
`--ds-progress-bar-color` and its `-success` / `-warning` / `-error` siblings became
|
|
36
|
+
`--ds-bar-fill-color` and siblings, because `--ds-bar-bar-color` stutters. The global
|
|
37
|
+
`--progress-h` is `--bar-h` — same 6px, under a name that still describes the component.
|
|
38
|
+
|
|
39
|
+
An override of a name nothing reads still parses, so a missed rename reports nothing and the bar
|
|
40
|
+
simply returns to its default look.
|
|
41
|
+
|
|
42
|
+
- **`valueFormat` on `ds-column-chart` and `ds-line-chart` now receives a second argument,
|
|
43
|
+
`location`.** The axis tick and the annex table used to share one call with no way to tell them
|
|
44
|
+
apart, so a custom formatter that spelled a value out in full also spelled it out on the axis,
|
|
45
|
+
where a fixed-width column has room for `1.2M` and not `1,248,392`. The callback is
|
|
46
|
+
`(value: number, location: ChartFormatLocation) => string` now, called with `'tick'` for the axis
|
|
47
|
+
label and `'tooltip'` everywhere else a value is printed in full (the annex table, the generated
|
|
48
|
+
description, the value beside a mark).
|
|
49
|
+
|
|
50
|
+
```ts
|
|
51
|
+
valueFormat: ChartValueFormat = (value, location) =>
|
|
52
|
+
location === 'tick' ? compact(value) : spelled(value);
|
|
53
|
+
```
|
|
54
|
+
|
|
55
|
+
An existing one-argument callback still compiles and still runs, because JavaScript ignores an
|
|
56
|
+
argument nothing reads. It cannot tell the two locations apart, though, so it prints the same
|
|
57
|
+
string for both, which is un-abbreviated on the axis wherever the built-in default used to
|
|
58
|
+
abbreviate for it.
|
|
59
|
+
|
|
60
|
+
**The built-in default changed too, with no callback involved.** It used to pick one suffix for
|
|
61
|
+
the whole axis, from the axis's own step, so `800K` and `1600K` shared a unit even past a million.
|
|
62
|
+
It now compacts each tick by that tick's own magnitude, so the same axis prints `800K` beside
|
|
63
|
+
`1.6M`. An axis whose ticks cross a thousand, million or billion boundary renders differently.
|
|
64
|
+
|
|
65
|
+
### Added
|
|
66
|
+
|
|
67
|
+
- **`ds-chart` is importable, with the marks that draw inside it.** The container the column and
|
|
68
|
+
line charts are built inside now ships as its own entry point,
|
|
69
|
+
`@ids-group-ltd/ids-design-system/components/chart`, for a plot the five presets do not cover - a
|
|
70
|
+
combo of columns and a cumulative line being the case that asked for it. It owns the frame, the
|
|
71
|
+
axes, the gridlines, the caption, the legend slot, the annex table and the generated description;
|
|
72
|
+
what is drawn against its scales is projected in.
|
|
73
|
+
|
|
74
|
+
```html
|
|
75
|
+
<ds-chart [categories]="months" secondaryAxisMode="rounded">
|
|
76
|
+
<svg:g dsColumnSeries [data]="billed" />
|
|
77
|
+
<svg:g dsLineSeries [data]="cumulative" axis="secondary" />
|
|
78
|
+
</ds-chart>
|
|
79
|
+
```
|
|
80
|
+
|
|
81
|
+
The entry point carries the container, the two series marks, the reference line and label marks,
|
|
82
|
+
their data types, the scales token and the two geometry helpers. A mark is an ATTRIBUTE selector
|
|
83
|
+
on a real `<svg:g>`, never an element of its own: an element the SVG specification does not know
|
|
84
|
+
renders nothing, its children included. Write `<svg:g dsColumnSeries>`, not `<ds-column-series>`.
|
|
85
|
+
|
|
86
|
+
**Reach for a preset first.** `ds-bar-chart`, `ds-column-chart`, `ds-donut-chart`,
|
|
87
|
+
`ds-funnel-chart` and `ds-line-chart` carry the accessible defaults, and the container is the
|
|
88
|
+
escape hatch for the plot none of them draws. It is not re-exported from the package facade, so it
|
|
89
|
+
is imported by its own path. The marks are Angular components, so nothing projected from React or
|
|
90
|
+
from `@angular/elements` can draw inside the canvas.
|
|
91
|
+
|
|
92
|
+
- **A column chart can carry several named series per category.** Hand `data` a list of
|
|
93
|
+
`ColumnChartSeries` instead of a flat list of points and every category carries one column per
|
|
94
|
+
series, keyed by a `ds-chart-legend` under the plot. `stack` decides how they share the band:
|
|
95
|
+
`'none'` (the default) and `'grouped'` stand them side by side, `'stacked'` puts each on top of
|
|
96
|
+
the one before it, and `'normalized'` stacks then divides by the category's own total, so every
|
|
97
|
+
band is full and the axis reads in shares.
|
|
98
|
+
|
|
99
|
+
```html
|
|
100
|
+
<ds-column-chart stack="grouped" [data]="[
|
|
101
|
+
{ id: 'billed', label: 'Billed', data: months },
|
|
102
|
+
{ id: 'committed', label: 'Committed', fill: 'hatched', data: forecast },
|
|
103
|
+
]" />
|
|
104
|
+
```
|
|
105
|
+
|
|
106
|
+
A series takes one colour for all of its marks and a series-wide `fill` paints every one of its
|
|
107
|
+
columns, where a flat list of points still colours each mark by its own position — the marks of a
|
|
108
|
+
single-series chart ARE the categories and the marks of a grouped one are not. A flat list still
|
|
109
|
+
takes the whole band, so a chart that was passing one stays exactly as it was. Stacked segments
|
|
110
|
+
are separated by a 2px gap in the surface colour rather than a drawn rule, which survives print
|
|
111
|
+
and colour-vision deficiency. `stack="stacked"` and `ds-line-chart`'s `axisMode="stacked"` are
|
|
112
|
+
different things: series on top of each other, against two plots one above the other.
|
|
113
|
+
|
|
114
|
+
- **`ds-donut-chart` takes `partOfWhole`, so its percentages can be turned off.** A ring always
|
|
115
|
+
printed each slice's share and there was no way to stop it. The input defaults to `true`, which is
|
|
116
|
+
what the ring already did, so nothing changes without asking; `[partOfWhole]="false"` drops the
|
|
117
|
+
percentage from the legend, the tooltip and the data table alike.
|
|
118
|
+
|
|
119
|
+
It starts `true` here and `false` on every other chart on purpose: a ring IS parts of one whole, so
|
|
120
|
+
a share of the total is a real quantity whatever the data, while a column chart's categories often
|
|
121
|
+
sum to a number nobody can point at.
|
|
122
|
+
|
|
123
|
+
- **A column can be drawn as a projection rather than a reading.** A `ColumnChartPoint` that sets
|
|
124
|
+
`fill: 'hatched'` keeps its colour and takes a striped texture over it, which is what separates a
|
|
125
|
+
forecast from a settled figure without spending a second hue on it.
|
|
126
|
+
|
|
127
|
+
```html
|
|
128
|
+
<ds-column-chart [data]="[
|
|
129
|
+
{ label: 'Jun', value: 3020 },
|
|
130
|
+
{ label: 'Jul', value: 3400, fill: 'hatched' },
|
|
131
|
+
]" />
|
|
132
|
+
```
|
|
133
|
+
|
|
134
|
+
Texture is the encoding that survives greyscale, print and colour-vision deficiency, so it carries
|
|
135
|
+
the distinction where a lighter tint of the same colour would not. The chart reads nothing into the
|
|
136
|
+
flag: which columns are projections is a fact only the caller has. `--ds-chart-hatch-color` and
|
|
137
|
+
`--ds-chart-hatch-width` tune the stripes.
|
|
138
|
+
|
|
139
|
+
- **A second value axis on `ds-chart`, and a line series to draw against it.** A plot can now carry
|
|
140
|
+
two quantities at two magnitudes - a figure per month on the left axis, the running total of
|
|
141
|
+
those months on the right - instead of flattening one of them against the other's scale.
|
|
142
|
+
|
|
143
|
+
`secondaryAxisMode` takes the same four words `ds-line-chart`'s `yAxisMode` does:
|
|
144
|
+
`'rounded'` (the default) hangs the second scale on the first's own gridlines at a round step,
|
|
145
|
+
`'exact'` ends it on its largest reading, `'independent'` scales and grids it on its own, and
|
|
146
|
+
`'stacked'` draws two plots one above the other over a shared category axis. `ChartAxisMode` and
|
|
147
|
+
`ChartAxis` are exported from the core entry point, and `LineChartAxisMode` is now an alias of
|
|
148
|
+
the first.
|
|
149
|
+
|
|
150
|
+
`axisColor` and `secondaryAxisColor` paint each axis's tick labels in the colour of the marks
|
|
151
|
+
measured against it, which on a two-scale plot is the only thing that says which numbers a mark
|
|
152
|
+
is read against. They are inert while the plot has one axis.
|
|
153
|
+
|
|
154
|
+
`--ds-chart-area-opacity` sets how solid the band a line series fills down to its baseline is.
|
|
155
|
+
|
|
156
|
+
- **Reference lines and bands on `ds-column-chart`.** `thresholds` draws a target, a budget or an
|
|
157
|
+
SLA across the plot, behind the columns.
|
|
158
|
+
|
|
159
|
+
```ts
|
|
160
|
+
thresholds: ChartThreshold[] = [
|
|
161
|
+
{ value: 85, label: 'Target' },
|
|
162
|
+
{ value: 73, label: 'Escalation', dash: 'dotted' },
|
|
163
|
+
];
|
|
164
|
+
```
|
|
165
|
+
|
|
166
|
+
Each entry is ONE number, not a coordinate pair: `value`, plus an optional `label`, `color` and
|
|
167
|
+
`dash` (`'solid' | 'dashed' | 'dotted'`, default `'dashed'`). `to` turns the same object into a
|
|
168
|
+
band filled between two readings instead of a line, written in either order.
|
|
169
|
+
|
|
170
|
+
A threshold widens the value axis to hold it, so a target above every column still lands on the
|
|
171
|
+
plot rather than off it. It is also named in the generated description - "Target at 85, 2 of 5
|
|
172
|
+
points above" - so the line reaches a reader who cannot see it.
|
|
173
|
+
|
|
174
|
+
Four tokens set the default look: `--ds-chart-threshold-color`,
|
|
175
|
+
`--ds-chart-threshold-band-opacity`, `--ds-chart-threshold-dashed-pattern` and
|
|
176
|
+
`--ds-chart-threshold-dotted-pattern`. A threshold's own `color` overrides the first.
|
|
177
|
+
|
|
178
|
+
### Changed
|
|
179
|
+
|
|
180
|
+
- **Hovering a legend item behaves as hovering the mark it names.** On `ds-donut-chart` the panel
|
|
181
|
+
opened over the legend row rather than over the arc, so the reader was pointed at the label
|
|
182
|
+
instead of the slice; on `ds-funnel-chart` the stage rows did nothing at all. Both now open the
|
|
183
|
+
same panel over the MARK and dim the rest of the plot, identical to pointing at the arc or the bar
|
|
184
|
+
directly, and the keyboard route follows wherever the legend carries it.
|
|
185
|
+
|
|
186
|
+
- **A chart tooltip opens against its mark, not against the row that holds it.** `ds-bar-chart`
|
|
187
|
+
anchored the panel to the whole row — label, value and track — so it opened a row-height above
|
|
188
|
+
the bar it was about: 46.7px from the mark where the gap asks for 6. It anchors to the bar now.
|
|
189
|
+
The gap itself went from 12px to 6px on every chart, because a panel a finger's width off its
|
|
190
|
+
mark reads as floating free of it.
|
|
191
|
+
|
|
192
|
+
- **`ds-column-chart`'s `data` input accepts a second shape.** It was
|
|
193
|
+
`readonly ColumnChartPoint[]` and is now
|
|
194
|
+
`readonly ColumnChartPoint[] | readonly ColumnChartSeries[]`. Passing one is unaffected; reading
|
|
195
|
+
the signal back or overriding it is not. `chart.data()[0].value` stops type-checking without a
|
|
196
|
+
narrowing test, because a `ColumnChartSeries` has no `value`, and a subclass redeclaring `data`
|
|
197
|
+
fails on TS2416 since an input signal's type is invariant. Narrow on the shape —
|
|
198
|
+
`'data' in entry` — wherever the values are read back.
|
|
199
|
+
|
|
200
|
+
- **Exported class member surface moved — only matters if you SUBCLASS one of these.**
|
|
201
|
+
`ProgressComponent` and `MeterComponent` are gone; `BarComponent` carries every member both of
|
|
202
|
+
them had. `ChartTooltipDirective`, internal and not exported from the package root, gains
|
|
203
|
+
`dsChartTooltipPreferBelow`. `ColumnChartComponent` moved its drawing into the shared container
|
|
204
|
+
and took several series, so it gained `thresholds`, `categories`, `geometry`, `tableRows`,
|
|
205
|
+
`viewHeightPx`, `skeletonHeightPx`, `stack`, `resolvedSeries`, `seriesRefs`, `pinnedSeries`,
|
|
206
|
+
`slotCount`, `offsets`, `offsetsFor`, `multiSeries`, `legendItems` and `axisFormat`, and lost the
|
|
207
|
+
members that used to draw its marks. `DonutChartComponent` gained
|
|
208
|
+
`partOfWhole`, `arcAt`, `isDimmed` and three legend handlers; `FunnelChartComponent` gained
|
|
209
|
+
`isDimmed` and `onRowEnter`. A subclass declaring any of those names collides: rename yours, or
|
|
210
|
+
add `override` where it genuinely means the same thing.
|
|
211
|
+
|
|
212
|
+
- **A held mark opens its panel BELOW itself.** The Unpin control sits at the plot's top edge, and
|
|
213
|
+
a panel opening upward from a mark in the upper half landed on top of it. No z-index fixes that
|
|
214
|
+
— the panel is portaled to the body, and an app layout that isolates its stacking context traps
|
|
215
|
+
the chart's own chrome underneath whatever number it carries. Below-first while pinned keeps the
|
|
216
|
+
two apart; the other three fallbacks still catch a mark with no room under it.
|
|
217
|
+
|
|
218
|
+
- **Moving a pin from one mark to another no longer blinks.** The press that re-aimed it cleared
|
|
219
|
+
the pin first and the click set it again, so the Unpin control and the held mark's styling
|
|
220
|
+
unmounted for a frame between the two marks. A press that lands on another mark of the same
|
|
221
|
+
chart is a re-aim now, and `pinned` never goes false across it.
|
|
222
|
+
|
|
223
|
+
- **The pin glyph is a drawing pin seen from the side.** Head-on it read as a lamp or a bell at the
|
|
224
|
+
14px the charts badge it at.
|
|
225
|
+
|
|
226
|
+
- **A focused mark wears the app's own focus colour.** The ring was white with a dark halo, which
|
|
227
|
+
on a coloured band read as an artefact rather than as a focus indicator. It is
|
|
228
|
+
`--focus-ring-color` with a light keyline around it now — the keyline is what separates it from
|
|
229
|
+
a mark of the same hue family, which is why the indicator is two tones either way.
|
|
230
|
+
`--ds-chart-focus-ring-color` and `--ds-chart-focus-halo-color` still set both.
|
|
231
|
+
|
|
232
|
+
- **A chart with nothing to draw keeps its axes.** `ds-line-chart` and `ds-column-chart` render
|
|
233
|
+
the value axis and the category axis behind the empty, error and no-visible-series messages, so
|
|
234
|
+
the message stands in a plot rather than in a blank card. Without ticks or labels: there is no
|
|
235
|
+
data to scale them against. The charts with no axes — donut, funnel, bar — are unchanged.
|
|
236
|
+
|
|
237
|
+
- **`ds-bar` cannot collapse to nothing in a content-sized cell.** It carries
|
|
238
|
+
`min-inline-size: 3rem`, overridable through `--ds-bar-min-width`. A box sized to its content —
|
|
239
|
+
a `width: 'content'` table column, a shrink-to-fit flex or grid item — is sized by what its
|
|
240
|
+
contents contribute intrinsically, and a bar that is 100% of its cell contributes nothing: one
|
|
241
|
+
alone in such a cell measures 0px wide. `ds-progress` had no floor, so a bar that used to
|
|
242
|
+
disappear there is now visible; set the property to `0` for the old behaviour.
|
|
243
|
+
|
|
244
|
+
- **`indeterminate` is ignored unless `semantics` is `'progress'`.** Only a task has an unknown
|
|
245
|
+
duration. Nothing that set it on `ds-progress` is affected, because that is the default.
|
|
246
|
+
|
|
247
|
+
### Fixed
|
|
248
|
+
|
|
249
|
+
- **A pinned tooltip survives a scroll.** Every chart tore its panel down on any scroll of the page,
|
|
250
|
+
and because a pinned mark deliberately stops answering the pointer, nothing brought it back: the
|
|
251
|
+
pin badge and the Unpin control were left sitting over a reading that was no longer on screen.
|
|
252
|
+
The panel repositions now instead of closing. An unpinned tooltip still goes away on both a scroll
|
|
253
|
+
and the pointer leaving, as it always did.
|
|
254
|
+
|
|
255
|
+
- **A column chart plots a domain that reaches below zero.** Every scale clamped its floor at zero,
|
|
256
|
+
so a negative reading drew nothing at all and a P&L series rendered as a flat baseline with no
|
|
257
|
+
warning. The axis now spans the data, the zero line is drawn where it falls inside the plot, and a
|
|
258
|
+
negative column grows downward from it with its value label at its own tip. Room for that label is
|
|
259
|
+
reserved only when the domain actually reaches below zero, so an all-positive chart keeps its
|
|
260
|
+
height.
|
|
261
|
+
|
|
262
|
+
- **The value axis fits its own labels.** The gutter was a fixed width, which an SVG canvas CLIPS
|
|
263
|
+
rather than overflows, so a locale whose compact numbers are wider than an English `3.5k` lost the
|
|
264
|
+
leading digit of every tick - `3,5 тыс.` printed as `,5 тыс.`. The gutter is measured from the
|
|
265
|
+
widest label that actually rendered, and `axisGutter` is the floor it will not go below.
|
|
266
|
+
|
|
267
|
+
|
|
268
|
+
## 0.13.2 — 2026-09-15
|
|
269
|
+
|
|
270
|
+
### Added
|
|
271
|
+
|
|
272
|
+
- **`ds-line-chart` takes `annotations`, so a reading can be labelled without a pointer.** The
|
|
273
|
+
chart had tooltips and nothing else, which leaves a peak unreadable in a screenshot, a printed
|
|
274
|
+
page or a slide. An annotation names a `categoryIndex`, a `label` and optionally the `seriesId`
|
|
275
|
+
it belongs to — left out, the first plotted series.
|
|
276
|
+
|
|
277
|
+
```html
|
|
278
|
+
<ds-line-chart
|
|
279
|
+
[categories]="months"
|
|
280
|
+
[series]="series"
|
|
281
|
+
[annotations]="[{ categoryIndex: 5, label: 'Peak' }]" />
|
|
282
|
+
```
|
|
283
|
+
|
|
284
|
+
It sits above the reading, below it where the plot has no room — a peak is at the top, which is
|
|
285
|
+
exactly where a label clamped upward lands on its own marker — and anchors to its own edge within
|
|
286
|
+
48 view units of one rather than hanging outside the viewBox. A label whose series is hidden or
|
|
287
|
+
whose reading is `null` draws nothing, so a legend toggle takes its annotations with it.
|
|
288
|
+
|
|
289
|
+
It is drawn with a halo rather than a box (`paint-order: stroke`), so it survives crossing the
|
|
290
|
+
line and a gridline; `--ds-line-chart-annotation-color`, `-font-size`, `-weight`, `-halo-color`
|
|
291
|
+
and `-halo-width` set its look. The plot's own text is `aria-hidden`, so the labels are read out
|
|
292
|
+
of the chart's description instead — `Noted: Peak; Launch.` after the series sentences — rather
|
|
293
|
+
than twice from the plot and the annex table.
|
|
294
|
+
|
|
295
|
+
- **`ds-progress` takes a `target`, drawn as a hairline across the track.** A second point on the
|
|
296
|
+
same 0–100 scale, so a bar reads actual against a goal or a baseline in one glance instead of
|
|
297
|
+
standing alone. Clamped like `value`, ignored while `indeterminate`, and unset draws nothing —
|
|
298
|
+
every existing bar is unchanged.
|
|
299
|
+
|
|
300
|
+
```html
|
|
301
|
+
<ds-progress
|
|
302
|
+
[value]="62"
|
|
303
|
+
[target]="75"
|
|
304
|
+
ariaLabel="Resolved 62% against a 75% target" />
|
|
305
|
+
```
|
|
306
|
+
|
|
307
|
+
**Name the comparison in `ariaLabel`.** `role="progressbar"` announces one value and has no second
|
|
308
|
+
to carry, so the mark is visual only — a reader on a screen reader gets the target from the label
|
|
309
|
+
or not at all. `--ds-progress-target-color` and `--ds-progress-target-width` set its look.
|
|
310
|
+
|
|
311
|
+
- **`ds-progress` takes a `max`, so `value` can be the real count.** The bar read 0–100 only and
|
|
312
|
+
pinned `aria-valuemax="100"`, which made a caller convert their own numbers before us and put the
|
|
313
|
+
percentage into the accessible name in place of the measurement. `max` is the scale `value` and
|
|
314
|
+
`target` are read against; at its default of 100 they are percentages, so every existing bar is
|
|
315
|
+
unchanged, and `aria-valuemax` follows it.
|
|
316
|
+
|
|
317
|
+
```html
|
|
318
|
+
<ds-progress [value]="37" [max]="80" [target]="64" ariaLabel="Requests handled" />
|
|
319
|
+
```
|
|
320
|
+
|
|
321
|
+
That bar fills to 46.25% and reports `aria-valuenow="37"` of `aria-valuemax="80"` — "37 of 80"
|
|
322
|
+
rather than "46%". A `max` of zero or less falls back to 100, because a scale with no width has no
|
|
323
|
+
fraction to draw.
|
|
324
|
+
|
|
325
|
+
`ProgressComponent` grows by the `target` and `max` inputs; a subclass declaring either name stops
|
|
326
|
+
building until it renames the member or marks it `override`.
|
|
327
|
+
|
|
328
|
+
- **`ds-bar-chart` and `ds-column-chart` take `partOfWhole`, and it is what states each mark's share
|
|
329
|
+
of the total.** A share of a total is only a real quantity when the marks are parts of one whole.
|
|
330
|
+
Visitors per funnel stage, or response time per endpoint, sum to a number nobody can point at, and
|
|
331
|
+
a percentage of THAT is arithmetic dressed as a fact — so the charts no longer state one unless
|
|
332
|
+
you say the relationship holds:
|
|
333
|
+
|
|
334
|
+
```html
|
|
335
|
+
<ds-bar-chart partOfWhole caption="Spend by department, share of the budget" [data]="rows" />
|
|
336
|
+
```
|
|
337
|
+
|
|
338
|
+
With it set, the share appears in two places: the tooltip's second line, and a `Share of total`
|
|
339
|
+
column in the data table. The column is headed `Share of total` rather than `Share` because
|
|
340
|
+
`ds-bar-chart` already prints a percentage beside each row and that one is the share of the
|
|
341
|
+
LARGEST row — two different questions, each now labelled with the one it answers.
|
|
342
|
+
|
|
343
|
+
The cell is empty where there is no share to state: a lone mark, or a reading that is zero,
|
|
344
|
+
negative or non-finite. Negatives are left out of the total rather than subtracted from it.
|
|
345
|
+
|
|
346
|
+
- **Every chart takes `pinOnClick`, which holds a reading in place.** Clicking a mark keeps it, its
|
|
347
|
+
tooltip and — with `dimOthers` — the dimming of everything else, so the comparison survives the
|
|
348
|
+
pointer leaving the chart entirely. Hovering another mark does not move it; clicking another one
|
|
349
|
+
does. Clicking the pinned mark again, pressing outside it, or Escape releases it. Off by default:
|
|
350
|
+
a click is already the drill-down hook, and a mark left lit after the pointer has gone needs a
|
|
351
|
+
reader who knows why it is lit.
|
|
352
|
+
|
|
353
|
+
```html
|
|
354
|
+
<ds-column-chart interactive pinOnClick dimOthers [data]="points" />
|
|
355
|
+
```
|
|
356
|
+
|
|
357
|
+
A pinned mark carries a pushpin on an opaque disc — over the row's bar, the column, the middle of
|
|
358
|
+
the ring's arc, the middle of the funnel band — because the panel can sit anywhere on screen and
|
|
359
|
+
the reader needs to see WHICH mark is held. An `Unpin` button appears centred above the plot while
|
|
360
|
+
anything is pinned, so the way out is on screen rather than a key nobody was told about, and it is
|
|
361
|
+
centred because a corner competes with the donut's legend and the column chart's value labels.
|
|
362
|
+
|
|
363
|
+
The click output fires either way — pinning is a state, not a handler. On `ds-line-chart` the pin
|
|
364
|
+
hangs off the data markers rather than the plot, so Enter and Space pin from the keyboard too.
|
|
365
|
+
|
|
366
|
+
- **`ds-meter` — one track and one fill, for a measurement inside a table cell.** Every chart is a
|
|
367
|
+
block with a caption, a legend and an annex table; in a 60px cell that chrome is the whole cell,
|
|
368
|
+
so a micro-bar in a column had nothing to be built from. This is the mark on its own — no
|
|
369
|
+
caption, no legend, no tooltip, no table.
|
|
370
|
+
|
|
371
|
+
```html
|
|
372
|
+
<ds-meter [value]="row.rate" [max]="highestRate" />
|
|
373
|
+
```
|
|
374
|
+
|
|
375
|
+
`max` is the ceiling the column is read against, usually the column's own largest value, so the
|
|
376
|
+
longest bar fills its track and the rest are its share; at its default of 100, `value` is a
|
|
377
|
+
percentage. A value past `max` fills the track rather than overflowing, a negative one draws
|
|
378
|
+
nothing, and a `max` of zero or less falls back to 100.
|
|
379
|
+
|
|
380
|
+
**It is not `ds-progress`.** That reports how far a task has got and says so with
|
|
381
|
+
`role="progressbar"`, which a table of two hundred measurements would announce two hundred times.
|
|
382
|
+
A rate, a score or a count against a ceiling has no beginning and no completion. So the mark is
|
|
383
|
+
`aria-hidden` unless `ariaLabel` names it — leave it unset where the cell prints the figure
|
|
384
|
+
beside the bar, and set it where the bar is the only place the number appears.
|
|
385
|
+
|
|
386
|
+
The fill takes `--ds-meter-fill-color`, so a column is coloured once in a stylesheet rather than
|
|
387
|
+
once per row; the `color` input overrides it where the colour carries meaning.
|
|
388
|
+
`--ds-meter-height`, `--ds-meter-track-color` and `--ds-meter-radius` set the rest.
|
|
389
|
+
|
|
390
|
+
The bar is as wide as the box it sits in, so the column decides. A box sized to its content —
|
|
391
|
+
`width: 'content'` on `ds-table`, or a shrink-to-fit flex or grid item — is sized by what its
|
|
392
|
+
contents contribute intrinsically, and a bar that is 100% of its cell contributes nothing: one
|
|
393
|
+
alone in such a cell comes out 0px wide. The host carries a `min-inline-size` of `3rem` so it
|
|
394
|
+
cannot vanish, overridable through `--ds-meter-min-width`; give it a width of your own where the
|
|
395
|
+
bar should be a fixed size.
|
|
396
|
+
|
|
397
|
+
- **A `ds-bar-chart` row takes `segments`, which divide its bar without shortening it.** A row that
|
|
398
|
+
is a distribution had to become its own chart. The bar keeps its own length — the row's share of
|
|
399
|
+
the largest row — and the parts say what it is made of, so one plot answers both "which department
|
|
400
|
+
spends most" and "on what".
|
|
401
|
+
|
|
402
|
+
```html
|
|
403
|
+
<ds-bar-chart [data]="[{ label: 'Engineering', value: 412000, segments: [
|
|
404
|
+
{ label: 'Salaries', value: 291000 },
|
|
405
|
+
{ label: 'Tooling', value: 74000 },
|
|
406
|
+
] }]" />
|
|
407
|
+
```
|
|
408
|
+
|
|
409
|
+
The parts are sized against their OWN sum and always fill the bar: a set that does not add up to
|
|
410
|
+
`value` is a data error, and a gap left where the difference is would read as an unlabelled
|
|
411
|
+
category. They are categories rather than one series, so they take the categorical palette in
|
|
412
|
+
order and the row's `color` goes unused; `color` on a segment overrides its slot. Each part gets
|
|
413
|
+
its own row in the annex table under the row it belongs to. Pair the chart with `ds-chart-legend`
|
|
414
|
+
to name them — the parts carry no text of their own.
|
|
415
|
+
|
|
416
|
+
- **A `ds-bar-chart` row takes `detail`, a second reading printed under the label.** A row often
|
|
417
|
+
encodes a ratio — 12,400 visitors against 456 requests — and the bar can draw only one of the two
|
|
418
|
+
numbers, so the other had nowhere to go. It is passed already formatted, because the row knows
|
|
419
|
+
what its second number means and the chart does not, and it reaches the annex table too.
|
|
420
|
+
|
|
421
|
+
```html
|
|
422
|
+
<ds-bar-chart [data]="[{ label: 'Organic', value: 12400, detail: '456 requests · 3.7%' }]" />
|
|
423
|
+
```
|
|
424
|
+
|
|
425
|
+
- **`ds-line-chart` takes `max` and `maxSecondary`, which pin the value axis.** A panel that opens
|
|
426
|
+
one subject at a time derived a different axis for each, so two plots with the same gentle wiggle
|
|
427
|
+
could be four times apart in value with nothing on screen saying so. A fixed maximum is what makes
|
|
428
|
+
two renders comparable.
|
|
429
|
+
|
|
430
|
+
```html
|
|
431
|
+
<ds-line-chart [max]="5000" [categories]="months" [series]="series" />
|
|
432
|
+
```
|
|
433
|
+
|
|
434
|
+
Null, the default, keeps the derived axis, so every existing chart is unchanged. A maximum below
|
|
435
|
+
the data does not clip it — the larger of the two wins, because hiding a reading is worse than
|
|
436
|
+
more headroom than you asked for. `maxSecondary` does the same for the axis a series reaches with
|
|
437
|
+
`axis: 'secondary'`.
|
|
438
|
+
|
|
439
|
+
- **`ds-funnel-chart` takes `drop`, which says what its Drop column reports.** `'relative'`, the
|
|
440
|
+
default, is the share that leaked at that stage and is what the column always showed;
|
|
441
|
+
`'absolute'` is the COUNT that leaked, and `'none'` takes the column out. Both figures answer a
|
|
442
|
+
real question and they are not the same question: on a settlement funnel the share is a talking
|
|
443
|
+
point and the count is a re-targeting job. The count was recoverable by subtracting two rows, and
|
|
444
|
+
a reader should not have to.
|
|
445
|
+
|
|
446
|
+
```html
|
|
447
|
+
<ds-funnel-chart drop="absolute" [stages]="stages" />
|
|
448
|
+
```
|
|
449
|
+
|
|
450
|
+
- **Every chart takes `tooltipLingerMs`, and `DS_CONFIG.chart.tooltipLingerMs` sets it app-wide.**
|
|
451
|
+
How long the panel stays after the pointer leaves the mark. See the tooltip entry under Changed
|
|
452
|
+
for what the default does and when to raise it.
|
|
453
|
+
|
|
454
|
+
- **A pinned mark offers an `Unpin` control, and says which mark it is.** `ds-bar-chart`,
|
|
455
|
+
`ds-column-chart`, `ds-donut-chart` and `ds-funnel-chart` render a pill button above the plot
|
|
456
|
+
while a mark is pinned — Escape already released one, and a control that says so is what a reader
|
|
457
|
+
finds without knowing the key. `ds-donut-chart` and `ds-funnel-chart` also draw a pin glyph at the
|
|
458
|
+
pinned slice's or band's centre, so the plot itself carries which one is held rather than leaving
|
|
459
|
+
it to the panel; the glyph takes no pointer events. `--ds-chart-pin-size` sizes it, and the button
|
|
460
|
+
is `.pin-reset`.
|
|
461
|
+
|
|
462
|
+
The internal mark-state interface behind it — not exported from the package root — gains a
|
|
463
|
+
`release()`, and its factory implements it. Only a hand-written implementation of that interface
|
|
464
|
+
has one more method to satisfy.
|
|
465
|
+
|
|
466
|
+
- **A toggleable legend in `isolate` mode offers `None`.** Beside `All` and the per-series controls,
|
|
467
|
+
which left no way to clear the plot in one action.
|
|
468
|
+
|
|
469
|
+
### Changed
|
|
470
|
+
|
|
471
|
+
- **Turning a chart's frame off is an input now, not a stylesheet rule.** The frame still draws by
|
|
472
|
+
default. Switching it off took `ds-bar-chart { --ds-chart-frame-border-width: 0;
|
|
473
|
+
--ds-chart-frame-padding: 0 }` in a global sheet — a deep rule into a component's own chrome,
|
|
474
|
+
which is the shape of styling the rest of the library has been turning into inputs and tokens.
|
|
475
|
+
|
|
476
|
+
`frame` takes `'auto'` (the default, draws it) or `'none'`, and falls back to
|
|
477
|
+
`DS_CONFIG.chart.frame` when unset — whether charts live inside cards is one decision per app,
|
|
478
|
+
the same as `dataTable`:
|
|
479
|
+
|
|
480
|
+
```ts
|
|
481
|
+
provideDsConfig({ chart: { frame: 'none' } });
|
|
482
|
+
```
|
|
483
|
+
|
|
484
|
+
```html
|
|
485
|
+
<ds-donut-chart frame="none" [data]="slices" />
|
|
486
|
+
```
|
|
487
|
+
|
|
488
|
+
The two custom properties still size the frame and still work; a stylesheet zeroing them can drop
|
|
489
|
+
those declarations in favour of the config key. `ChartFrame` is exported from the package root.
|
|
490
|
+
|
|
491
|
+
- **The annex data table is off by default.** `dataTable` defaults to `'none'` rather than
|
|
492
|
+
`'toggle'`, on all five charts and in `DS_CONFIG.chart.dataTable`. A disclosure under every plot
|
|
493
|
+
is chrome the page did not ask for, and the page usually carries the numbers already.
|
|
494
|
+
|
|
495
|
+
It stays the non-visual route to the numbers where a page does NOT carry them, so turn it on
|
|
496
|
+
deliberately — per chart with `dataTable="toggle"`, or once for an app:
|
|
497
|
+
|
|
498
|
+
```ts
|
|
499
|
+
provideDsConfig({ chart: { dataTable: 'toggle' } });
|
|
500
|
+
```
|
|
501
|
+
|
|
502
|
+
- **A legend control isolates a series rather than hiding one, and `ds-chart-legend` says which.**
|
|
503
|
+
`mode` is `'isolate'` by default: choosing a series shows that one and hides the rest, which takes
|
|
504
|
+
one action instead of one per series on a crowded chart. `mode="toggle"` is the old behaviour —
|
|
505
|
+
hide one, leave the rest — for taking a dominant series out so the others can be read at a usable
|
|
506
|
+
scale. `ds-line-chart` forwards it as `legendMode`.
|
|
507
|
+
|
|
508
|
+
The two are different controls, not two looks: isolate is a single choice among many, so it
|
|
509
|
+
renders as a radio group running `All`, each series, `None`, and toggle renders as the checkboxes
|
|
510
|
+
it already did. That is what gives each the keyboard and screen-reader behaviour it should have.
|
|
511
|
+
One option is always chosen — `All` where the set is neither one series nor empty — because a
|
|
512
|
+
radio group with nothing selected cannot say whether it means "everything" or "not decided".
|
|
513
|
+
|
|
514
|
+
**If you set `legendFilters` on `ds-line-chart`, its legend changes shape.** Add
|
|
515
|
+
`legendMode="toggle"` to keep the checkboxes. `hiddenSeries` is unchanged in both modes, so a page
|
|
516
|
+
driving it from a URL parameter needs nothing.
|
|
517
|
+
|
|
518
|
+
- **A chart tooltip can be selected and dismissed with Escape, and reached with the pointer where
|
|
519
|
+
you ask for it.** The pane was inert and closed the instant the pointer left the mark, which left
|
|
520
|
+
it unreadable at high zoom, unselectable, and impossible to clear without moving the pointer away.
|
|
521
|
+
|
|
522
|
+
The pane takes the pointer now, and Escape closes the panel — it stays closed until the pointer
|
|
523
|
+
visits another mark, so a reader who clears the screen keeps it cleared. Reaching the panel is
|
|
524
|
+
`tooltipLingerMs`, which is `0`: the panel goes when the pointer does, because one left behind
|
|
525
|
+
sits over the plot the reader has moved on to. WCAG 1.4.13's hoverable clause only bites where the
|
|
526
|
+
panel holds something to reach — a link, a figure, a selectable string — so set
|
|
527
|
+
`[tooltipLingerMs]="140"` on those charts, or `DS_CONFIG.chart.tooltipLingerMs` for an app whose
|
|
528
|
+
tooltips all carry one. 140ms is what crossing the gap to a portaled panel takes at an ordinary
|
|
529
|
+
pointer speed.
|
|
530
|
+
|
|
531
|
+
If you styled `.ds-chart-tooltip-pane` with `pointer-events`, that rule now decides whether the
|
|
532
|
+
panel can be selected at all — the pane must stay `auto`.
|
|
533
|
+
|
|
534
|
+
- **A chart tooltip's second line is opt-in.** `0.13.1` gave every `ds-bar-chart` and
|
|
535
|
+
`ds-column-chart` tooltip a `18.6% of total` line whether or not the marks were parts of a whole.
|
|
536
|
+
It appears only under `partOfWhole` now. Set it on any chart whose categories genuinely divide one
|
|
537
|
+
total to keep the line; leave it off and the tooltip carries the label and the value, as before
|
|
538
|
+
`0.13.1`.
|
|
539
|
+
|
|
540
|
+
- **Exported class member surface grew — only matters if you SUBCLASS one of these.** `BarChartComponent`,
|
|
541
|
+
`ColumnChartComponent`, `DonutChartComponent`, `FunnelChartComponent` and `LineChartComponent` all
|
|
542
|
+
gain `pinOnClick` and the protected `onMarkClick`, which `LineChartComponent` spells
|
|
543
|
+
`onMarkerClick` beside its own `pinnedCategory` and `releaseCategoryPin`; `BarChartComponent` and
|
|
544
|
+
`ColumnChartComponent` also gain `partOfWhole` and the protected `valueClearance`; all five gain
|
|
545
|
+
`frame` and `frameResolved`; `LineChartComponent` gains `legendMode`; the
|
|
546
|
+
internal `ChartLegendComponent`, which the package root does not export, gains `mode`, `isolated`,
|
|
547
|
+
`isolate` and `showAll`; and the internal `ChartTooltipDirective`, also unexported there, gains
|
|
548
|
+
`dsChartTooltipExtraGap` and the private `detachEscape` and `closeOnEscape`.
|
|
549
|
+
|
|
550
|
+
All five also gain `tooltipLingerMs` and the private `tooltipLingerResolved`; `FunnelChartComponent`
|
|
551
|
+
gains `drop` and the protected `pinnedCenter`; `LineChartComponent` gains `max`, `maxSecondary`,
|
|
552
|
+
`annotations`, `placedAnnotations` and the protected `onPointerAnywhere`, `host`,
|
|
553
|
+
`cancelCategoryClear` and `pendingCategoryClear`; the internal legend also gains `groupName` and
|
|
554
|
+
`hideAll`.
|
|
555
|
+
|
|
556
|
+
Outside the charts: `ProgressComponent` gains `target`, `max` and the protected `scale`,
|
|
557
|
+
`clampedTarget`, `targetPercent` and `valuePercent`, and the internal message base the fields and
|
|
558
|
+
the button extend — unexported from the package root — gains a protected
|
|
559
|
+
`reserveFollowsFieldDefault`.
|
|
560
|
+
|
|
561
|
+
A subclass declaring any of those names collides. For a public or protected member the fix is
|
|
562
|
+
`override` or a rename; for a private one only a rename works, because TS2415 fires on the name
|
|
563
|
+
and `override` does not clear it.
|
|
564
|
+
|
|
565
|
+
### Fixed
|
|
566
|
+
|
|
567
|
+
- **`ds-line-chart` draws from axis to axis.** Its readings sat at the centre of a slot each, which
|
|
568
|
+
left an empty strip of plot against the value axis and another against the far edge — a gap that
|
|
569
|
+
reads as data the chart is withholding. The first reading is on the value axis now and the last
|
|
570
|
+
at the far edge, with the rest dividing the run evenly. The crosshair band is centred on its
|
|
571
|
+
reading and clamped at both ends, so the first and last are half-width and neither hangs over an
|
|
572
|
+
axis label.
|
|
573
|
+
|
|
574
|
+
- **A drag across a chart no longer selects its chrome.** Axis ticks, legend labels and the caption
|
|
575
|
+
a screen reader needs — clipped to a thin strip for everyone else — all came out selected, and the
|
|
576
|
+
selection painted as bars across the card over content that is not visibly there. The plot is
|
|
577
|
+
`user-select: none` now; the annex table, the funnel's stage table and the visible caption stay
|
|
578
|
+
selectable, because those carry numbers people copy.
|
|
579
|
+
|
|
580
|
+
- **Clicking a slice or a band no longer draws a rectangle around it.** Chromium focuses an SVG
|
|
581
|
+
shape when it is clicked even with no `tabindex` on it, and reports that focus as NOT
|
|
582
|
+
`:focus-visible` — so a rule keyed on `:focus-visible` never fired and the browser painted its
|
|
583
|
+
own outline instead. On a ring arc or a funnel band an outline is the BOUNDING BOX, which stood
|
|
584
|
+
off the shape and read as a selection nobody asked for. `ds-donut-chart`, `ds-funnel-chart` and
|
|
585
|
+
`ds-line-chart` marks now suppress it on `:focus`. The keyboard indicator is untouched: it is a
|
|
586
|
+
stroke that follows the silhouette, and it still paints under `:focus-visible`.
|
|
587
|
+
|
|
588
|
+
- **`ds-column-chart`'s tooltip clears the value printed above the column.** The panel is anchored
|
|
589
|
+
to the column and opened 12px above it, which is exactly where `showValues` prints the figure,
|
|
590
|
+
so the two overlapped. It now clears the text as well as the mark; with `showValues` off the gap
|
|
591
|
+
is unchanged.
|
|
592
|
+
|
|
593
|
+
- **`ds-button` ignores the app-wide `DS_CONFIG.field.reserveMessage`.** The button takes the same
|
|
594
|
+
message line a field does, and with it took the field-wide default: an app calling
|
|
595
|
+
`provideDsConfig({ field: { reserveMessage: true } })` gave EVERY button an empty message row,
|
|
596
|
+
which turns the host from `inline-flex` into a column with a gap. One app found 125 buttons
|
|
597
|
+
across 45 files changed box that way, and nothing in the build, the types or the release notes
|
|
598
|
+
reported it. `reserveMessage` exists so a field row does not shift its neighbours as a message
|
|
599
|
+
appears, and a button is not in that column.
|
|
600
|
+
|
|
601
|
+
A button reserves only where you ask it to, with `[reserveMessage]="true"`. Fields are unchanged:
|
|
602
|
+
`DS_CONFIG.field.reserveMessage` still reaches every one of them, `ds-field-group` included.
|
|
603
|
+
|
|
604
|
+
The decision lives on the internal `DsMessageBase`, the shared message base the fields and the
|
|
605
|
+
button extend, as a protected `reserveFollowsFieldDefault`. The package root does not export it; a
|
|
606
|
+
subclass reaching it through the deep entry point and declaring that name stops building until it
|
|
607
|
+
renames the member or marks it `override`.
|
|
608
|
+
|
|
609
|
+
- **Two legends on one page no longer fight over the same selection.** A legend's isolate controls
|
|
610
|
+
are radios, and every legend named the same group — so a page with more than one chart formed a
|
|
611
|
+
single document-wide group: choosing a series in one legend cleared the selection in the others,
|
|
612
|
+
and only the last-rendered legend showed one at all. Each legend now names its own group.
|
|
613
|
+
|
|
614
|
+
A legend also always shows exactly one control chosen. A leftover partial state left the group
|
|
615
|
+
with nothing checked; it settles on `All`.
|
|
616
|
+
|
|
617
|
+
- **`ds-line-chart` holds its height when the last series is switched off.** The empty message
|
|
618
|
+
reserved the plot-height token alone, and the plot is an SVG sized by its ratio against the card
|
|
619
|
+
width — so on any card wider than that token the message box came up short and the card jumped.
|
|
620
|
+
It reserves the canvas ratio now, with the token as the floor for a very narrow card.
|
|
621
|
+
|
|
622
|
+
### What you can now DELETE
|
|
623
|
+
|
|
624
|
+
| your workaround | why it is unnecessary | replace with |
|
|
625
|
+
| --- | --- | --- |
|
|
626
|
+
| `--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' } })` |
|
|
627
|
+
| `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 |
|
|
628
|
+
|
|
3
629
|
## 0.13.1 — 2026-09-14
|
|
4
630
|
|
|
5
631
|
### Added
|