@ids-group-ltd/ids-design-system 0.10.1 → 0.10.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 +433 -14
- package/components.md +73 -13
- package/fesm2022/ids-group-ltd-ids-design-system.mjs +348 -143
- package/fesm2022/ids-group-ltd-ids-design-system.mjs.map +1 -1
- package/migrations/0.10.0.json +420 -44
- package/migrations/0.10.1.json +80 -16
- package/migrations/0.10.2.json +482 -0
- package/migrations/0.10.3.json +73 -0
- package/migrations/0.2.0.json +32 -8
- package/migrations/0.3.0.json +19 -3
- package/migrations/0.4.0.json +50 -11
- package/migrations/0.5.0.json +93 -24
- package/migrations/0.5.1.json +106 -29
- package/migrations/0.6.0.json +2 -1
- package/migrations/0.6.2.json +33 -3
- package/migrations/0.6.3.json +19 -3
- package/migrations/0.7.0.json +77 -25
- package/migrations/0.7.1.json +84 -8
- package/migrations/0.8.0.json +46 -10
- package/migrations/0.9.0.json +284 -35
- package/migrations/AUTHORING.md +125 -12
- package/migrations/README.md +62 -5
- package/package.json +1 -1
- package/styles/_dropdown-overlay.scss +4 -3
- package/styles/_field-group-segment.scss +4 -0
- package/styles/_focus.scss +36 -22
- package/styles/_text-clip.scss +12 -0
- package/themes/_semantic.scss +20 -3
- package/types/ids-group-ltd-ids-design-system.d.ts +187 -68
package/CHANGELOG.md
CHANGED
|
@@ -8,6 +8,379 @@ While the package is on `0.x`, minor releases may contain breaking changes.
|
|
|
8
8
|
|
|
9
9
|
## Unreleased
|
|
10
10
|
|
|
11
|
+
## 0.10.3 — 2026-08-24
|
|
12
|
+
|
|
13
|
+
### Added
|
|
14
|
+
|
|
15
|
+
- **Two SCSS mixins for building your own composite controls** (`components.md` § Global helper
|
|
16
|
+
classes). `focus.owns-the-focus-ring($control)` — include it in a shell that paints its own ring
|
|
17
|
+
on `:focus-within`, naming the ONE control inside that must not paint the base indicator too.
|
|
18
|
+
`outline: 0` cannot do that, because the base indicator is a box-shadow, and a box-wide reset
|
|
19
|
+
instead silences the tab stops living in the box — a clear button, a stepper arrow. It is the
|
|
20
|
+
mixin `tools/check-focus-rings.mjs` checks for. `text-clip.single-line-ellipsis` — a one-line
|
|
21
|
+
label that truncates with an ellipsis, via `overflow: clip` plus `overflow-clip-margin`, because
|
|
22
|
+
`hidden` under a line-height tighter than the font glyph box shaves the top and bottom off every
|
|
23
|
+
glyph. `@use 'styles/focus'` / `@use 'styles/text-clip'` to reach them; a mixin emits nothing until
|
|
24
|
+
it is included.
|
|
25
|
+
|
|
26
|
+
### Fixed
|
|
27
|
+
|
|
28
|
+
- **`ds-input` and `ds-textarea` were the two shells 0.10.2's ring fix missed.** Same defect and same
|
|
29
|
+
cause as "One focus ring per field, not two" below: the universal `:where(:focus-visible)` shadow
|
|
30
|
+
lands on the inner element, the box paints its own halo on `:focus-within`, and the `outline: 0`
|
|
31
|
+
both already had cannot cancel a shadow. So the two plainest fields in the library went on drawing
|
|
32
|
+
a 4px control ring around the `<input>`/`<textarea>` **and** a 3px field halo around the box.
|
|
33
|
+
**They were missed because that pass trusted the shell list written in `styles/_focus.scss` rather
|
|
34
|
+
than measuring.** A browser sweep — 9,968 focusable elements over 64 pages, transitions disabled so
|
|
35
|
+
every computed shadow is final — found exactly these two and nothing else in the library. The reset
|
|
36
|
+
stays scoped to the field element, so `clear-btn` and `password-toggle` inside the same box keep
|
|
37
|
+
their own rings; they are real tab stops.
|
|
38
|
+
- **The token reference was missing 11 public tokens that were always overridable.**
|
|
39
|
+
`tools/extract-tokens.mjs` searched for the literal `var(--ds-`, so any resolver whose declaration
|
|
40
|
+
wrapped across lines put a newline between `var(` and the name and the token silently never reached
|
|
41
|
+
the reference. Newly listed and described: `--ds-container-pad-x`, `--ds-multi-select-border-color`
|
|
42
|
+
(+`-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`, and
|
|
44
|
+
`--ds-time-picker-trigger-bg-color` / `-border` / `-color`. Nothing changed in the components —
|
|
45
|
+
these overrides already worked; only the documentation was blind to them.
|
|
46
|
+
- **Two buttons inside portaled panels had no focus indicator, and one panel had square corners — a
|
|
47
|
+
private token read from outside the host that declares it.** `ds-date-picker`'s `.period-trigger`
|
|
48
|
+
(the month/year header, `tabindex="0"`) and `ds-time-picker`'s `.time-action` both did
|
|
49
|
+
`box-shadow: var(--_…-focus-shadow)` beside `outline: none`. Those private tokens are declared on
|
|
50
|
+
`:host`, the panels are portaled out of it by the CDK, so the `var()` resolved to nothing — and an
|
|
51
|
+
unresolvable `var()` makes `box-shadow` its initial value, `none`. Measured: resting and focused
|
|
52
|
+
paint were byte-identical on both, so a keyboard user landing there saw nothing. Another WCAG 2.4.7
|
|
53
|
+
failure, and older than the 0.10.x focus work. `ds-time-picker`'s panel `border-radius` read the
|
|
54
|
+
same way and fell back to `0`, so the panel rendered square instead of `--ds-radius-panel`.
|
|
55
|
+
**Found by opening each overlay and probing inside it** — the earlier sweeps only ever saw
|
|
56
|
+
focusables that exist while the overlay is closed. `ds-select`, `ds-multi-select` and
|
|
57
|
+
`ds-autocomplete` panels were checked the same way and are clean.
|
|
58
|
+
- **`ds-search`'s clear button had no focus indicator at all — introduced by 0.10.2's own ring fix.**
|
|
59
|
+
That fix silenced the base indicator with a shell-wide reset, which also hit `.search-clear`, a
|
|
60
|
+
`tabindex="0"` tab stop. Measured: with the field's halo already lit, tabbing from the input to the
|
|
61
|
+
× changed **no** paint property anywhere on screen — box-shadow, outline, border, background and
|
|
62
|
+
colour were byte-identical in both states, so a keyboard user could not tell the × had focus. A
|
|
63
|
+
WCAG 2.4.7 failure, and the same defect as the double ring seen from the other side. Every shell now
|
|
64
|
+
names the one control it speaks for through the new `focus.owns-the-focus-ring($control)` mixin
|
|
65
|
+
instead of blanketing its box, and `ds-field-group` drops its blanket entirely — each segment
|
|
66
|
+
already silences its own. `tools/check-focus-rings.mjs` fails the build when a component paints a
|
|
67
|
+
ring on `:focus-within` without silencing the base rule; it replaces the hand-kept shell list in
|
|
68
|
+
`styles/_focus.scss` that had been wrong for two releases.
|
|
69
|
+
|
|
70
|
+
## 0.10.2 — 2026-08-24
|
|
71
|
+
|
|
72
|
+
### Added
|
|
73
|
+
|
|
74
|
+
- **`TableColumn.interactive` — the cell that says WHICH text opens the record.** On a
|
|
75
|
+
`[rowInteractive]` table the whole row is the control, so the hover tint says "clickable" and
|
|
76
|
+
nothing says what the click leads to; a `cursor: pointer` does not name a target. Mark the column
|
|
77
|
+
`interactive: true` and its cell takes a link colour plus an underline while the row is hovered —
|
|
78
|
+
**both, never hue alone** — through `--ds-table-cell-link-color` (default `--accent`) and
|
|
79
|
+
`--ds-table-cell-link-decoration` (default `underline`). Off unless a column asks for it, and inert
|
|
80
|
+
on a passive table for the same reason the row tint is: nothing should promise a click that does not
|
|
81
|
+
happen. Four list screens in one consumer had written this as
|
|
82
|
+
`:host ::ng-deep ds-table tr:hover .cell-name { color: var(--accent); text-decoration: underline }`,
|
|
83
|
+
which was their last table reach that no token could replace.
|
|
84
|
+
|
|
85
|
+
- **`TableRowAction` can vary its items per row: `hidden` and `disabledReason`.** The contract could
|
|
86
|
+
only GREY an item that was always there, so a menu whose items swap by status — a draft offering Edit
|
|
87
|
+
+ Launch where a live record offers Revert + Delete — grew a permanently dead half on every row. That
|
|
88
|
+
is why the row-action column shipped in 0.6.3 and one consumer adopted it in **zero** of eleven row
|
|
89
|
+
menus. `hidden?: (row) => boolean` leaves the item out instead, and **a row with every item hidden
|
|
90
|
+
renders no kebab at all** rather than opening an empty menu. `disabledReason?: string | ((row) =>
|
|
91
|
+
string)` puts the why on the item's second line, read only when `disabled` returns true for that row —
|
|
92
|
+
a reason on a live item would read as a caveat on something that works.
|
|
93
|
+
|
|
94
|
+
- **`ds-menu-item` takes a `description` — a standing second line under the label.** For a limitation
|
|
95
|
+
the action carries ("only the first 1,000 rows", "read-only in this workspace"), visible without hover
|
|
96
|
+
or focus, which is what separates it from a `[dsTooltip]`. **It reaches assistive tech as
|
|
97
|
+
`aria-describedby`, not as part of the item's name:** the line is `aria-hidden` and referenced by id,
|
|
98
|
+
so the projected label alone names the action. Seven items across four files in one consumer
|
|
99
|
+
hand-rolled this with the same five-line rule; the width cap is now
|
|
100
|
+
`--ds-menu-item-description-max-width` instead of each app's own `14rem`.
|
|
101
|
+
|
|
102
|
+
- **`data-focus="inset"` — a focus style that survives a clipping ancestor.** The ring is a box-shadow
|
|
103
|
+
outside the border box, so any `overflow: hidden` ancestor ate it and left the element focusable with
|
|
104
|
+
**no indicator at all** — measured in four places in one app, one of them a `ds-button` inside a
|
|
105
|
+
wrapper that clips for its own animation. Clipping a card to hold a full-bleed child inside a rounded
|
|
106
|
+
corner is normal, and `ds-card` + `padding: none` invites exactly that. **Unlike the other four focus
|
|
107
|
+
styles this one is NOT pinned to `:root`:** a clip is a local problem, so the attribute works wherever
|
|
108
|
+
you set it and the declarations inherit into the subtree. Put it on the clipping element.
|
|
109
|
+
|
|
110
|
+
- **`ds-search.clear()` is public.** It empties the field, DROPS an armed keystroke and publishes `''`
|
|
111
|
+
at once — which writing `''` into `value` does not do: the effect watching `value` cancels the timer
|
|
112
|
+
only when the incoming text DIFFERS from what the control last pushed, so a host-owned Clear button
|
|
113
|
+
could not always drop the debounce it was clearing. Public for the same reason `focus()` is, and the
|
|
114
|
+
same button needs both.
|
|
115
|
+
|
|
116
|
+
- **`ds-search` binds to a form — both systems — and a disabled search now looks disabled.** It held a
|
|
117
|
+
value that nothing could bind: no `NG_VALUE_ACCESSOR`, so `[(ngModel)]`, a `formControlName` and a
|
|
118
|
+
signal form all slid off it while its own `[(value)]` kept working. It extends
|
|
119
|
+
`DsControlValueAccessor` now, like every other control that carries a value, and a new `disabled`
|
|
120
|
+
input folds together with the form's own disabled state. The shell paints the disabled surface from
|
|
121
|
+
the inner input's state, which it never did — a disabled search looked live and still took a click.
|
|
122
|
+
**Deliberately no label and no message row.** A toolbar filter is not a validated field, and giving
|
|
123
|
+
it the field chrome would restyle every toolbar it sits in; reach for `ds-input` where a search
|
|
124
|
+
needs a label.
|
|
125
|
+
|
|
126
|
+
- **`--ds-menu-radius` — the bare `ds-menu` corner, which two token descriptions already promised.**
|
|
127
|
+
The component hardcoded `var(--radius-md)` while `token-descriptions.json` referred to
|
|
128
|
+
`--ds-menu-radius` as though it were public; the dead-token audit caught it. Same default, so
|
|
129
|
+
nothing moves — this only makes the documented hook real. The panelled case stays separate: inside a
|
|
130
|
+
`ds-popover` the menu clips to `--ds-menu-clip-radius`, which the popover publishes.
|
|
131
|
+
|
|
132
|
+
### Changed
|
|
133
|
+
|
|
134
|
+
- **`ds-search` no longer takes the field message inputs, because it never rendered them.**
|
|
135
|
+
Since it gained form binding it extended `DsControlValueAccessor`, which sits on `DsFieldBase` — so
|
|
136
|
+
the API reference advertised `hint`, `error`, `warning`, `errors`, `invalid`, `touched`,
|
|
137
|
+
`reserveMessage` and `messageIcon` on a component whose template has no `ds-field-message` and whose
|
|
138
|
+
class reads none of them. **A consumer binding `error="Too short"` on a `ds-search` got silence, and
|
|
139
|
+
the reference had told them it would work.** Those eight inputs are gone from it now; the reference
|
|
140
|
+
lists the ten it actually implements.
|
|
141
|
+
**BREAKING only if you bound one:** it used to compile and do nothing, and now it is a template type
|
|
142
|
+
error, which is the point. Where a search needs a label or an error line, that is `ds-input` — a
|
|
143
|
+
toolbar filter is not a validated field, which is the same reasoning that kept the message row off it
|
|
144
|
+
in the first place.
|
|
145
|
+
**How the split works, since it is a shape other controls may want:** the `ControlValueAccessor`
|
|
146
|
+
plumbing is now `valueControlBridge()`, a function rather than a base class, so a control can bind to
|
|
147
|
+
a form without inheriting the message API. `DsControlValueAccessor` is that function plus
|
|
148
|
+
`DsFieldBase` and delegates to it, so the logic exists once rather than twice. `hidden` stayed on
|
|
149
|
+
`ds-search`: it belongs to the forms contract — signal forms reaches every control through it — not to
|
|
150
|
+
the message API.
|
|
151
|
+
- **A field's message line now carries a glyph for `error`, `warning` and `success` — and not for
|
|
152
|
+
`hint`.** Colour was the whole signal before, and in the light theme warning (#8A7400) against success
|
|
153
|
+
(#156822) is a hue apart and nothing else: WCAG 1.4.1 is about exactly that, and four of the six
|
|
154
|
+
systems audited for the fill question carry a per-state icon in the field. **`hint` deliberately stays
|
|
155
|
+
bare** — it is the resting text rather than a state, and it is the majority of rows on any real form
|
|
156
|
+
(25 of 43 on our own input page), so a glyph there is noise rather than signal.
|
|
157
|
+
**Per state, independently, app-wide:**
|
|
158
|
+
`provideDsConfig({ field: { stateIcons: { warning: false, hint: 'info' } } })` — a name replaces the
|
|
159
|
+
glyph, `false` removes it, each key is independent of the others, and **`stateIcons: false` is the one
|
|
160
|
+
line back to how fields looked before**. **Per field:** `messageIcon` wins over both —
|
|
161
|
+
`[messageIcon]="false"` drops the glyph on that field alone. It is declared once on the shared
|
|
162
|
+
field base, so it reaches all fifteen fields that render a message row.
|
|
163
|
+
**Two new hooks:** `--ds-field-message-icon-gap`, and `--ds-field-message-icon-offset`, which centres
|
|
164
|
+
the glyph on the FIRST line rather than the block — the row is `align-items: flex-start` now, so a
|
|
165
|
+
message that wraps keeps its glyph beside the first line instead of floating in the middle. The offset
|
|
166
|
+
defaults to a calc over the two tokens that set that line, so it survives a retuned message type.
|
|
167
|
+
**The size is not a token, on purpose:** `ds-icon` takes a number and writes `width`/`height`
|
|
168
|
+
attributes, so a CSS hook would mean reaching into another component's template. The glyph is 14px
|
|
169
|
+
(`--icon-sm`, under the 12px message text); making icon size CSS-driven is a separate change to
|
|
170
|
+
`ds-icon`.
|
|
171
|
+
- **`ds-stat`'s `value` takes `string | number | null`, so Angular's own pipes bind to it.**
|
|
172
|
+
`number`, `currency`, `percent` and `date` are all typed `string | null`, so
|
|
173
|
+
`[value]="count | number"` failed `strictTemplates` with TS2322 and consumers wrote
|
|
174
|
+
`count.toLocaleString('en-US')` in the template instead — which pins a locale rather than reading
|
|
175
|
+
`LOCALE_ID`, and re-runs on every change-detection pass where a pure pipe is cached. One consumer's
|
|
176
|
+
KPI row carries both idioms side by side for exactly this reason. `null` renders as nothing, like the
|
|
177
|
+
empty default, and the four pipes now have a demo on the docs page — which is also the test, since
|
|
178
|
+
that section compiles under `strictTemplates`.
|
|
179
|
+
|
|
180
|
+
- **If you EXTEND a DS component, eleven classes grew and six members changed type.** `npm run
|
|
181
|
+
class-surface` against 0.10.1: `DsFieldBase` (`messageIcon` — the state glyph, declared once for
|
|
182
|
+
every field rather than per component), `DsControlValueAccessor` (`bridge`),
|
|
183
|
+
`FieldMessageComponent` (`config`, `iconResolved`), `AutocompleteComponent` and
|
|
184
|
+
`MultiSelectComponent` (`chipsMode`, `showsEveryChip`), `MenuItemComponent` (`description`,
|
|
185
|
+
`descriptionId`), `SearchComponent` (the CVA surface it now declares itself: `bridge`,
|
|
186
|
+
`disabled`, `formDisabled`, `hidden`, `isDisabled`, `markTouched`, `registerOnChange`,
|
|
187
|
+
`registerOnTouched`, `setDisabledState`, `writeValue`), `SidenavItemComponent` (`rail`,
|
|
188
|
+
`railResolved`), `SidenavComponent` (`rail`), `TableComponent` (`actionReason`, `actionsFor`,
|
|
189
|
+
`hasActionsFor`, `visibleRowActions`) and `TimePickerComponent` (`insideATrigger`). A subclass
|
|
190
|
+
declaring any of those names now fails with TS4114 — or TS2415, since a redeclared private
|
|
191
|
+
collides just as a public one does, and a name on `DsFieldBase` reaches every field through it.
|
|
192
|
+
**Six members kept their name and changed type**, which is the case that compiles for a caller
|
|
193
|
+
and breaks an overrider: `maxVisibleChips` on both pickers (widened to
|
|
194
|
+
`number | 'fit' | 'all' | null`, default now `null`), `FieldMessageComponent.icon` (widened to
|
|
195
|
+
`IconName | false | null`, so `false` can mean "no glyph" against a state that supplies one),
|
|
196
|
+
`DsConfig.field` (its shape grew the glyph defaults), `SearchComponent.clear` (`protected` →
|
|
197
|
+
public), `StatComponent.value` (widened to `string | number | null`) and
|
|
198
|
+
`TimeColumnsComponent.onKey` (its parameter list changed). **What the report does NOT show:**
|
|
199
|
+
`ds-search` no longer extends the field base, so it loses eight inherited inputs — the tool
|
|
200
|
+
compares declarations per file and a dropped `extends` moves nothing, so that break is documented
|
|
201
|
+
in its own entry above and not here.
|
|
202
|
+
|
|
203
|
+
- **Every readback that resolves through `DS_CONFIG` is now public.** `sizeResolved` on fourteen
|
|
204
|
+
controls, plus `elevationResolved` / `paddingResolved` (card), `withDotResolved` (badge),
|
|
205
|
+
`borderedResolved` / `stickyScrollbarResolved` (table), `dividersResolved` (both modals),
|
|
206
|
+
`reserveMessageResolved` (every field), the picker locale/format resolvers, and
|
|
207
|
+
`brandName` / `letterGlyph` / `taglineText` (sidenav, auth-layout). They were `protected`, so the
|
|
208
|
+
migration path 0.10.0 published — "read `sizeResolved()` now that `size()` returns null when unbound"
|
|
209
|
+
— did not compile: reading one from a host, a test or a `viewChild` was TS2445.
|
|
210
|
+
**The line is `DS_CONFIG`, and it is deliberate.** A host cannot recompute an app-level default, so
|
|
211
|
+
that readback has to be public. Members a host CAN derive from its own bindings stay closed:
|
|
212
|
+
`invalidResolved`, `railResolved`, `sortModeResolved`, `filterModeResolved`.
|
|
213
|
+
**Subclassers:** these are new public names on the classes, so a subclass that happens to use one now
|
|
214
|
+
needs `override`. Composition remains the supported route.
|
|
215
|
+
|
|
216
|
+
- **The focus ring's inner gap is `transparent`, not `--surface-canvas`.** The 2px band exists to
|
|
217
|
+
separate the ring from the element, so it has to match what is actually BEHIND — and a named surface
|
|
218
|
+
only is that when nothing intervenes. In a dark app with white cards it painted the dark canvas as a
|
|
219
|
+
rim around a white card, reading as a rendering artifact rather than a focus state. Transparent costs
|
|
220
|
+
nothing on a canvas-coloured ground (the same pixels show through) and is right on every other.
|
|
221
|
+
|
|
222
|
+
- **`maxVisibleChips`: `null` means "unset" now, and `'all'` is the mode that shows every chip.**
|
|
223
|
+
`ds-autocomplete` and `ds-multi-select` took `number | 'fit' | null`, in which `null` was the
|
|
224
|
+
LOUDEST setting — render every chip and let the trigger wrap — while 0.10.0 gave `null` a service
|
|
225
|
+
meaning on twenty-two other inputs: not deciding, fall through to the default. The three modes are
|
|
226
|
+
named now: `'fit'` measures the trigger and shows what fits, a number is a ceiling that is still
|
|
227
|
+
measured ("at most N"), `'all'` renders the lot. **BREAKING: `[maxVisibleChips]="null"` used to show
|
|
228
|
+
every chip and now resolves to `'fit'`** — bind `maxVisibleChips="all"` for the old behaviour. Leaving
|
|
229
|
+
it unbound behaves exactly as before, since `'fit'` was already the default, and `null` now leaves
|
|
230
|
+
room for a `DS_CONFIG` slot to answer it app-wide.
|
|
231
|
+
|
|
232
|
+
- **The active `ds-sidenav-item` is a tinted wash with a coloured label, not a solid brand pill** — and
|
|
233
|
+
the edge rail is an input rather than a token you blank out. The item filled with `--accent` and put
|
|
234
|
+
`--text-on-primary` on its label, making the loudest element on the screen out of a state that only
|
|
235
|
+
says "you are here"; two apps independently replaced it, which is the signal that decided this.
|
|
236
|
+
Material fills its navigation drawer's active item with `secondary-container` and labels it
|
|
237
|
+
`on-secondary-container`; Carbon uses `$background-selected` with a border and a weight bump.
|
|
238
|
+
Neither fills with the brand accent. Ours is `--accent-subtitle` behind an `--accent-strong` label,
|
|
239
|
+
and hover deepens toward the accent (`--accent-muted`) instead of lightening toward white — the old
|
|
240
|
+
88%-toward-white mix was invisible on a wash. **The state still does not rest on colour alone:** the
|
|
241
|
+
edge rail and the weight bump both stay — and **the rail is now `--accent-strong`, the active label's
|
|
242
|
+
own colour, instead of `--secondary`.** An orange bar across a monochrome-blue row measured **2.33:1**
|
|
243
|
+
on the light wash, under the 3:1 floor a non-text indicator needs; the accent measures 6.16:1 light and
|
|
244
|
+
5.28:1 dark. Carbon's indicator is the interactive colour and Material's IS the wash — neither
|
|
245
|
+
introduces a second hue. Restore the old bar with `--ds-sidenav-item-rail: var(--secondary)`.
|
|
246
|
+
Every `--ds-sidenav-item-*-active` token keeps its name, so
|
|
247
|
+
an app that already retuned them keeps its own look and needs no edit.
|
|
248
|
+
**`[rail]="false"` on `ds-sidenav`** drops the edge marker for every item, and an item can override
|
|
249
|
+
it for itself (`[rail]` on `ds-sidenav-item`, unset = follow the parent). The old route was
|
|
250
|
+
`--ds-sidenav-item-rail: transparent` or a `::ng-deep` box-shadow reset — both still work, but the
|
|
251
|
+
input says what it means. `SidenavContract` gained a `rail: () => boolean` member; nothing outside
|
|
252
|
+
the library is expected to implement it.
|
|
253
|
+
|
|
254
|
+
- **The shipped migration manifests say WHERE to look, not only what changed — and a lint now holds
|
|
255
|
+
them to it.** `migrations/<version>.json` (the files `dist/ds/migrations/` carries into your
|
|
256
|
+
`node_modules`, which the auto-update plugin runs) gained `surface`, `detect`, `verify`, `restore`,
|
|
257
|
+
`supersedes` / `supersededBy`, and a structured `deleteList`. The reason is a consumer upgrade that
|
|
258
|
+
went 0.6.0 → 0.10.1 and passed over two entries in silence: `0.7.1`'s
|
|
259
|
+
`table-sortkey-non-null-when-unsorted` pointed at `ds-table[sortKey]`, which appears in nobody's
|
|
260
|
+
template, while the code that breaks was their own store —
|
|
261
|
+
`sorting: store.sortKey() ? { path: store.sortKey()!, … } : undefined` — so the search found
|
|
262
|
+
nothing, the item was recorded not-applicable, and the re-check's clean grep agreed. Three
|
|
263
|
+
server-paged screens kept sorting by a column whose header showed no sort. `surface` and `detect`
|
|
264
|
+
make that item searchable in the artifact that actually changes; `verify` gives a behavioural entry
|
|
265
|
+
the positive assertion a re-check can test, since there is no removed symbol whose absence proves
|
|
266
|
+
anything. **Every published manifest was back-filled the same day:** 167 items across 19 releases
|
|
267
|
+
got a `surface`, every behavioural one a `verify`, every changed default a `restore`, and the 32
|
|
268
|
+
prose `DELETE-LIST:` lines became `deleteList` arrays with a greppable `find` each — four of those
|
|
269
|
+
"lines" turned out to be the words "the DELETE-LIST" inside ordinary prose. Two default flips that
|
|
270
|
+
reverse each other now link both ways: `0.7.0` / `0.7.1` on `reserveMessage`, and `0.8.0` / `0.9.0`
|
|
271
|
+
on the table's sort mode. `npm run migration-lint` enforces the contract with no warning level, and
|
|
272
|
+
both the release preflight and the PR gate run it, so a manifest nobody can act on stops the
|
|
273
|
+
pipeline instead of reaching a consumer. Three CHANGELOG blocks also gained the "What you can now
|
|
274
|
+
DELETE" table their manifests had been carrying alone — 0.10.0's nineteen rows, 0.10.1's and
|
|
275
|
+
0.6.2's.
|
|
276
|
+
|
|
277
|
+
### Fixed
|
|
278
|
+
|
|
279
|
+
- **One focus ring per field, not two.** Since 0.10.0 the universal `:where(:focus-visible)` rule has
|
|
280
|
+
given every focusable element a `box-shadow`, and these shells paint their own on `:focus-within` —
|
|
281
|
+
`outline: 0`, which each inner control already had, cannot cancel a shadow. So a focused field drew a
|
|
282
|
+
tight ring around its inner control AND a halo around the box. Measured on five shapes: `ds-search`,
|
|
283
|
+
`ds-autocomplete`, `ds-date-picker`, `ds-number-stepper`, and any field inside a `ds-field-group`
|
|
284
|
+
(fixed once in the shared segment mixin). It is the same trap 0.10.0 warned consumers about — an app
|
|
285
|
+
rule that styles focus with an `outline` only — landing in our own components.
|
|
286
|
+
**The reset is scoped to the control the shell speaks for, deliberately.** A `ds-number-stepper` step
|
|
287
|
+
button keeps its own ring, and so does a chip's close button: those are `tabindex="0"` tab stops, and
|
|
288
|
+
the halo is already on, so it cannot say which of them focus moved to. The date picker's calendar
|
|
289
|
+
toggle is `tabindex="-1"` and correctly loses its ring.
|
|
290
|
+
|
|
291
|
+
- **A flat line box stopped shaving descenders off clipped labels** (mm-broker MBP-245). `.option` sets
|
|
292
|
+
`line-height: 1` while `.option-label` adds the `overflow: hidden` its ellipsis needs and no padding,
|
|
293
|
+
so the label box was exactly the font size tall and the glyph box was taller: measured **2.13px above
|
|
294
|
+
the cap line and 1.47px below the baseline** clipped, on every option rather than only the ones with a
|
|
295
|
+
descender. Fixed with `overflow: clip` plus a `var(--space-1)` clip margin, which **moves no geometry**
|
|
296
|
+
— the option row stays 30px, the multi-select row 36px, the table row 38px.
|
|
297
|
+
**Six sites:** the shared dropdown overlay (`ds-select`, `ds-autocomplete`), `ds-multi-select`'s own
|
|
298
|
+
copy, `.cell-clip` in `ds-table` and `.label` in `ds-breadcrumbs` (both measured), and the `.crumb`
|
|
299
|
+
rules in `ds-topbar` / `ds-page-header`, which share the shape and are unreachable in our own docs.
|
|
300
|
+
**Two behaviours checked rather than assumed:** the ellipsis still applies (`text-overflow` reads any
|
|
301
|
+
non-`visible` overflow), and `ds-table`'s clipped-cell popover still fires, since `scrollWidth >
|
|
302
|
+
clientWidth` still reports true under `clip`.
|
|
303
|
+
- **A field bound with signal forms threw once per field, and then showed an error it had already
|
|
304
|
+
cleared.** `resolveFieldMessage` subscribes to `NgControl`'s `events` stream to follow reactive and
|
|
305
|
+
template-driven forms. The `NgControl` that signal forms bridges carries no such stream, so the
|
|
306
|
+
subscription threw `TypeError: Cannot read properties of undefined (reading 'pipe')` — four times on
|
|
307
|
+
our own Practice → Signal Forms page, swallowed into the console. **The second half is what a user
|
|
308
|
+
saw:** the throw left that snapshot frozen at first render, and the message resolver falls back to it
|
|
309
|
+
whenever the live errors go empty — so a field that had just become VALID went on showing its FIRST
|
|
310
|
+
failure, with `aria-invalid="true"`. Measured through CDP with real input: empty → "We need an email",
|
|
311
|
+
`nope` → "That does not look like an email address", a valid address → **the required message again**.
|
|
312
|
+
Now the `NgControl` path bows out entirely when it has no live stream, leaving the component's own
|
|
313
|
+
inputs — which is where a signal-forms field's errors and touched arrive — as the single source. The
|
|
314
|
+
same sequence now clears the message and drops `aria-invalid`. **Reactive and template-driven forms are
|
|
315
|
+
untouched** and were re-checked on `/components/input`: too short, empty and valid each render
|
|
316
|
+
correctly, as before.
|
|
317
|
+
|
|
318
|
+
- **`components.md` was missing two layouts and naming three sidenav defaults that are not the
|
|
319
|
+
defaults.** The digest `tools/build-schematics.mjs` copies into `dist/ds/` is what a consumer's own
|
|
320
|
+
agent reads to answer "what does this library have", and `ds-app-layout` and `ds-auth-layout` were
|
|
321
|
+
absent from it entirely — an agent asked to build a shell or a sign-in screen could not find either
|
|
322
|
+
and had no way to know they existed. It also named `--primary`, `--text-on-primary` and
|
|
323
|
+
`--secondary` as the active sidenav item's defaults, which the wash rework in this same release
|
|
324
|
+
replaced. Both are corrected. Three smaller claims went with them: the search page said two things
|
|
325
|
+
skip the debounce where the code and this changelog both say three, the `--ds-stat-value-white-space`
|
|
326
|
+
description said an unwrapped phrase is clipped when it escapes the tile instead, and `ds-badge`
|
|
327
|
+
carried a superseded docblock. **No API changed** — only what the shipped documentation says about it.
|
|
328
|
+
|
|
329
|
+
- **Five more overlays dismiss on a click in the host's own empty width.** `ds-select`,
|
|
330
|
+
`ds-multi-select`, `ds-autocomplete`, `ds-time-picker` and `ds-color-picker` all tested the whole
|
|
331
|
+
HOST in their outside-pointer guard, which is the defect `ds-date-picker` was fixed for in 0.10.1
|
|
332
|
+
(MBP-225): the trigger box hugs its own content while the host takes whatever width a consumer's
|
|
333
|
+
layout gives it, so the label, the message row and any bare strip beside the trigger swallowed the
|
|
334
|
+
dismiss instead of performing it. Each guard now tests its TRIGGER, as `ds-popover` always did;
|
|
335
|
+
`ds-time-picker` tests whichever of its three triggers are present, since a range renders two.
|
|
336
|
+
**Behaviour change if you relied on it:** a press on the label of an open picker now closes the
|
|
337
|
+
panel. A press on the trigger still keeps it open, which is what that exception exists for (the
|
|
338
|
+
caret, and re-focus).
|
|
339
|
+
|
|
340
|
+
- **`variant="tonal"` now reads as disabled in the dark theme, where it rested on desaturation alone.**
|
|
341
|
+
Measured on `/components/button`: the disabled label was **1.11:1** from the enabled one (#778ff8 →
|
|
342
|
+
#979eb5) and the fill **1.20:1**, so the only signal was a hue going grey — and the label sat at 5.51:1
|
|
343
|
+
on its own fill, which reads as a live control. Tonal now takes the same 40% label mix ghost, text and
|
|
344
|
+
outline already use, toward `--surface-default`: the state gap becomes **2.90:1** in dark and **3.39:1**
|
|
345
|
+
in light, and the label keeps its hue instead of turning grey. **Toward the surface and not toward
|
|
346
|
+
tonal's own fill, even though the label sits on that fill** — the disabled fill has already moved
|
|
347
|
+
toward the label, so mixing into it yields only 2.56:1. The fill itself still barely moves (1.09:1
|
|
348
|
+
light, 1.20:1 dark) and does not need to: the label carries the state, which is the same division of
|
|
349
|
+
labour the transparent variants shipped with in 0.10.1. Override with
|
|
350
|
+
`--ds-button-label-color-disabled` as before.
|
|
351
|
+
|
|
352
|
+
- **`ds-multi-select`'s panel follows `--ds-dropdown-panel-radius` like the other two.** Its panel
|
|
353
|
+
element is `class="panel"`, not `.dropdown-panel`, so it never picked up the shared overlay rule and
|
|
354
|
+
sat at a hardcoded `--radius-md` (8px) while `ds-select` and `ds-autocomplete` moved with the token. It
|
|
355
|
+
now resolves the same chain, so a brand that rounds its dropdowns rounds all three.
|
|
356
|
+
|
|
357
|
+
- **`ds-date-picker`: a click on the host's own empty width now dismisses the open calendar.** The
|
|
358
|
+
outside-pointer guard treated the whole host element as the trigger, but the visible trigger box
|
|
359
|
+
hugs its mask while the host takes whatever a consumer's layout gives it — `flex-grow: 1` beside a
|
|
360
|
+
Clear button leaves a wide bare strip between the field and the button, and a click there kept the
|
|
361
|
+
calendar open with no visible reason (mm-broker MBP-225). The guard now tests the trigger box
|
|
362
|
+
itself: a press on the field or its calendar glyph still keeps the panel up, while the label, the
|
|
363
|
+
message row and the host's empty width dismiss it like any other outside click.
|
|
364
|
+
|
|
365
|
+
### What you can now DELETE
|
|
366
|
+
|
|
367
|
+
None of this is required — skipping it leaves working code that is merely redundant. Each row is a
|
|
368
|
+
workaround written against a hook that only landed in this release.
|
|
369
|
+
|
|
370
|
+
| If you have | Delete it, because |
|
|
371
|
+
| --- | --- |
|
|
372
|
+
| A hand-rolled second line inside a `ds-menu-item` — a projected span, a `max-width` near `14rem`, and probably no `aria-describedby` | The `description` input, capped by `--ds-menu-item-description-max-width` |
|
|
373
|
+
| `overflow: visible` forced back onto an element that needs to clip, or your own inset shadow standing in for a focus ring | `data-focus="inset"` on the clipping element |
|
|
374
|
+
| A `border-radius` override aimed at `ds-multi-select .panel` alone | `--ds-dropdown-panel-radius` now reaches all three connected panels |
|
|
375
|
+
| A timer of your own around a `ds-search` Clear button, or a value written twice to make the debounce let go | `clear()` |
|
|
376
|
+
| A copy of the config fallback chain in your own host — `this.size() ?? config.control?.size ?? 'md'` | The component's resolver is public now; read `sizeResolved()` |
|
|
377
|
+
| Your own wash replacing the solid active sidenav pill — a `--ds-sidenav-item-bg-color-active` override plus a matching label colour | That IS the default now; compare yours against it and drop it if they agree |
|
|
378
|
+
| `--ds-sidenav-item-rail: transparent`, or a `::ng-deep` box-shadow reset to hide the active rail | `[rail]="false"` on `ds-sidenav` |
|
|
379
|
+
| A `::ng-deep` `border-radius` rule on a bare `ds-menu` | `--ds-menu-radius` |
|
|
380
|
+
| `--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
|
+
| `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
|
+
| 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` |
|
|
383
|
+
|
|
11
384
|
## 0.10.1 — 2026-08-20
|
|
12
385
|
|
|
13
386
|
### Removed
|
|
@@ -192,8 +565,8 @@ While the package is on `0.x`, minor releases may contain breaking changes.
|
|
|
192
565
|
mix (0.036 → 0.099 light), so the disabled label stays tinted rather than going grey; that was
|
|
193
566
|
chosen deliberately over a desaturating variant after looking at both.
|
|
194
567
|
**`solid` and `tonal` are unchanged**, deliberately: a white label mixed into a white surface does
|
|
195
|
-
not move, and tonal's disabled fill already carries the state on its own.
|
|
196
|
-
mix target is `--surface-default`, a stand-in for "whatever is behind" — CSS cannot read the actual
|
|
568
|
+
not move, and tonal's disabled fill already carries the state on its own.
|
|
569
|
+
**Known limitation:** the mix target is `--surface-default`, a stand-in for "whatever is behind" — CSS cannot read the actual
|
|
197
570
|
backdrop, so on a tinted ground (a card at `--surface-secondary`, an alert) the disabled label is
|
|
198
571
|
computed against the page colour rather than that ground. Consumers who set
|
|
199
572
|
`--ds-button-label-color-disabled` are unaffected.
|
|
@@ -229,6 +602,14 @@ While the package is on `0.x`, minor releases may contain breaking changes.
|
|
|
229
602
|
`DsFieldBase` is internal and deliberately not exported — it holds only the inputs every field has,
|
|
230
603
|
which is why `success`, `label`, `required` and `optional` stayed on the components.
|
|
231
604
|
|
|
605
|
+
### What you can now DELETE
|
|
606
|
+
|
|
607
|
+
None of this is required — skipping it leaves working code that is merely redundant. Each row is a workaround this release made unnecessary.
|
|
608
|
+
|
|
609
|
+
| If you have | Delete it, because |
|
|
610
|
+
| --- | --- |
|
|
611
|
+
| A `?? ''` guard wrapped around a message binding - `[error]="form.errors?.message ?? ''"` - added because a null pushed into `hint` / `error` / `warning` / `success` threw a TypeError during render. | nothing - bind the expression directly, the inputs absorb null now |
|
|
612
|
+
|
|
232
613
|
## 0.10.0 — 2026-08-18
|
|
233
614
|
|
|
234
615
|
### Added
|
|
@@ -299,10 +680,7 @@ While the package is on `0.x`, minor releases may contain breaking changes.
|
|
|
299
680
|
The two signals are read-only — a subclass that used to `.set()` them (they were protected writables)
|
|
300
681
|
drives them through `runExport()` now.
|
|
301
682
|
|
|
302
|
-
- **`provideDsConfig` answers seven more inputs
|
|
303
|
-
itself.** Five of the release's eight new sections — `avatar`, `brand` and `modal` have their own
|
|
304
|
-
entries:
|
|
305
|
-
`control.size` (honoured by button, icon-button, input, textarea, select, autocomplete, search,
|
|
683
|
+
- **`provideDsConfig` answers seven more inputs, so an app stops restating itself.** Five new sections: `control.size` (honoured by button, icon-button, input, textarea, select, autocomplete, search,
|
|
306
684
|
date/time picker, number stepper, checkbox, radio, switch and field-group), `card.elevation` and
|
|
307
685
|
`card.padding`, `table.stickyScrollbar` and `table.bordered`, `icon.size`, and `badge.withDot`.
|
|
308
686
|
Precedence is **input → config → built-in**, so a screen that differs still binds the attribute and
|
|
@@ -349,7 +727,7 @@ While the package is on `0.x`, minor releases may contain breaking changes.
|
|
|
349
727
|
|
|
350
728
|
- **`--ds-dropdown-panel-radius` — the lever 0.9.0's notes promised and never shipped.** That release
|
|
351
729
|
said an 8px select panel could be restored with `--ds-select-panel-radius`; no such token existed,
|
|
352
|
-
so the advice did nothing
|
|
730
|
+
so the advice did nothing. This is the honest version, and it is
|
|
353
731
|
panel-level rather than per-component on purpose: retuning one picker's corner is not a thing to
|
|
354
732
|
encourage, while `--ds-radius-panel` moves modal, popover and date picker too. Defaults to that
|
|
355
733
|
role, so an untouched theme is unchanged, and it is forwarded onto the portaled pane — scope it with
|
|
@@ -674,6 +1052,12 @@ While the package is on `0.x`, minor releases may contain breaking changes.
|
|
|
674
1052
|
specificity. **If you deliberately suppressed a focus ring** by leaving an element unstyled, it will now
|
|
675
1053
|
show one; give that element `box-shadow: none` explicitly. Note the rule also drops the outline such an
|
|
676
1054
|
element used to get from the browser, so if an `outline` was what you wanted there, declare it yourself.
|
|
1055
|
+
**The case that actually bites, added 2026-08-21 after a consumer hit it fourteen times:** an app rule
|
|
1056
|
+
that styles `:focus-visible` with an **`outline` only**. That rule keeps winning on `outline`, but it
|
|
1057
|
+
says nothing about `box-shadow`, so the base rule still supplies one and the element renders **both** —
|
|
1058
|
+
a second ring in the app's colour around the DS ring. Nothing fails a build and nothing greps for it:
|
|
1059
|
+
the app rule looks untouched because it is. Add `box-shadow: none` to that rule, or — better, and what
|
|
1060
|
+
this release is for — delete the rule and retint the DS ring through `--ds-control-focus-shadow`.
|
|
677
1061
|
|
|
678
1062
|
- **A disabled `ds-button` / `ds-icon-button` now reads as disabled on a COLOURED accent.** One label recipe
|
|
679
1063
|
for every variant — `oklch(from accent 70% 0.035 h)` — replacing the 58% default, and on `ds-button` the
|
|
@@ -957,6 +1341,32 @@ While the package is on `0.x`, minor releases may contain breaking changes.
|
|
|
957
1341
|
could `.set()` — and a plain `private pending: … = null` is not a field the parser recognises, which
|
|
958
1342
|
is how `SearchComponent`'s `pending` and `pushed` sit outside its reported seven.
|
|
959
1343
|
|
|
1344
|
+
### What you can now DELETE
|
|
1345
|
+
|
|
1346
|
+
None of this is required — skipping it leaves working code that is merely redundant. Each row is a workaround this release made unnecessary.
|
|
1347
|
+
|
|
1348
|
+
| If you have | Delete it, because |
|
|
1349
|
+
| --- | --- |
|
|
1350
|
+
| A `ResizeObserver`, a container query or a hand-tuned per-breakpoint `maxVisibleChips` number, keeping a chip trigger on one line. | `maxVisibleChips="fit"`, which re-splits on any width change rather than at the breakpoints you listed |
|
|
1351
|
+
| A `max-height` plus `overflow: hidden` on a chip trigger, stopping it growing a line per selection - it clips a chip mid-glyph and hides the count. | `maxVisibleChips` (a number, or `"fit"`), which drops whole chips and reports how many are hidden |
|
|
1352
|
+
| Your own `max-height` on a logo projected into `ds-sidenav`'s `[brand]` slot, or a wrapper sized to hold it. | `--ds-sidenav-brand-max-height` (default `none`, so nothing changes until you set it) |
|
|
1353
|
+
| A global rule against `.ds-dropdown-panel` or `.cdk-overlay-pane` to change a dropdown corner. | `--ds-dropdown-panel-radius`, which scopes to one picker when written under a component selector |
|
|
1354
|
+
| A query for `ds-autocomplete`'s inner `<input>` plus a synthetic `input` event, clearing leftover filter text after a pick. | `clear()` - and the component clears that text itself now |
|
|
1355
|
+
| A local `.link-button` class, or a padding / border / background / font reset on `button.link` in your overrides. | the global `.link` class with `.inline` / `.standalone` / `.sm` / `.xs` |
|
|
1356
|
+
| A `[dsStatValue]` projection used only to set `white-space: normal` or a smaller font size on a TEXT value. | the two hooks on the ordinary `value` input - keep the slot for a value that is genuinely another component, like a badge |
|
|
1357
|
+
| A wrapper around `ds-search` adding a typing debounce (typically 200ms) with an immediate path when the field empties. | `[debounce]`, which does both plus the Enter flush |
|
|
1358
|
+
| `--ds-button-height` / `--ds-button-font-size` / `--ds-button-pad-x` pinned under `ds-filter-bar` to force its trigger smaller. | `triggerSize="sm"` |
|
|
1359
|
+
| `[dividers]="false"` repeated on every modal (one consumer had 41), or a reach into `.modal > .header` / `.body` / `.actions` with `!important` because hiding the rules left the padding stacked. | `provideDsConfig({ modal: { dividers: false } })`, which drops the rules AND the padding that existed to clear them |
|
|
1360
|
+
| A helper keeping the last visited tab per path in `sessionStorage`. | `rememberLastTab` on `ds-tabs` (needs `urlParam`, which supplies the names) |
|
|
1361
|
+
| An adapter component that injects a brand object and fans it out into `brand` / `logoLetter` / `tagline` bindings on each auth screen. | `provideDsConfig({ brand: … })`; the accent stays a `[dsBrandName]` projection instead of a `brandAccent` string plus an `indexOf` split |
|
|
1362
|
+
| The `ds-avatar` wiring around your own initials helper (the helper itself stays yours). | `[name]` plus one `[initialsRule]` |
|
|
1363
|
+
| An attribute repeated identically on every element - one consumer binds `[stickyScrollbar]="true"` on all 35 of its tables and `size="sm"` on 146 buttons. | `provideDsConfig` with the matching section (`table`, `control.size`, …) |
|
|
1364
|
+
| A button wired to `exportCsv()` on a SERVER-PAGED table - it serialises the rows the table holds, so the file is one page. | `runExport()` with an `exportFetcher` |
|
|
1365
|
+
| The computed beside every list table - `items().length > 0 ? 'overlay' : 'skeleton'` - one consumer feature carried three copies of it. | `[loading]="true"`, which resolves the treatment itself; pin a value only where you mean to override the rule |
|
|
1366
|
+
| 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
|
+
| A `::ng-deep ds-table { .table th, .table td { width: 1%; white-space: nowrap } }` override - the shrink-to-content idiom. | `TableColumn.width: 'content'` |
|
|
1368
|
+
| 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` |
|
|
1369
|
+
|
|
960
1370
|
## 0.9.1 — 2026-08-10
|
|
961
1371
|
|
|
962
1372
|
### Added
|
|
@@ -1058,14 +1468,14 @@ genuine gap worth reporting.
|
|
|
1058
1468
|
|
|
1059
1469
|
### Changed (breaking, visual)
|
|
1060
1470
|
|
|
1061
|
-
- **The `ds-select`
|
|
1062
|
-
|
|
1063
|
-
|
|
1471
|
+
- **The `ds-select` dropdown panel has a 12px corner, was 8px.** It was the one panel outside the
|
|
1472
|
+
radius role layer — modal, popover, date picker, time picker, autocomplete, bottom sheet, stat and
|
|
1473
|
+
page footer all resolve `--ds-radius-panel` — so it disagreed with its siblings by 4px and could
|
|
1064
1474
|
not be retuned through the role consumers are told to use. Restore with `--ds-radius-panel: 8px`,
|
|
1065
|
-
which moves every panel together
|
|
1066
|
-
`--ds-select-panel-radius
|
|
1067
|
-
|
|
1068
|
-
|
|
1475
|
+
which moves every panel together; there is no per-panel token for the select, and
|
|
1476
|
+
`--ds-select-panel-radius` does not exist. `ds-multi-select` is not part of this: its panel is a
|
|
1477
|
+
separate element with a hardcoded `border-radius: var(--radius-md)` that the shared rule does not
|
|
1478
|
+
reach, so it stays at 8px.
|
|
1069
1479
|
|
|
1070
1480
|
- **Seven exit `@keyframes` are gone, replaced by four global presets.** `modal-out`, `ds-sheet-fade-out`
|
|
1071
1481
|
and `drawer-scrim-out` become `ds-fade-out`; `ds-sheet-down` and the four `drawer-panel-close-*` become
|
|
@@ -2370,6 +2780,15 @@ genuine gap worth reporting.
|
|
|
2370
2780
|
scrim click-to-close, panel-scoped plus document-level Escape, `animationend` teardown, and the focus
|
|
2371
2781
|
trap are all unchanged.
|
|
2372
2782
|
|
|
2783
|
+
### What you can now DELETE
|
|
2784
|
+
|
|
2785
|
+
None of this is required — skipping it leaves working code that is merely redundant. Each row is a workaround this release made unnecessary.
|
|
2786
|
+
|
|
2787
|
+
| If you have | Delete it, because |
|
|
2788
|
+
| --- | --- |
|
|
2789
|
+
| A logo overlaid or absolutely positioned on top of ds-sidenav's brand row, written when there was no slot for one. | project it into `[brand]` |
|
|
2790
|
+
| 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
|
+
|
|
2373
2792
|
## 0.6.1 — 2026-07-16
|
|
2374
2793
|
|
|
2375
2794
|
### Fixed
|