@ids-group-ltd/ids-design-system 0.10.3 → 0.11.0
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 +359 -40
- package/components.md +14 -6
- package/fesm2022/ids-group-ltd-ids-design-system.mjs +559 -464
- package/fesm2022/ids-group-ltd-ids-design-system.mjs.map +1 -1
- package/migrations/0.1.0.json +2 -1
- package/migrations/0.10.0.json +209 -32
- package/migrations/0.10.1.json +33 -9
- package/migrations/0.10.2.json +88 -22
- package/migrations/0.10.3.json +21 -4
- package/migrations/0.11.0.json +216 -0
- package/migrations/0.2.0.json +22 -9
- package/migrations/0.2.1.json +2 -1
- package/migrations/0.2.2.json +2 -1
- package/migrations/0.3.0.json +16 -10
- package/migrations/0.4.0.json +38 -14
- package/migrations/0.5.0.json +49 -25
- package/migrations/0.5.1.json +75 -33
- package/migrations/0.6.0.json +6 -2
- package/migrations/0.6.1.json +19 -1
- package/migrations/0.6.2.json +3 -1
- package/migrations/0.6.3.json +13 -4
- package/migrations/0.7.0.json +45 -26
- package/migrations/0.7.1.json +57 -19
- package/migrations/0.8.0.json +50 -12
- package/migrations/0.9.0.json +142 -23
- package/migrations/0.9.1.json +2 -1
- package/package.json +2 -1
- package/styles/_link.scss +1 -2
- package/styles/_overlay-motion.scss +0 -1
- package/types/ids-group-ltd-ids-design-system.d.ts +129 -59
- package/migrations/AUTHORING.md +0 -273
package/CHANGELOG.md
CHANGED
|
@@ -8,6 +8,270 @@ While the package is on `0.x`, minor releases may contain breaking changes.
|
|
|
8
8
|
|
|
9
9
|
## Unreleased
|
|
10
10
|
|
|
11
|
+
## 0.11.0 — 2026-08-26
|
|
12
|
+
|
|
13
|
+
### Added
|
|
14
|
+
|
|
15
|
+
- **`ds-checkbox` and `ds-radio-group` now show a validation state on the CONTROL, not only in the
|
|
16
|
+
message under it.** Both already rendered `ds-field-message` and already took `hint`/`error`/`warning`;
|
|
17
|
+
what was missing was the paint, so on a checkbox the only sign of an invalid state was the red line
|
|
18
|
+
underneath — which `color-not-only` says is not enough on its own.
|
|
19
|
+
**Two treatments, because the shapes differ.** The checkbox moves its **border** and nothing else: at
|
|
20
|
+
16px a tinted fill reads as "checked", so the shared field mixin — built for a 39px box with a
|
|
21
|
+
background — could not be reused. The radio group colours its **label**: when a required group is
|
|
22
|
+
unanswered no single radio is wrong, so reddening every ring would point five fingers at one
|
|
23
|
+
unanswered question. Both also carry `warning`.
|
|
24
|
+
**Deliberately NOT extended to `ds-radio`, `ds-switch` or `ds-slider`**, and the reasoning is on the
|
|
25
|
+
record rather than left to taste: a lone radio's choice belongs to its group, a switch applies on flip
|
|
26
|
+
rather than on submit, and a slider always holds a value inside bounds the control enforces itself —
|
|
27
|
+
"required" is not even expressible there. Counted across 39 usages in one consumer's three apps, the
|
|
28
|
+
only `[invalid]` binding in the whole codebase is on a radio group; every switch there carries a hint
|
|
29
|
+
and no error, and the slider is unused. Those three keep their message line, which is what they use.
|
|
30
|
+
|
|
31
|
+
- **`ds-sidenav` `brandRoute` — the brand row can lead home.** Set it and the mark plus wordmark become
|
|
32
|
+
one link; leave it unset and the row stays the plain block it was, because a logo that goes nowhere
|
|
33
|
+
should not be a link and every app decides for itself whether its mark is a way home. The link
|
|
34
|
+
announces itself as `"<brand>, home"`, overridable with **`brandLinkLabel`** — a wordmark alone does
|
|
35
|
+
not say where it goes. Router targets only, and `RouterLink` is instantiated only once `brandRoute` is
|
|
36
|
+
set, so an app with no router provided still renders the sidenav.
|
|
37
|
+
|
|
38
|
+
- **`ds-button` can say WHY it is refused, without a tooltip.** A greyed button that does not explain
|
|
39
|
+
itself is a dead end, and the only way to explain one was `[dsTooltip]` — reachable by mouse alone.
|
|
40
|
+
One consumer carried that workaround on three buttons; two sibling cases on `ds-menu-item` already
|
|
41
|
+
went away in 0.10.2 when it gained `[description]`. Which input to reach for depends on whether the
|
|
42
|
+
user can lift the refusal on this screen:
|
|
43
|
+
- **Standing refusal** — no permission, no integration, nothing here will change it. Set
|
|
44
|
+
**`disabledReason`** beside `disabled` and the reason renders as a second line INSIDE the button.
|
|
45
|
+
Setting it also flips HOW the button is disabled: **`aria-disabled="true"` instead of the native
|
|
46
|
+
attribute**, because a natively disabled button never takes focus and its description is therefore
|
|
47
|
+
never announced (measured: `document.activeElement` never becomes it, Tab skips it). The click is
|
|
48
|
+
swallowed in the handler instead, so **`(pressed)` still never fires** — verified against a live
|
|
49
|
+
control that does fire. Chrome's own accessibility tree reads name `"Approve invoice"`, description
|
|
50
|
+
`"Needs the Finance role"`, state disabled: the reason is the DESCRIPTION, not part of the name.
|
|
51
|
+
**Length is deliberately uncapped** — the text wraps and the button grows rather than truncating the
|
|
52
|
+
one thing that explains the refusal.
|
|
53
|
+
- **Temporary refusal** — the form simply is not filled in yet. Do NOT disable the button: leave it
|
|
54
|
+
live, judge validity in the submit handler, and carry the text UNDER it with **`hint` / `warning` /
|
|
55
|
+
`error`** — the same three inputs the fields take, resolved by the same `resolveFieldMessage` and
|
|
56
|
+
rendered by the same `ds-field-message`, with **`messageIcon`**, **`reserveMessage`** and the same
|
|
57
|
+
`DS_CONFIG.field.*` fallbacks. `reserveMessage` holds the line's height while it is empty, so a
|
|
58
|
+
button that gains an error mid-form does not shove the layout below it.
|
|
59
|
+
Also new: **`ariaDescribedBy`** on both `ds-button` and `ds-icon-button`, for pointing at a
|
|
60
|
+
description the app renders itself. On `ds-button` it is merged with the reason's own id.
|
|
61
|
+
**`ds-icon-button` gets no `disabledReason`** — icon-only leaves no room for a second line, and a
|
|
62
|
+
reason living only in the accessibility tree reproduces exactly the invisibility this closes.
|
|
63
|
+
**Nothing changes for a button that sets none of these.** Without `disabledReason` the native
|
|
64
|
+
`disabled` attribute stays and focus still skips it; without a message the host keeps the
|
|
65
|
+
`inline-flex` box every existing layout was built against. A message-bearing button becomes a column,
|
|
66
|
+
and since the host shrinks to fit, a message longer than the label widens the pair — button included,
|
|
67
|
+
exactly as a field's control spans its own message.
|
|
68
|
+
|
|
69
|
+
- **`--ds-button-shadow` and `--ds-button-shadow-hover` — the rest state finally has a hook.** Focus and
|
|
70
|
+
pressed already had one (`--ds-button-focus-shadow`, `--ds-button-pressed-shadow`); the resting shadow
|
|
71
|
+
did not, which is the only reason a consumer styling its option buttons as a screen's primary surface
|
|
72
|
+
still had a `::ng-deep ds-button button` rule at all — `background`, `color`, `font-weight` and
|
|
73
|
+
`border` were already tokens. That block becomes four token lines and the deep selector goes.
|
|
74
|
+
**Both default to `none`**, so nothing moves until an app asks. `-shadow-hover` falls back to
|
|
75
|
+
`-shadow`, so setting the resting one alone keeps the button steady under the pointer, and the focus
|
|
76
|
+
ring and pressed halo still win while those states are on.
|
|
77
|
+
|
|
78
|
+
- **`--ds-card-overflow`, so a card can hold a full-bleed child inside its own radius.** A child whose
|
|
79
|
+
background runs to the card's edge — an image, a grey footer strip — paints its square corners over
|
|
80
|
+
the card's rounded ones, and the host cannot fix it: the rounded box is `ds-card`'s inner element, out
|
|
81
|
+
of reach. Five screens in one consumer's portal carried the same
|
|
82
|
+
`:host ::ng-deep ds-card .card { overflow: hidden }` to get at it; that rule can go.
|
|
83
|
+
**Set `--ds-card-overflow: clip`** — `clip` rather than `hidden`, so the card does not also become a
|
|
84
|
+
scroll container.
|
|
85
|
+
**Opt-in, not the new default.** Clipping every card would cut the focus ring off any child sitting at
|
|
86
|
+
its edge: the ring is an outset shadow, and `ds-card` with `padding="none"` is the exact example
|
|
87
|
+
Foundations → Colour already gives for a clipping ancestor. Where a clipped card holds focusable
|
|
88
|
+
content, pair it with `data-focus="inset"` and the indicator moves inside the box instead of
|
|
89
|
+
disappearing.
|
|
90
|
+
|
|
91
|
+
- **`ds-table` column `link` — a cell that IS a link, so a row can say where it leads.** Until now the
|
|
92
|
+
only way in was clicking the row: `rowInteractive` gives the `<tr>` a tabindex and Enter/Space, but a
|
|
93
|
+
row has no href, so it never enters the tab order **as a link**, a screen reader announces a table
|
|
94
|
+
row, and Ctrl/Cmd-click cannot open it in a new tab. `interactive: true` only tinted the cell while
|
|
95
|
+
the row was hovered — invisible to a keyboard or touch user. Six lists in one consumer's portal
|
|
96
|
+
compensated by repeating the destination as a `View Details` item in the row's overflow menu, which
|
|
97
|
+
is a menu entry performing navigation rather than an action.
|
|
98
|
+
`link?: (row) => string | readonly unknown[] | null | undefined` returns an Angular route target and the column's
|
|
99
|
+
value renders as a real `<a>`. **`null` for a row leaves that cell plain text**, so a list where only
|
|
100
|
+
some records are reachable needs no second column. External URLs go through a `[dsCellTemplate]` —
|
|
101
|
+
`link` takes route targets only, and `RouterLink` is instantiated only once a column sets `link`, so
|
|
102
|
+
an app with no router provided still renders the table.
|
|
103
|
+
**Composes with `rowInteractive`**: the link stops its own click from reaching the row, so the name
|
|
104
|
+
navigates once and the rest of the row still fires the row handler. The two together cost **two tab
|
|
105
|
+
stops per row**, so on a long list prefer the link alone — which is the shape Roselli's "Don't Turn a
|
|
106
|
+
Table into an ARIA Grid Just for a Clickable Row" argues for, with the row click as an enhancement on
|
|
107
|
+
top of a control that already works.
|
|
108
|
+
|
|
109
|
+
### Changed
|
|
110
|
+
|
|
111
|
+
- **Every migration item now carries `action`, and the reasoning has moved out of its way.** The
|
|
112
|
+
manifests in `dist/ds/migrations/` — the ones your own upgrade tooling reads — gained three prose
|
|
113
|
+
fields per item: `action` is the imperative alone and the only field to execute, `appliesWhen` is
|
|
114
|
+
the boundary (which components, which bindings, and what is explicitly NOT affected), and
|
|
115
|
+
`pitfall` is the way to apply the item mechanically correctly and still ship a broken app. `note`
|
|
116
|
+
keeps what is left, the WHY. All **189 items across 22 published manifests** were rewritten by
|
|
117
|
+
hand for this: note prose fell from 12,547 words to 4,263, the **103 ALL-CAPS markers** that had
|
|
118
|
+
been standing in for the missing fields are gone, and no note runs past 120 words. Four new lint
|
|
119
|
+
rules hold it — `action` required (M039), no marker in a note (M040), the 120-word ceiling (M041)
|
|
120
|
+
and a key allowlist so a typo cannot sit unread (M042) — and `tools/migration-lint-selftest.mjs`
|
|
121
|
+
mutation-tests all 34 rules to prove none of them is dead. **If you read these files with your own
|
|
122
|
+
tooling, read `action` first and `pitfall` before you report an item done.** Nothing was removed:
|
|
123
|
+
every field that was there is still there, with the same name and meaning.
|
|
124
|
+
- **If you EXTEND a DS field, its message inputs now live one class further up.** `hint`, `error`,
|
|
125
|
+
`warning`, `messageIcon`, `reserveMessage` and `reserveMessageResolved` moved out of `DsFieldBase`
|
|
126
|
+
into a new `DsMessageBase`, which `DsFieldBase` extends — so `ds-button` can take the message half
|
|
127
|
+
without also inheriting `errors`, `invalid` and `touched`, which describe a form control's validation
|
|
128
|
+
state and mean nothing on a button. **`DsFieldBase`'s own surface is unchanged**: every one of those
|
|
129
|
+
members still resolves through it, with the same names, types and defaults. Called out only because
|
|
130
|
+
`npm run class-surface` cannot see a member that moved to a base class — it reports members per class
|
|
131
|
+
and this is the case it warns about. A subclass redeclaring one of these collides exactly as it did
|
|
132
|
+
before; subclassing a DS component stays unsupported (`components.md` § Components).
|
|
133
|
+
|
|
134
|
+
- **If you EXTEND a DS component, six of them grew members.** `npm run class-surface` against
|
|
135
|
+
0.10.3: `ButtonComponent` gained `disabledReason`, `ariaDescribedBy`, `softDisabled`, `message`,
|
|
136
|
+
`fieldMessage`, `hasMessageRow`, `describedBy`, `hintId`, `reasonId` and `uid`;
|
|
137
|
+
`IconButtonComponent` gained `ariaDescribedBy`; `TableComponent` grew one member, `cellLink`, which
|
|
138
|
+
backs the new `link` column by resolving a column’s `link(row)` to the value the template binds;
|
|
139
|
+
`SidenavComponent` gained `brandRoute`, `brandLinkLabel` and the protected `brandAriaLabel`; and
|
|
140
|
+
`CheckboxComponent` and `RadioGroupComponent` each gained the protected `controlState`.
|
|
141
|
+
A subclass that happens to declare the same name now fails with
|
|
142
|
+
TS4114 (“must have an ‘override’ modifier”), or TS2415 if the signature differs — and `protected` is
|
|
143
|
+
no protection, since a redeclared protected member collides exactly as a public one does.
|
|
144
|
+
Subclassing a DS component stays unsupported (`components.md` § Components); compose instead.
|
|
145
|
+
|
|
146
|
+
### Fixed
|
|
147
|
+
|
|
148
|
+
- **A `ds-sidenav-item` with no destination was `<a href="#">`, so clicking it navigated.** With neither
|
|
149
|
+
`routerLink` nor `href` the template fell back to `href="#"` — which rewrites the URL and throws the
|
|
150
|
+
scroll position away, on every click. That is what made a sidenav SPECIMEN move the docs page.
|
|
151
|
+
It renders a `<button type="button">` now: an item that only emits `activate` is a button, not a link.
|
|
152
|
+
Verified on the built docs — the element is a `BUTTON`, carries no `href`, and a click leaves both the
|
|
153
|
+
URL and the scroll position untouched. **Styling is unaffected** (the rules are class-based, and the
|
|
154
|
+
UA's button chrome is reset on `.item`), and both `<a>` variants are unchanged.
|
|
155
|
+
**If you relied on the anchor**: an item you want to be a link needs `href` or `routerLink`, which it
|
|
156
|
+
always did — `href=""` no longer silently becomes `#`.
|
|
157
|
+
|
|
158
|
+
- **`ds-table`'s pager took no inset, so it sat out of line with the columns and on the container's
|
|
159
|
+
border.** The footer carried `padding-top` alone — no horizontal, no bottom — while every cell is
|
|
160
|
+
inset by `--ds-table-cell-pad-x`. That padding is what insets the content of a `padding: 0` container,
|
|
161
|
+
which is how tables are normally placed, so the summary line landed **16px left of the column text**
|
|
162
|
+
with its baseline **on the border**. Measured before: footer padding `12px 0 0 0`, footer content at
|
|
163
|
+
0 against the cells' 16. After: `12px 16px 12px`, footer content at 16 — aligned — and the summary
|
|
164
|
+
21px clear of the bottom edge. **It follows `--ds-table-cell-pad-x` with the cells**, verified: set
|
|
165
|
+
the hook to 40px and both move together, so a retuned table keeps its footer in line.
|
|
166
|
+
|
|
167
|
+
- **`ds-banner`'s body had no size of its own, so a 16px page rendered it LARGER than its own 14px
|
|
168
|
+
title** — and in `compact` the title and body ran together with nothing between them. Both came from
|
|
169
|
+
the same place: the gap lived on the TITLE, where it also fired with no body under it and could not
|
|
170
|
+
fire at all in `compact` (which zeroes that margin). The gap now belongs to the body — it appears only
|
|
171
|
+
when a body is actually projected — and the body takes `--font-size-s`, overridable through the new
|
|
172
|
+
**`--ds-banner-body-font-size`**. Measured: title 14px and body 14px in a 16px context (was 16px);
|
|
173
|
+
4px between title and body in `compact` (was 0px); a title-only `compact` banner unchanged, because
|
|
174
|
+
the wrapper is `:empty` and contributes nothing.
|
|
175
|
+
**The "compact has no body" line in the docs was never true** — nothing was ever hidden, and 17 of
|
|
176
|
+
one consumer's compact banners project one. It is a supported pairing now rather than a claim.
|
|
177
|
+
|
|
178
|
+
- **A `compact` banner whose title was longer than its column overflowed the column and cut the text
|
|
179
|
+
with nothing to show it had been cut.** `compact` is the one-line strip, so its title carries
|
|
180
|
+
`white-space: nowrap` — but nothing made it DEGRADE: there was no `text-overflow`, and the host had
|
|
181
|
+
no `min-width: 0`, so as a flex or grid ROW item it refused to shrink below its own min-content.
|
|
182
|
+
Measured: a **260px column held a 319px banner**, with the title clipped mid-word and no ellipsis.
|
|
183
|
+
The title now ellipsises and the host can be squeezed — re-measured in the same 260px column, the
|
|
184
|
+
banner is 227px and the title ends in `…`. A non-compact banner is unaffected: its title still wraps
|
|
185
|
+
(two lines at 260px) rather than clipping, which is the difference between the two variants.
|
|
186
|
+
**This is what was behind the "crooked banner" report**, not the title alignment it was filed as —
|
|
187
|
+
that part did not reproduce, and is covered by the alignment entry above.
|
|
188
|
+
|
|
189
|
+
- **`ds-banner` no longer inherits its alignment from whatever it is dropped into.** Reported as "the
|
|
190
|
+
title is centred while the body stays at start" (mm-broker). The DS does not centre the title — measured
|
|
191
|
+
across all twelve banners in the docs, in both layouts, title and body both compute `start` and there
|
|
192
|
+
is no `text-align` anywhere in the component. What IS true is the underlying defect: the banner owned
|
|
193
|
+
no alignment at all, so a centred ancestor dragged **both** of its text blocks along (measured: both
|
|
194
|
+
flip to `center` under a centred parent). It now sets `text-align: start` on its own box, so a banner
|
|
195
|
+
reads as one alignment wherever it sits. If you were centring a banner deliberately by centring its
|
|
196
|
+
container, that stops working — say so and it becomes an input.
|
|
197
|
+
|
|
198
|
+
- **`ds-sidenav-footer`'s account menu now uses `ds-menu-divider`, so the divider tokens reach it.** It
|
|
199
|
+
hand-rolled a `div` with local styles instead, which meant `--ds-menu-divider-color` and
|
|
200
|
+
`--ds-menu-divider-spacing` did nothing there — an override written against the documented tokens
|
|
201
|
+
silently skipped the one menu the DS ships itself. **The line also sat 6px from its neighbours where
|
|
202
|
+
every other menu puts it 2px away**, because the hand-rolled rule added `--space-1` of its own on top
|
|
203
|
+
of the menu's gap. It now behaves like the component it should always have been: **the divider adds
|
|
204
|
+
no space of its own** — measured 2px above and 2px below the line, which is exactly the gap between
|
|
205
|
+
any two ordinary items, so the line takes one row's place instead of pushing the rows apart. Reported
|
|
206
|
+
as UNEVEN spacing; that part did not reproduce — the gaps were symmetric both before and after. The
|
|
207
|
+
defect was that there was extra spacing at all.
|
|
208
|
+
|
|
209
|
+
- **`ds-menu-divider` sits FLUSH now — a boundary is not a row, so it takes no space of its own.** Its
|
|
210
|
+
own padding already defaulted to 0 (0.8.0), but `ds-menu` is a flex column and its row gap still
|
|
211
|
+
landed above AND below the line, so every divider sat one row's width away from the items it
|
|
212
|
+
separates. It now cancels that gap: **measured 0px above the line and 0px below**, while two ordinary
|
|
213
|
+
items keep their 2px. `--ds-menu-divider-spacing` is untouched and still the way to add air —
|
|
214
|
+
verified: `8px` gives exactly 8px each side, and clearing it returns to flush. A divider used outside
|
|
215
|
+
a `ds-menu` is unaffected (the cancel falls back to `0px`).
|
|
216
|
+
**If you set `--ds-menu-divider-spacing`** — including via 0.8.0's restore recipe — **your boundary
|
|
217
|
+
tightens by the menu's row gap**, because that gap no longer stacks on top of your value. Add it back
|
|
218
|
+
in your own value if you want the old measurement exactly.
|
|
219
|
+
|
|
220
|
+
- **`ds-w3w` rendered a space its own format does not have.** The pill showed
|
|
221
|
+
`/// daring.lion.race`; a what3words identifier is `///daring.lion.race`, flush, which is what the
|
|
222
|
+
component's own `aria-label` has said all along — so the screen and the accessible name disagreed.
|
|
223
|
+
The cause was the template's line breaks: the prefix sat on its own line inside the mark element, and
|
|
224
|
+
in inline flow that leading/trailing whitespace collapses to a rendered space. Measured at the default
|
|
225
|
+
size, the pill was **7.8px wider** than the format allows. The mark row is a flex container now, which
|
|
226
|
+
drops whitespace-only text nodes outright, so the identifier renders flush and the template stays free
|
|
227
|
+
to be formatted for reading. No API change, and nothing to do on your side.
|
|
228
|
+
|
|
229
|
+
- **Nine defects in six already-published manifests, and a repo upgraded before today may be holding
|
|
230
|
+
the result.** The prose split above rewrote every item; this is the separate, smaller set where the
|
|
231
|
+
DATA was wrong — found by auditing each manifest against the code of its own release. It matters
|
|
232
|
+
because these files are executed: your upgrade tooling read them, acted, and reported done.
|
|
233
|
+
**Three changes had no item at all.** `0.2.0` never filed the `--surface-subtle` →
|
|
234
|
+
`--surface-subtitle` rename, so an override still naming the old token resolves to nothing and says
|
|
235
|
+
nothing. `0.9.0` never filed the six inputs whose declared type widened from `InputSignal` to
|
|
236
|
+
`InputSignalWithTransform` (`min`/`max`/`maxLength` on `ds-input`, `min`/`max` on
|
|
237
|
+
`ds-number-stepper`, `maxLength` on `ds-textarea`) — the TS2322 an explicit annotation hits and the
|
|
238
|
+
TS2416 a subclass hits had no explanation anywhere. `0.10.0` never filed
|
|
239
|
+
`ModalService.confirm({ tone: 'error' })` gaining the modal's error badge in the header.
|
|
240
|
+
**Two instructions were wrong, so following them edited the wrong thing.** `0.7.1`’s à-la-carte
|
|
241
|
+
`@use` lines were written as bare `styles/…` specifiers, which resolve only inside this repo and
|
|
242
|
+
fail from an app; they are package-qualified now. And `0.7.1`’s modal `.title` was filed as a
|
|
243
|
+
`class-rename` to `.heading` when no rename happened — it is a `behavior` item now, so anyone who
|
|
244
|
+
renamed that class did so on our word and can put it back.
|
|
245
|
+
**One `verify` certified a bug as correct.** `0.8.0` said an unset `sortMode` resolves to `server`.
|
|
246
|
+
It resolves to `client`, so a server-paged table left unset sorts only the rows in hand — and the
|
|
247
|
+
check passed anyway. That release’s item now says to declare `sortMode="server"` explicitly.
|
|
248
|
+
**Three items searched too few file types.** `0.5.1`’s two `variant` remaps and `0.10.0`’s
|
|
249
|
+
`floating` removal were marked template-only, so a `variant=` sitting in a stylesheet or a `.ts`,
|
|
250
|
+
and the five dead floating-label tokens (`--field-h-floating` and the four `--field-floating-*`),
|
|
251
|
+
were never looked for. Their `surface` now names style and TypeScript too.
|
|
252
|
+
**What to do:** if your last upgrade ran before this release AND crossed one of those six versions,
|
|
253
|
+
re-run just those items — `migrations/<version>.json` now carries them right, and nothing else in
|
|
254
|
+
those files changed meaning. Also corrected: `0.10.2`’s two `maxVisibleChips` items now declare
|
|
255
|
+
that they supersede `0.10.0#max-visible-chips-zero-inverted`, which an upgrade stepping through both
|
|
256
|
+
had been applying for nothing.
|
|
257
|
+
**Pure upside in the same pass: sixteen more rows** in the "What you can now DELETE" tables of
|
|
258
|
+
0.6.1, 0.7.1, 0.8.0, 0.9.0, 0.10.0 and 0.10.3 — workarounds those releases made redundant and never
|
|
259
|
+
listed.
|
|
260
|
+
|
|
261
|
+
### What you can now DELETE
|
|
262
|
+
|
|
263
|
+
None of this is required — skipping it leaves working code that is merely redundant. Each row is a
|
|
264
|
+
workaround written against a hook that only landed in this release.
|
|
265
|
+
|
|
266
|
+
| If you have | Delete it, because |
|
|
267
|
+
| --- | --- |
|
|
268
|
+
| A local rule padding `.pagination-footer`, or a `TODO(ds-table-footer-padding)` marker | The footer is inset by the cells' own padding now — horizontally by `--ds-table-cell-pad-x`, and the same at the bottom as the top. A local rule doubles it. |
|
|
269
|
+
| `dsTooltip` on a `ds-button` that is `disabled`, carrying the reason it is refused | `disabledReason` puts the reason inside the button AND makes it focusable, so a keyboard and a screen reader reach it too — which a tooltip never did. Scope it: a tooltip that merely NAMES the action stays. For a refusal the user can lift by filling the form in, drop `disabled` entirely and use `error`/`warning`/`hint`. |
|
|
270
|
+
| `::ng-deep ds-card .card` with `overflow: hidden`, to clip a full-bleed child inside the card radius | `--ds-card-overflow: clip` — and pair it with `data-focus="inset"` where the clipped card holds focusable content |
|
|
271
|
+
| `::ng-deep ds-button button` kept alive only by a resting `box-shadow` | `--ds-button-shadow` (and `--ds-button-shadow-hover`) on the host |
|
|
272
|
+
| A `View Details` `ds-menu-item` in `rowActions` that only repeats where the row already leads | `link` on the column that names the record — a real `<a>`, tabbable and Ctrl/Cmd-clickable, announced as a link rather than as a table row |
|
|
273
|
+
|
|
274
|
+
|
|
11
275
|
## 0.10.3 — 2026-08-24
|
|
12
276
|
|
|
13
277
|
### Added
|
|
@@ -35,13 +299,14 @@ While the package is on `0.x`, minor releases may contain breaking changes.
|
|
|
35
299
|
every computed shadow is final — found exactly these two and nothing else in the library. The reset
|
|
36
300
|
stays scoped to the field element, so `clear-btn` and `password-toggle` inside the same box keep
|
|
37
301
|
their own rings; they are real tab stops.
|
|
38
|
-
- **The token reference was missing
|
|
302
|
+
- **The token reference was missing 14 public tokens that were always overridable.**
|
|
39
303
|
`tools/extract-tokens.mjs` searched for the literal `var(--ds-`, so any resolver whose declaration
|
|
40
304
|
wrapped across lines put a newline between `var(` and the name and the token silently never reached
|
|
41
305
|
the reference. Newly listed and described: `--ds-container-pad-x`, `--ds-multi-select-border-color`
|
|
42
306
|
(+`-focus`), `--ds-segmented-selected-bg-color` / `-label-color` / `--ds-segmented-radius`,
|
|
43
|
-
`--ds-time-picker-option-bg-color-selected` / `-text-color-selected` / `-bg-color-hover`,
|
|
44
|
-
`--ds-time-picker-trigger-bg-color` / `-border` / `-color
|
|
307
|
+
`--ds-time-picker-option-bg-color-selected` / `-text-color-selected` / `-bg-color-hover`,
|
|
308
|
+
`--ds-time-picker-trigger-bg-color` / `-border` / `-color`, `--ds-field-message-icon-offset` and
|
|
309
|
+
`--ds-time-picker-focus-shadow`. Nothing changed in the components —
|
|
45
310
|
these overrides already worked; only the documentation was blind to them.
|
|
46
311
|
- **Two buttons inside portaled panels had no focus indicator, and one panel had square corners — a
|
|
47
312
|
private token read from outside the host that declares it.** `ds-date-picker`'s `.period-trigger`
|
|
@@ -67,6 +332,16 @@ While the package is on `0.x`, minor releases may contain breaking changes.
|
|
|
67
332
|
ring on `:focus-within` without silencing the base rule; it replaces the hand-kept shell list in
|
|
68
333
|
`styles/_focus.scss` that had been wrong for two releases.
|
|
69
334
|
|
|
335
|
+
### What you can now DELETE
|
|
336
|
+
|
|
337
|
+
None of this is required — skipping it leaves working code that is merely redundant. Each row is a
|
|
338
|
+
workaround this release made unnecessary. Generated from the release manifest’s `deleteList`.
|
|
339
|
+
|
|
340
|
+
| If you have | Delete it, because |
|
|
341
|
+
| --- | --- |
|
|
342
|
+
| `ds-input input`, `ds-textarea textarea`, `--ds-input-focus-shadow`, `box-shadow: none` | A rule killing one of the two focus rings a ds-input or ds-textarea used to paint - typically box-shadow: none on the inner input, or --ds-input-focus-shadow re-declared as none to hide the doubling. Replace with: nothing - the component now paints one ring on its own. |
|
|
343
|
+
| `.search-clear`, `ds-search`, `:focus-visible`, `box-shadow` | A focus rule you added to the ds-search clear button because it showed no indicator at all - the shell-wide reset 0.10.2 used silenced that tab stop too. Every shell names the one control it silences now, so the button keeps its own ring. Replace with: nothing - the component paints it. |
|
|
344
|
+
|
|
70
345
|
## 0.10.2 — 2026-08-24
|
|
71
346
|
|
|
72
347
|
### Added
|
|
@@ -254,7 +529,7 @@ While the package is on `0.x`, minor releases may contain breaking changes.
|
|
|
254
529
|
- **The shipped migration manifests say WHERE to look, not only what changed — and a lint now holds
|
|
255
530
|
them to it.** `migrations/<version>.json` (the files `dist/ds/migrations/` carries into your
|
|
256
531
|
`node_modules`, which the auto-update plugin runs) gained `surface`, `detect`, `verify`, `restore`,
|
|
257
|
-
`supersedes
|
|
532
|
+
`supersedes`, and a structured `deleteList`. The reason is a consumer upgrade that
|
|
258
533
|
went 0.6.0 → 0.10.1 and passed over two entries in silence: `0.7.1`'s
|
|
259
534
|
`table-sortkey-non-null-when-unsorted` pointed at `ds-table[sortKey]`, which appears in nobody's
|
|
260
535
|
template, while the code that breaks was their own store —
|
|
@@ -267,7 +542,8 @@ While the package is on `0.x`, minor releases may contain breaking changes.
|
|
|
267
542
|
got a `surface`, every behavioural one a `verify`, every changed default a `restore`, and the 32
|
|
268
543
|
prose `DELETE-LIST:` lines became `deleteList` arrays with a greppable `find` each — four of those
|
|
269
544
|
"lines" turned out to be the words "the DELETE-LIST" inside ordinary prose. Two default flips that
|
|
270
|
-
reverse each other
|
|
545
|
+
reverse each other are linked by `supersedes` on the LATER item, one way only because a published
|
|
546
|
+
manifest cannot know its own future: `0.7.0` / `0.7.1` on `reserveMessage`, and `0.8.0` / `0.9.0`
|
|
271
547
|
on the table's sort mode. `npm run migration-lint` enforces the contract with no warning level, and
|
|
272
548
|
both the release preflight and the PR gate run it, so a manifest nobody can act on stops the
|
|
273
549
|
pipeline instead of reaching a consumer. Three CHANGELOG blocks also gained the "What you can now
|
|
@@ -380,11 +656,43 @@ workaround written against a hook that only landed in this release.
|
|
|
380
656
|
| `--ds-button-label-color-disabled` pinned on a tonal button to make its disabled state visible, most likely only in the dark theme | The default disabled-label recipe carries it |
|
|
381
657
|
| `count.toLocaleString('en-US')` (or any hand-rolled formatting) inside a `ds-stat` binding, because `[value]="count \| number"` would not typecheck | The pipe binds now, and it reads `LOCALE_ID` instead of a pinned locale |
|
|
382
658
|
| A `::ng-deep ds-table tr:hover .some-cell { color; text-decoration }` rule to make one cell read as the row's link target | `interactive: true` on that column, retuned with `--ds-table-cell-link-color` / `--ds-table-cell-link-decoration` |
|
|
659
|
+
| `ds-icon`, `field-message`, `align-items: center` | A glyph rendered by hand beside a field's error or warning text, or a margin nudge added to line one up against the old centred message row. Replace with: the built-in state glyph (error / warning / success carry one now), retuned through DS_CONFIG.field.stateIcons or messageIcon, with --ds-field-message-icon-gap / -offset for the spacing. |
|
|
660
|
+
| `box-shadow: none`, `--ds-field-focus-shadow` | A rule that killed one of the two focus rings a field used to paint - on an inner input, or by re-declaring the field focus shadow. SCOPE, and it matters: this release suppresses the inner ring on ds-search, ds-autocomplete, ds-date-picker, ds-number-stepper and ds-field-group ONLY. A workaround on ds-input or ds-textarea is still load-bearing here - deleting it brings the double ring back. Leave those two until you are on the release that names them. Also leave any rule you wrote against the universal :where(:focus-visible) base indicator itself: that rule is still the one this library ships. Replace with: nothing: the field paints one ring now. |
|
|
661
|
+
| `padding-block`, `line-height`, `option-label` | A padding or line-height override added to an option label, a clipped table cell or a breadcrumb to stop the descenders being shaved. Replace with: nothing: the clip carries a --space-1 margin now, at the same row height. |
|
|
383
662
|
|
|
384
663
|
## 0.10.1 — 2026-08-20
|
|
385
664
|
|
|
386
665
|
### Removed
|
|
387
666
|
|
|
667
|
+
- **The seven inputs every field shares are declared once, in `DsFieldBase`.** `hint`, `error`,
|
|
668
|
+
`warning`, `errors`, `invalid`, `touched` and `reserveMessage` — plus the `reserveMessageResolved`
|
|
669
|
+
helper — were hand-copied into all fourteen fields, 98 declarations. **Nothing about the public API
|
|
670
|
+
changed:** every input keeps its name, type, default and documentation, and the docs API tables are
|
|
671
|
+
byte-identical apart from the eight new `success` rows (verified by diffing the generated
|
|
672
|
+
reference: 0 lost, 8 gained).
|
|
673
|
+
**Why it is worth knowing anyway:** the duplication had already drifted twice — `success` was
|
|
674
|
+
missing from eight fields, and `ds-date-picker` had quietly moved to a different `invalid` source.
|
|
675
|
+
A new state added to the base now reaches every field at once.
|
|
676
|
+
`DsControlValueAccessor` and `DsBooleanControlValueAccessor` extend the base (so single inheritance
|
|
677
|
+
still holds for the thirteen fields that already extended one of them) and `ds-radio` extends it
|
|
678
|
+
directly. Only the UNIVERSAL inputs moved: `success`, `label`, `required` and `optional` stay on the
|
|
679
|
+
components, because they exist on 9, 9, 7 and 5 fields respectively and lifting them would hand a
|
|
680
|
+
checkbox a `success` or a slider a `label` it never had.
|
|
681
|
+
|
|
682
|
+
- **`ds-icon-button` with `variant="standard"` mixes its disabled glyph toward the surface too.**
|
|
683
|
+
New default on that variant only: `color-mix(in srgb, <icon colour> 40%, var(--surface-default))`.
|
|
684
|
+
Same defect as ghost, and it matters more here — there is no word to read, just a 16px glyph.
|
|
685
|
+
Measured: light **4.17 → 5.19:1**, dark **1.46 → 3.58:1**. Light was already healthy, because the
|
|
686
|
+
enabled glyph is `--text-secondary` at OKLCH L 35% and the old recipe moved it to L 70%; **dark was
|
|
687
|
+
the break**, where the enabled glyph is L 80% and a disabled one pinned at L 70% left ten points
|
|
688
|
+
and a 1.46:1 gap.
|
|
689
|
+
**Scoped to `standard` deliberately, and this is the trap worth knowing:** the resolver is declared
|
|
690
|
+
once on the base and no variant overrode it, so touching the base would have hit `filled` too —
|
|
691
|
+
whose glyph is `--c-on`, i.e. white, and white mixed into a white surface does not move at all,
|
|
692
|
+
which would have put an invisible white glyph on a pale disabled fill. `filled`, `tonal` and
|
|
693
|
+
`outlined` keep the base recipe unchanged. Consumers who set
|
|
694
|
+
`--ds-icon-button-icon-color-disabled` are unaffected.
|
|
695
|
+
|
|
388
696
|
- **`--opacity-muted` is gone from the token scale.** It was the last token in the file that no
|
|
389
697
|
component read: the disabled states moved onto `--text-disabled` + `--opacity-disabled` in
|
|
390
698
|
0.10.0, and it had been sitting there since, labelled a legacy alias. Keeping a dead number in a
|
|
@@ -1163,35 +1471,6 @@ None of this is required — skipping it leaves working code that is merely redu
|
|
|
1163
1471
|
|
|
1164
1472
|
### Changed
|
|
1165
1473
|
|
|
1166
|
-
- **The seven inputs every field shares are declared once, in `DsFieldBase`.** `hint`, `error`,
|
|
1167
|
-
`warning`, `errors`, `invalid`, `touched` and `reserveMessage` — plus the `reserveMessageResolved`
|
|
1168
|
-
helper — were hand-copied into all fourteen fields, 98 declarations. **Nothing about the public API
|
|
1169
|
-
changed:** every input keeps its name, type, default and documentation, and the docs API tables are
|
|
1170
|
-
byte-identical apart from the eight new `success` rows (verified by diffing the generated
|
|
1171
|
-
reference: 0 lost, 8 gained).
|
|
1172
|
-
**Why it is worth knowing anyway:** the duplication had already drifted twice — `success` was
|
|
1173
|
-
missing from eight fields, and `ds-date-picker` had quietly moved to a different `invalid` source.
|
|
1174
|
-
A new state added to the base now reaches every field at once.
|
|
1175
|
-
`DsControlValueAccessor` and `DsBooleanControlValueAccessor` extend the base (so single inheritance
|
|
1176
|
-
still holds for the thirteen fields that already extended one of them) and `ds-radio` extends it
|
|
1177
|
-
directly. Only the UNIVERSAL inputs moved: `success`, `label`, `required` and `optional` stay on the
|
|
1178
|
-
components, because they exist on 9, 9, 7 and 5 fields respectively and lifting them would hand a
|
|
1179
|
-
checkbox a `success` or a slider a `label` it never had.
|
|
1180
|
-
|
|
1181
|
-
- **`ds-icon-button` with `variant="standard"` mixes its disabled glyph toward the surface too.**
|
|
1182
|
-
New default on that variant only: `color-mix(in srgb, <icon colour> 40%, var(--surface-default))`.
|
|
1183
|
-
Same defect as ghost, and it matters more here — there is no word to read, just a 16px glyph.
|
|
1184
|
-
Measured: light **4.17 → 5.19:1**, dark **1.46 → 3.58:1**. Light was already healthy, because the
|
|
1185
|
-
enabled glyph is `--text-secondary` at OKLCH L 35% and the old recipe moved it to L 70%; **dark was
|
|
1186
|
-
the break**, where the enabled glyph is L 80% and a disabled one pinned at L 70% left ten points
|
|
1187
|
-
and a 1.46:1 gap.
|
|
1188
|
-
**Scoped to `standard` deliberately, and this is the trap worth knowing:** the resolver is declared
|
|
1189
|
-
once on the base and no variant overrode it, so touching the base would have hit `filled` too —
|
|
1190
|
-
whose glyph is `--c-on`, i.e. white, and white mixed into a white surface does not move at all,
|
|
1191
|
-
which would have put an invisible white glyph on a pale disabled fill. `filled`, `tonal` and
|
|
1192
|
-
`outlined` keep the base recipe unchanged. Consumers who set
|
|
1193
|
-
`--ds-icon-button-icon-color-disabled` are unaffected.
|
|
1194
|
-
|
|
1195
1474
|
- **`avatarTint` switches from OKLCH to `hsl(H 50% 62%)` with white initials, always.** The seeded
|
|
1196
1475
|
tints read as dull, and every set of initials came out black. The auto-contrast was not the fault:
|
|
1197
1476
|
measured across the hue circle, the old `oklch(62% 0.14 h)` put every hue's luminance between 0.218
|
|
@@ -1366,6 +1645,12 @@ None of this is required — skipping it leaves working code that is merely redu
|
|
|
1366
1645
|
| An override retuning `--opacity-muted` to compensate for a washed-out disabled state. That token is a de-emphasis level for hints and secondary text and carries no disabled state at all - and on `ds-button` / `ds-icon-button` it was always inert, because neither ever read it. | `--ds-button-label-color-disabled` / `--ds-icon-button-icon-color-disabled` |
|
|
1367
1646
|
| A `::ng-deep ds-table { .table th, .table td { width: 1%; white-space: nowrap } }` override - the shrink-to-content idiom. | `TableColumn.width: 'content'` |
|
|
1368
1647
|
| A `stopPropagation()` on a control inside a clickable row, added so the row would not steal the control's KEY. Read each hit before deleting: a CLICK still bubbles (`onRowClick` only skips a target inside an `<input>`), so a click-path guard stays. | nothing on the key path - `onRowKey` now requires `target === currentTarget` |
|
|
1648
|
+
| `sortChange`, `sortKey`, `sortDir`, `setTimeout` | Host code that re-bound the sort after a cleared sort, written because the header lost its indicator whenever the host default equalled the last value Angular had written. The marked state is a linkedSignal over both inputs now. Replace with: nothing - answer the cleared sort with your default and stop there. |
|
|
1649
|
+
| `.visually-hidden`, `clip: rect`, `clip-path: inset(50%)` | Your own .visually-hidden definition, or a rule targeting the pending row glyph by name, written because the class ds-password-rules used was declared by no stylesheet and its screen-reader text rendered visibly. One shared mixin backs all four components now. Replace with: nothing - the components carry the class themselves. |
|
|
1650
|
+
| `ds-timeline-item`, `margin-top`, `margin: -` | A margin you added on ds-timeline-item or its node to pull the marker onto the heading centre. The component pulls the node column up itself now, so your compensation double-applies. Replace with: nothing - remove the margin. |
|
|
1651
|
+
| `--field-h-floating`, `--field-floating-label-fs`, `--field-floating-label-lh`, `--field-floating-label-top`, `--field-floating-pad-t` | An override of one of the five floating-label tokens. They were :root declarations backing the floating variant, which this release removed, so the declaration now sets a custom property nothing reads. Replace with: nothing - delete the declaration. |
|
|
1652
|
+
| `new Event('input'`, `dispatchEvent`, `querySelector` | A query for `ds-autocomplete`'s inner `<input>` plus a synthetic `input` event, clearing leftover filter text after a pick. Replace with: `clear()` - and the component clears that text itself now. |
|
|
1653
|
+
| A `::ng-deep` override on `ds-field-group` forcing the invalid `border-error` back to red, or suppressing a segment fill inside a group | Both are fixed in the component. Replace with: nothing - both overrides are redundant. |
|
|
1369
1654
|
|
|
1370
1655
|
## 0.9.1 — 2026-08-10
|
|
1371
1656
|
|
|
@@ -1419,24 +1704,29 @@ redundant.
|
|
|
1419
1704
|
| `.button.button.button { … }` or rules against `.v-outline` / `.c-secondary` | `ds-button` reflects `[data-variant]` and `[data-color]` on the HOST. Use `ds-button[data-variant="outline"]` |
|
|
1420
1705
|
| `--radius-sm: 0` to square a checkbox | `--ds-checkbox-radius` |
|
|
1421
1706
|
| `.title.title { font-size }` inside a modal | `--ds-modal-title-font-size` |
|
|
1422
|
-
| Pagination label type overrides | `--ds-pagination-label-*` |
|
|
1707
|
+
| Pagination label type overrides — a rule on `ds-pagination` setting `--ds-pagination-label-*` | `--ds-pagination-label-*` |
|
|
1423
1708
|
| `.size { display: none }` on a pager | `[showPageSize]="false"` — and it is now forwarded through `ds-table` too |
|
|
1424
1709
|
| `.actions:empty { display: none }` on a modal | The library already ships it |
|
|
1425
1710
|
| `--ds-modal-divider: transparent`, plus whatever you rewrote the modal padding to afterwards | `[dividers]="false"` — it drops the rules *and* the padding that existed to clear them |
|
|
1426
|
-
| A defensive hover rule
|
|
1711
|
+
| A defensive `:hover` rule guarding the selected dropdown row — a selector naming `is-selected` | The `:not(.is-selected)` branch already handles it |
|
|
1427
1712
|
| `ds-menu-divider { padding: 0 }` | `--ds-menu-divider-spacing`, which already defaults to 0 |
|
|
1428
1713
|
| A dozen scattered `--ds-*-radius: 0` | For a fully square brand, four lines: `--radius-sm/md/lg/xl: 0` (leave `--radius-pill`). Measured — the three ROLES alone leave options, clear buttons and dropdown panels rounded; they are the tool for squaring one family and keeping another. Worked example on the Theming page |
|
|
1429
1714
|
| A global rule squaring `.ds-overlay-pane` | Radius and elevation roles now travel onto portaled panes when the host overrides them |
|
|
1430
1715
|
| Absolutely positioning a search glyph over an autocomplete, or hiding `.autocomplete-chevron` | `dsAutocompletePrefix` and `[showChevron]="false"` |
|
|
1431
1716
|
| Querying the autocomplete's inner `<input>` and dispatching a synthetic `input` event to clear it | `clear()` |
|
|
1432
|
-
| A hand-built KPI tile
|
|
1717
|
+
| A hand-built KPI tile — a `kpi` block pairing your own markup with `ds-badge`, where `ds-stat` now fits | `ds-stat` takes a projected `[dsStatValue]` |
|
|
1433
1718
|
| A pinned `--ds-search-height` (or any sibling) to get a shorter control row | `density="compact"` on the container — every field control is 32px there, measured |
|
|
1434
1719
|
| A hand-rolled `.scrim` + `.panel` dialog, written because the modal header could not hold a badge or a second line | `ds-modal` projects `[title-badge]` and takes a `subtitle`. You get back the focus trap, focus restore, the scroll lock, Escape and the footer |
|
|
1435
1720
|
| `[value]="f.x().value()" (valueChange)="f.x().value.set($event)"` on every field of a signal form | `[formField]="f.x"` — the control implements the contract already |
|
|
1436
1721
|
| `white-space: normal` forced onto a badge in a table cell | `--ds-badge-white-space` |
|
|
1437
1722
|
| `::ng-deep .card { height: 100% }` for equal-height cards | The card's box fills a stretched host on its own |
|
|
1438
|
-
| `!important` on
|
|
1439
|
-
| A wrapper around `ds-table` for sort/range announcements,
|
|
1723
|
+
| `!important` on a `--ds-table-cell-pad` override under `density="compact"` | Compact no longer out-specifies the padding hooks |
|
|
1724
|
+
| A wrapper around `ds-table` for sort/range announcements, a `role="separator"` resize handle, or a header filter the checklist cannot express | All three ship: the live region, the `role="separator"` handle, and `dsHeaderFilter` |
|
|
1725
|
+
| `new Event('input'`, `dispatchEvent`, `querySelector` | Querying the autocomplete's inner `<input>` and dispatching a synthetic `input` event to clear it Replace with: `clear()`. |
|
|
1726
|
+
| `--ds-autocomplete-input-minw` | A --ds-autocomplete-input-minw override, written to hide the empty filter box that sat beside a chosen value in single mode. The input collapses on its own once a value is picked and the panel closes. Replace with: nothing - unless you genuinely want a wider typing area. |
|
|
1727
|
+
| `.trigger`, `:focus-within`, `ds-date-picker` | A :focus-within rule on the date-picker trigger, written because the trigger went dark while its panel was open. The component keeps an "open" class alongside the focus rules now. Replace with: nothing - the component holds the indicator itself. |
|
|
1728
|
+
| A wrapper around the export button catching a rejected `exportFetcher` — a `try {` / `catch` around it | ds-table emits `(exportFailed)` now. Replace with: bind (exportFailed) on ds-table. |
|
|
1729
|
+
| Your own live region around `ds-table` — an `aria-live` or `role="status"` element announcing sort state or row range | The table announces both through its own role="status" region, so keeping yours announces every change twice. Replace with: nothing - retune the wording through sortAnnouncement and rangeAnnouncement. |
|
|
1440
1730
|
|
|
1441
1731
|
**To sweep for the rest:** grep your styles for `::ng-deep`, `!important` and any selector naming a
|
|
1442
1732
|
DS internal class (`.button`, `.trigger`, `.option`, `.modal`). Each hit is either a row above or a
|
|
@@ -2154,6 +2444,15 @@ genuine gap worth reporting.
|
|
|
2154
2444
|
(select, multi-select, autocomplete, date / time / colour picker, popover, tooltip, menu submenus). A
|
|
2155
2445
|
global override always worked and is unaffected.
|
|
2156
2446
|
|
|
2447
|
+
### What you can now DELETE
|
|
2448
|
+
|
|
2449
|
+
None of this is required — skipping it leaves working code that is merely redundant. Each row is a
|
|
2450
|
+
workaround this release made unnecessary. Generated from the release manifest’s `deleteList`.
|
|
2451
|
+
|
|
2452
|
+
| If you have | Delete it, because |
|
|
2453
|
+
| --- | --- |
|
|
2454
|
+
| `ds-table`, `z-index`, `--table-sticky-corner-z`, `sticky` | A consumer z-index on DS table cells, raised to stop the first body row painting over the header when stickyHeader and stickyFirstColumn were both on. The sticky-header rule out-specified --table-sticky-corner-z and both landed on the same z-index; that is fixed in the component. Replace with: nothing - the component orders the layers itself. |
|
|
2455
|
+
|
|
2157
2456
|
## 0.7.1 — 2026-08-04
|
|
2158
2457
|
|
|
2159
2458
|
### Added
|
|
@@ -2427,6 +2726,17 @@ genuine gap worth reporting.
|
|
|
2427
2726
|
animation; the class is dropped, so `styles/overlay-motion` no longer applies to the pane and the modal
|
|
2428
2727
|
plays only its own `--ds-modal-*` entrance.
|
|
2429
2728
|
|
|
2729
|
+
### What you can now DELETE
|
|
2730
|
+
|
|
2731
|
+
None of this is required — skipping it leaves working code that is merely redundant. Each row is a
|
|
2732
|
+
workaround this release made unnecessary. Generated from the release manifest’s `deleteList`.
|
|
2733
|
+
|
|
2734
|
+
| If you have | Delete it, because |
|
|
2735
|
+
| --- | --- |
|
|
2736
|
+
| `[reserveMessage]="false"` | The default is FALSE again, so an opt-out binding only restates it - unless the field sits under a `dsReserveMessages` host or an app config that turns it on, where the binding is still the way back out. mm-broker carried six, three of them dead (2026-08-21). Replace with: nothing - delete the binding where no host reserves. |
|
|
2737
|
+
| `gap: var(--space-1)`, `margin-top: -` | A tighter sub-stack or a negative margin added to swallow the reserved message row is now over-tightening a form that no longer reserves it. Replace with: the normal 16px field stack. |
|
|
2738
|
+
| `ds-pagination`, `ds-field-message`, `display: none` | A rule hiding the empty message row inside the pagination rows-per-page select. The component pins that select to its own compact shape now, so the row is gone at the source. Replace with: nothing - delete the rule. |
|
|
2739
|
+
|
|
2430
2740
|
## 0.7.0 — 2026-07-30
|
|
2431
2741
|
|
|
2432
2742
|
### Changed
|
|
@@ -2786,7 +3096,7 @@ None of this is required — skipping it leaves working code that is merely redu
|
|
|
2786
3096
|
|
|
2787
3097
|
| If you have | Delete it, because |
|
|
2788
3098
|
| --- | --- |
|
|
2789
|
-
| A logo overlaid
|
|
3099
|
+
| A logo overlaid on ds-sidenav’s brand row — `position: absolute` against `ds-sidenav`'s brand row, written when there was no slot for one. | project it into `[brand]` |
|
|
2790
3100
|
| A scrollTop pin or a scroll-lock hack written against the content jolt an opening sheet used to cause in a shell that is a containing block for fixed descendants. | nothing - the entering panel no longer contributes that overflow |
|
|
2791
3101
|
|
|
2792
3102
|
## 0.6.1 — 2026-07-16
|
|
@@ -2809,6 +3119,15 @@ None of this is required — skipping it leaves working code that is merely redu
|
|
|
2809
3119
|
`aria-modal="true"`, telling assistive technology the page behind it was inert. Removed so the
|
|
2810
3120
|
announced ARIA state matches the panel's actual non-blocking behaviour.
|
|
2811
3121
|
|
|
3122
|
+
### What you can now DELETE
|
|
3123
|
+
|
|
3124
|
+
None of this is required — skipping it leaves working code that is merely redundant. Each row is a
|
|
3125
|
+
workaround this release made unnecessary. Generated from the release manifest’s `deleteList`.
|
|
3126
|
+
|
|
3127
|
+
| If you have | Delete it, because |
|
|
3128
|
+
| --- | --- |
|
|
3129
|
+
| `ds-date-picker`, `pointer: coarse`, `ontouchstart`, `matchMedia`, `type="date"` | A branch that swapped ds-date-picker for a native input, or disabled its masked typing, on touch devices. It existed because segment-aware editing was wired to keydown, which soft keyboards do not report faithfully; the mobile path goes through beforeinput now, so the masked field works there. Replace with: nothing - render ds-date-picker on touch as well. |
|
|
3130
|
+
|
|
2812
3131
|
## 0.6.0 — 2026-07-16
|
|
2813
3132
|
|
|
2814
3133
|
### Breaking
|
package/components.md
CHANGED
|
@@ -146,15 +146,19 @@ text rather than a state. Retune app-wide with `DS_CONFIG.field.stateIcons` (per
|
|
|
146
146
|
is not a validated field; where a search needs a label or an error line, use `ds-input`.
|
|
147
147
|
|
|
148
148
|
#### `<ds-button>` — `ButtonComponent`
|
|
149
|
-
Inputs: **two orthogonal axes** — `color: ButtonColor = 'primary'` (`'primary' | 'secondary' | 'tertiary' | 'neutral' | 'error' | 'success' | 'warning'`) and `variant: ButtonVariant = 'solid'` (`'solid' | 'tonal' | 'outline' | 'ghost' | 'text'`). Plus `size: DsSize | null = null` (unset resolves `DS_CONFIG.control.size`, then `md`), `type: 'button' | 'submit' | 'reset' = 'button'`, `disabled`, `loading`, `fullWidth`, `icon: IconName | null`.
|
|
149
|
+
Inputs: **two orthogonal axes** — `color: ButtonColor = 'primary'` (`'primary' | 'secondary' | 'tertiary' | 'neutral' | 'error' | 'success' | 'warning'`) and `variant: ButtonVariant = 'solid'` (`'solid' | 'tonal' | 'outline' | 'ghost' | 'text'`). Plus `size: DsSize | null = null` (unset resolves `DS_CONFIG.control.size`, then `md`), `type: 'button' | 'submit' | 'reset' = 'button'`, `disabled`, `loading`, `fullWidth`, `icon: IconName | null`. Plus the refusal pair below: `disabledReason`, and the field message inputs `hint` / `warning` / `error` / `messageIcon` / `reserveMessage` / `ariaDescribedBy`.
|
|
150
150
|
Axis meaning: **variant is loudness** (solid > tonal > outline/ghost/text), **color is hue** — every pair renders, and the UX-discouraged ones dev-warn (see `DISCOURAGED_COMBOS`). Only solid and tonal paint a fill: outline, ghost and text are TRANSPARENT, so they adopt the surface they sit on. Disabled splits by whether the fill can carry the state: `solid` and `tonal` keep `oklch(from accent 70% 0.035 h)`, while `outline`, `ghost` and `text` — the three with no fill of their own — mix the label toward the surface, `color-mix(in srgb, <label> 40%, var(--surface-default))`, because a fixed lightness cannot serve both themes. (History: the single `variant` axis was split into color × variant in 2026-06; `danger`→`error`, `link`→`text`, the old `ghost`→`outline`.)
|
|
151
151
|
Output: `(pressed): MouseEvent` — only fires when not disabled and not loading
|
|
152
|
-
Content slots: default (label / leading or trailing icon). For icon-only actions use `<ds-icon-button>`.
|
|
153
|
-
|
|
152
|
+
Content slots: default (label / leading or trailing icon), plus `[dsButtonSubtext]` for a projected second line. For icon-only actions use `<ds-icon-button>`.
|
|
153
|
+
**Saying WHY a button is refused, and the two kinds of refusal.** A greyed control that does not say why is a dead end, and until 0.10.4 the only way to explain one was a tooltip — mouse-only. Which input to reach for is decided by whether the user can lift the refusal on this screen:
|
|
154
|
+
- **Standing** (no permission, no integration — nothing here will change it): `disabledReason` beside `disabled`. The reason renders as a second line INSIDE the button, and setting it flips how the button is disabled — `aria-disabled="true"` instead of the native attribute, because a natively disabled button never takes focus and its description would never be announced (measured; Chrome's a11y tree reports name `"Approve invoice"`, description `"Needs the Finance role"`, state disabled). The click is swallowed in the handler instead, so `(pressed)` still never fires. Leave `disabledReason` unset and NOTHING changes: the native attribute stays, and so does every existing layout. Length is deliberately uncapped — the text wraps and the button grows.
|
|
155
|
+
- **Temporary** (the form is not filled in yet): do NOT disable the button at all. Leave it live, judge validity in the submit handler (the house rule for forms), and carry the text UNDER the button with `hint` / `warning` / `error` — the same three inputs the fields take, resolved by the same `resolveFieldMessage`, rendered by the same `ds-field-message`, with the same `messageIcon` and `reserveMessage` knobs and the same `DS_CONFIG.field.*` fallbacks. This is inheritance, not a copy: `hint`/`warning`/`error`/`messageIcon`/`reserveMessage` moved out of `DsFieldBase` into a new `DsMessageBase`, which `DsFieldBase` and `ButtonComponent` both extend — `errors`/`invalid`/`touched` stay on `DsFieldBase`, since a button has no validation state of its own.
|
|
156
|
+
Layout: a message-bearing button becomes a column (host class `with-message`), and because the host shrinks to fit, a message longer than the label widens the pair — button included, exactly as a field's control spans its own message. Without a message the host keeps the `inline-flex` box every existing layout was built against.
|
|
157
|
+
Tokens: `--ds-button-bg-color`, `--ds-button-bg-color-hover`, `--ds-button-bg-color-active`, `--ds-button-bg-color-disabled`, `--ds-button-label-color`, `--ds-button-label-color-disabled`, `--ds-button-border`, `--ds-button-radius`, `--ds-button-focus-shadow`, `--ds-button-pressed-shadow`, `--ds-button-shadow`, `--ds-button-shadow-hover`. The last two are the REST and hover shadow, both `none` by default — before them the only way to give a button a resting shadow was a deep selector into its inner `<button>`. `-shadow-hover` falls back to `-shadow`, so setting the resting one alone keeps the button steady under the pointer; focus and pressed keep their own hooks and still win while those states are on. For `variant="solid"`, `-bg-color-hover` / `-bg-color-active` / `-pressed-shadow` default to a `color-mix()` derivation of the resolved fill (88 % / 76 % + black — the theme's hover/pressed recipe), so overriding the fill alone retints the whole state set; tonal, outline, ghost and text keep explicit ramp defaults, so a full retint there means setting the state tokens too.
|
|
154
158
|
|
|
155
159
|
#### `<ds-icon-button>` — `IconButtonComponent`
|
|
156
160
|
Icon-only action with its own taxonomy, distinct from `ds-button`. `ariaLabel` is required (icon-only must be labelled for a11y).
|
|
157
|
-
Inputs: `icon: required IconName`, `ariaLabel: required string`, `variant: IconButtonVariant = 'standard'` (`'standard' | 'filled' | 'tonal' | 'outlined'`), `size: IconButtonSize = 'md'` (`'sm' | 'md' | 'lg'` = 32/40/48), `type: 'button' | 'submit' | 'reset' = 'button'`, `disabled: boolean = false`, `selected: boolean = false` (toggle — sets `aria-pressed`)
|
|
161
|
+
Inputs: `icon: required IconName`, `ariaLabel: required string`, `ariaDescribedBy: string | null = null` (point at text the page already shows — e.g. why the action is refused; icon-only leaves no room for a second line, which is why there is deliberately no `disabledReason` here), `variant: IconButtonVariant = 'standard'` (`'standard' | 'filled' | 'tonal' | 'outlined'`), `size: IconButtonSize = 'md'` (`'sm' | 'md' | 'lg'` = 32/40/48), `type: 'button' | 'submit' | 'reset' = 'button'`, `disabled: boolean = false`, `selected: boolean = false` (toggle — sets `aria-pressed`)
|
|
158
162
|
Output: `(pressed): MouseEvent` — fires when not disabled
|
|
159
163
|
Variant emphasis: `standard` chromeless (hover-reveal) · `filled` `--primary` · `tonal` `--primary-muted` · `outlined` bordered. `selected` renders the pressed/active fill.
|
|
160
164
|
Tokens: `--ds-icon-button-bg-color`, `--ds-icon-button-icon-color`, `--ds-icon-button-border`, `--ds-icon-button-bg-color-hover`, `--ds-icon-button-bg-color-active`, `--ds-icon-button-icon-color-hover`, `--ds-icon-button-radius`, `--ds-icon-button-focus-shadow`. `filled`/`selected` derive hover/active from the resolved bg, `standard`/`tonal`/`outlined` keep explicit ramp defaults.
|
|
@@ -282,8 +286,9 @@ The companion `<ds-toast-region>` lives inside the `ToastService` (see Services)
|
|
|
282
286
|
### Layout & navigation
|
|
283
287
|
|
|
284
288
|
#### `<ds-sidenav>` — `SidenavComponent`
|
|
285
|
-
Inputs: `collapsed: boolean = false`, `brand: string | null = null` (renders a letter mark + name; omit to project custom content, or set `DS_CONFIG.brand.name`), `logoLetter: string | null = null` (the mark's glyph; derived from `brand` when unset), `rail: boolean = true` (whether an active item draws its edge marker — turn it off here rather than painting `--ds-sidenav-item-rail` transparent)
|
|
289
|
+
Inputs: `collapsed: boolean = false`, `brand: string | null = null` (renders a letter mark + name; omit to project custom content, or set `DS_CONFIG.brand.name`), `logoLetter: string | null = null` (the mark's glyph; derived from `brand` when unset), `rail: boolean = true` (whether an active item draws its edge marker — turn it off here rather than painting `--ds-sidenav-item-rail` transparent), `brandRoute: string | readonly unknown[] | null = null`, `brandLinkLabel: string | null = null`
|
|
286
290
|
Content: default slot for groups/items + custom brand/footer rows
|
|
291
|
+
**The brand row leads home only if you say so.** `brandRoute` turns the mark + wordmark into one link; unset, the row stays a plain block. A logo that goes nowhere should not be a link, and whether a mark is a way home is an app's decision, not the DS's — so this is opt-in, like every other new capability here. The link announces itself as `"<brand>, home"` because a wordmark alone does not say where it goes; `brandLinkLabel` overrides that. Router targets only, and `RouterLink` is instantiated only inside the `@if`, so an app with no router provided still renders the sidenav. A collapse toggle projected into the row stays OUTSIDE the link — one control never nests inside another.
|
|
287
292
|
Tokens: `--ds-sidenav-bg-color`, `--ds-sidenav-border`, `--ds-sidenav-width`, `--ds-sidenav-width-collapsed`, `--ds-sidenav-mark-bg-color`, `--ds-sidenav-mark-label-color`
|
|
288
293
|
|
|
289
294
|
#### `<ds-sidenav-group>` — `SidenavGroupComponent`
|
|
@@ -294,6 +299,7 @@ When `expandable=true` renders header button with toggle + caret; collapses body
|
|
|
294
299
|
#### `<ds-sidenav-item>` — `SidenavItemComponent`
|
|
295
300
|
Inputs: `icon: IconName | null = null` (optional — falls back to `[icon]` slot), `label: required string`, `href: string = ''`, `routerLink: string | readonly unknown[] | null = null`, `active: boolean = false`, `badge: number | null = null`, `hasAlert: boolean = false`, `rail: boolean | null = null` (draws the active item's edge marker; unset follows the parent `ds-sidenav`)
|
|
296
301
|
Content slots: `[icon]` (custom icon when not using a DS IconName), `[trailing]` (right-aligned chrome — badges, indicators, kbd shortcuts)
|
|
302
|
+
**Three elements, decided by destination.** `routerLink` → an `<a [routerLink]>` with `routerLinkActive`; `href` → a plain `<a href>`; **neither → a `<button type="button">`**. Until 0.11.0 the last case fell back to `href="#"`, which navigates: it rewrites the URL and discards the scroll position on every click, which is how a sidenav SPECIMEN in these docs used to move the page under itself. An item that only emits `activate` is a button. Styling is identical across all three — the rules are class-based (`.item`) and the button's UA chrome is reset — so target the class, never the tag.
|
|
297
303
|
Tokens (on `:host`): `--ds-sidenav-item-label-color`, `--ds-sidenav-item-label-color-hover`, `--ds-sidenav-item-bg-color-hover`, `--ds-sidenav-item-bg-color-active` (default: `--accent-subtitle` — a wash, not a solid pill), `--ds-sidenav-item-label-color-active` (default: `--accent-strong`), `--ds-sidenav-item-bg-color-active-hover` (default: `--accent-muted`, deepening toward the accent), `--ds-sidenav-item-rail` (left rail, default: `--accent-strong`), `--ds-sidenav-item-radius`, `--ds-sidenav-alert-color`
|
|
298
304
|
|
|
299
305
|
#### `<ds-topbar>` — `TopBarComponent`
|
|
@@ -351,7 +357,8 @@ Content: label text (when `variant="label"`).
|
|
|
351
357
|
#### `<ds-card>` — `CardComponent`
|
|
352
358
|
Inputs: `elevation: 'flat' | 'raised' | 'hover' | 'interactive' = 'flat'`, `padding: 'none' | 'sm' | 'md' | 'lg' | null = null` (when `null`, no `padding-*` class is applied and the consumer controls padding via own CSS or `--ds-card-pad`)
|
|
353
359
|
Output: `(pressed): MouseEvent` — fires only when `elevation="interactive"`
|
|
354
|
-
Tokens: `--ds-card-bg-color`, `--ds-card-border`, `--ds-card-radius`, `--ds-card-pad`, `--ds-card-shadow`, `--ds-card-shadow-hover`, `--ds-card-focus-shadow`, `--ds-card-hover-lift`
|
|
360
|
+
Tokens: `--ds-card-bg-color`, `--ds-card-border`, `--ds-card-radius`, `--ds-card-pad`, `--ds-card-shadow`, `--ds-card-shadow-hover`, `--ds-card-focus-shadow`, `--ds-card-hover-lift`, `--ds-card-overflow`
|
|
361
|
+
Full-bleed child: a child whose background reaches the card edge paints square corners over the radius, and the host cannot fix it — the rounded box is the card's inner element. Set `--ds-card-overflow: clip` (`clip`, not `hidden`, so the card stays out of the scroll-container business). It is opt-in because a clipped card also cuts the focus ring off a child at its edge; where the clipped card holds focusable content, pair it with `data-focus="inset"`.
|
|
355
362
|
Convention tokens (consumer-side `.title` projected into the card slot — declared at `:root`, not on the host): `--card-title-fs` (default `var(--font-size-h4)` = 22px; MM brand steps down to `var(--font-size-h5)` = 18px). Consumer markup: `<h3 class="title">…</h3>`; local `.title` class reads the token via `font:` shorthand together with `--font-weight-bold` / `--line-height-snug` / `--font-heading`.
|
|
356
363
|
|
|
357
364
|
#### `<ds-accordion>` + `<ds-accordion-item>` — `AccordionComponent`, `AccordionItemComponent`
|
|
@@ -405,6 +412,7 @@ Selection is communicated via the `value` model. Keyboard: ArrowUp/Down, Enter/S
|
|
|
405
412
|
Inputs: `data: required readonly T[]`, `columns: required readonly TableColumn<T>[]`, `selectable: boolean = false`, `bordered: boolean = false` (opt-in outer border + radius; off by default so tables flush inside `<ds-card padding="none">` don't double-border), `loading: false | 'skeleton' | 'overlay' = false`, `stickyHeader: boolean = true`, `selectedIds: model<Set<string>>`, `sortKey: model<string | null>`, `sortDir: model<SortDir>` (`'asc' | 'desc' | null`), `skeletonRows: number = 5`
|
|
406
413
|
Outputs: `(rowClick): T`, `(sortChange): SortChangeEvent` (`{ key, dir }`)
|
|
407
414
|
Column shape: `{ key: string, label: string, sortable?: boolean, align?: 'left' | 'right' | 'center', cell?: (row: T) => string }`
|
|
415
|
+
Opening a row: give one column `link: (row) => <route target> | null` and its value renders as a real `<a>` — visible without hovering, in the tab order as a link, and Ctrl/Cmd-clickable, none of which a clickable `<tr>` can do. `null` for a row leaves that cell as plain text, so a partly-reachable list stays one column; external URLs go through a `[dsCellTemplate]` instead, since `link` takes Angular route targets only. It composes with `rowInteractive` (the link stops its click from reaching the row), but the two together cost **two tab stops per row** — on a long list prefer the link alone. `interactive: true` only tints a cell on row hover, which a keyboard or touch user never sees; prefer `link` wherever the row actually leads somewhere.
|
|
408
416
|
Cell templates: `<ng-template dsCellTemplate="<colKey>" let-row>…</ng-template>` — `row` is typed `unknown`, narrow via a helper method on the host.
|
|
409
417
|
Content slots: `[empty]` (rendered when `data.length === 0`), `[bulk-actions]` (rendered in the bulk action bar when `selectable && some selected`)
|
|
410
418
|
Loading modes: `'skeleton'` replaces rows with shimmer placeholders driven by the global `--skeleton-shimmer-x` keyframe; `'overlay'` keeps existing rows visible behind a translucent layer with a centred spinner.
|