@ids-group-ltd/ids-design-system 0.8.0 → 0.9.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 +377 -0
- package/components.md +500 -0
- package/design-system.md +145 -0
- package/fesm2022/ids-group-ltd-ids-design-system.mjs +1245 -371
- package/fesm2022/ids-group-ltd-ids-design-system.mjs.map +1 -1
- package/migrations/0.9.0.json +157 -0
- package/migrations/README.md +8 -1
- package/migrations/unreleased/README.md +134 -0
- package/package.json +1 -1
- package/styles/_dropdown-overlay.scss +34 -7
- package/styles/_field-box.scss +8 -3
- package/styles/_surface-motion.scss +48 -3
- package/styles/_tokens.scss +1 -4
- package/types/ids-group-ltd-ids-design-system.d.ts +631 -113
package/CHANGELOG.md
CHANGED
|
@@ -8,6 +8,383 @@ While the package is on `0.x`, minor releases may contain breaking changes.
|
|
|
8
8
|
|
|
9
9
|
## Unreleased
|
|
10
10
|
|
|
11
|
+
## 0.9.0 — 2026-08-10
|
|
12
|
+
|
|
13
|
+
### Changed (breaking, behaviour)
|
|
14
|
+
|
|
15
|
+
- **`ds-table` `sortMode` and `filterMode` default to `'server'`, were `'client'`.** Server-paged is the
|
|
16
|
+
normal case, and there the old default was actively wrong: the table sorted the current page, so the
|
|
17
|
+
rows looked sorted and were not — a dev warning existed only to say so. An undeclared table now emits
|
|
18
|
+
`(sortChange)` / updates `columnFilters` and reorders nothing itself. **A table that holds every row
|
|
19
|
+
must now declare `sortMode="client"` / `filterMode="client"`**; the dev warning has been turned around
|
|
20
|
+
to catch exactly that case (no `total` bound + sortable or filterable columns + no declared mode).
|
|
21
|
+
|
|
22
|
+
### Changed (breaking, visual)
|
|
23
|
+
|
|
24
|
+
- **The `ds-select` / `ds-multi-select` dropdown panel has a 12px corner, was 8px.** It was the one panel
|
|
25
|
+
outside the radius role layer — modal, popover, date picker, time picker, autocomplete, bottom sheet, card,
|
|
26
|
+
stat and page footer all resolve `--ds-radius-panel` — so it disagreed with its siblings by 4px and could
|
|
27
|
+
not be retuned through the role consumers are told to use. Restore with
|
|
28
|
+
`--ds-select-panel-radius: 8px`, or `--ds-radius-panel: 8px` to move every panel together.
|
|
29
|
+
|
|
30
|
+
- **Seven exit `@keyframes` are gone, replaced by four global presets.** `modal-out`, `ds-sheet-fade-out`
|
|
31
|
+
and `drawer-scrim-out` become `ds-fade-out`; `ds-sheet-down` and the four `drawer-panel-close-*` become
|
|
32
|
+
`ds-slide-edge-out`. They were view-encapsulated, so referencing one was only possible from a global
|
|
33
|
+
stylesheet — but if you did, that is the mapping. Nothing about the rendered motion changed.
|
|
34
|
+
|
|
35
|
+
- **`ds-search` is 40px tall by default, was 36px.** It was the only control in the library on that
|
|
36
|
+
height — `ds-button`, `ds-input`, `ds-select` and both pickers all resolve `--field-h-md` — so a search
|
|
37
|
+
box in a toolbar sat a step short of everything beside it. All three sizes now come off the field scale
|
|
38
|
+
(sm 32 / md 40 / lg 48; only md moved). Restore with `ds-search { --ds-search-height: 36px; }`. The
|
|
39
|
+
height also falls through `--ds-field-height` now, so one token levels a whole toolbar.
|
|
40
|
+
|
|
41
|
+
- **The global `--search-h` token is gone.** It existed only to hold that 36px and nothing reads it.
|
|
42
|
+
Use `--ds-search-height` to retune search alone, or `--ds-field-height` for the family.
|
|
43
|
+
|
|
44
|
+
### Changed
|
|
45
|
+
|
|
46
|
+
- **`ds-auth-layout` compresses its own chrome on a short viewport, so the layout is never the reason a
|
|
47
|
+
card scrolls.** Block padding, the column gap, the letter-mark tile and the masthead's inner gap clamp
|
|
48
|
+
against `svh`. At ~330px of viewport — a landscape phone — that furniture costs ~131px instead of ~219px.
|
|
49
|
+
Every multiplier reaches its maximum at a viewport **800px tall or more** — a viewport height, not a
|
|
50
|
+
screen size: a 1366x768 laptop sits near 630px once browser and OS chrome come off, and a 1080p screen at
|
|
51
|
+
150% display scaling near 585px, so a good many desktops render the compressed furniture too.
|
|
52
|
+
**Type is deliberately excluded.** An earlier draft clamped the wordmark and the tile's glyph as well;
|
|
53
|
+
both were measured to buy zero vertical space — the wordmark shares a flex row with the tile, whose height
|
|
54
|
+
exceeds the wordmark's line box at every viewport height, and the glyph sits in a fixed-size grid box —
|
|
55
|
+
while shrinking the brand against a fixed 14px tagline, worst for the users who scale their display up.
|
|
56
|
+
Both are back to the fixed sizes 0.8.0 ships.
|
|
57
|
+
`svh` rather than `dvh` because the dynamic unit changes as a mobile URL bar hides, which would re-space
|
|
58
|
+
the column mid-scroll; `min-height` stays on `dvh` so no strip of body background shows when the bar
|
|
59
|
+
retracts. New opt-outs: `--ds-auth-layout-pad-block` and `--ds-auth-layout-mark-size` (set
|
|
60
|
+
either, or the existing `-gap`, to a fixed value and that dimension stops compressing). A card taller than
|
|
61
|
+
the space left still scrolls — deliberately, because the alternative (pinning the masthead and footer out
|
|
62
|
+
of the flow) frees more room but lets chrome overlap a tall form.
|
|
63
|
+
|
|
64
|
+
- **`ds-auth-layout` — a round of fixes from an audit of the above.** All additive or corrective; nothing
|
|
65
|
+
to migrate. The letter-mark is now `aria-hidden`, so a screen reader announces "MyAdmin" rather than
|
|
66
|
+
"A MyAdmin"; it also carries `flex-shrink: 0`, so a long wordmark can no longer squash the square tile
|
|
67
|
+
into a rectangle. `logoLetter` on its own renders its tile instead of nothing (the outer gate never
|
|
68
|
+
tested it). The glyph is taken with a code-point split rather than `charAt(0)`, which returned half a
|
|
69
|
+
surrogate pair for a brand starting with an emoji. `box-sizing: border-box` is declared on the host
|
|
70
|
+
rather than inherited, because the documented à-la-carte style path omits `styles/reset` and without it
|
|
71
|
+
`min-height: 100dvh` plus the block padding overflows by exactly that padding — the scrollbar this
|
|
72
|
+
component exists to avoid. The four `env(safe-area-inset-*)` calls gained `0px` fallbacks and moved to
|
|
73
|
+
physical `padding-left`/`padding-right`, since the safe area belongs to the device and must not swap
|
|
74
|
+
sides with text direction; note the insets are inert unless the **host app** sets `viewport-fit=cover`
|
|
75
|
+
in its viewport meta, which the library cannot do and did not previously say. New tokens, both
|
|
76
|
+
defaulting to today's behaviour: `--ds-auth-layout-mark-radius` (the tile's radius was the one value
|
|
77
|
+
with no override hop) and `--ds-auth-layout-brand-max-height` (`none` by default — set it to cap a
|
|
78
|
+
projected `[brand]` logo, which nothing constrained). New input `landmark` (`'none'` by default): the
|
|
79
|
+
card holds the whole content of an auth screen but `ds-card` renders an `<article>`, which is not a
|
|
80
|
+
landmark, so `landmark="main"` gives a screen-reader user something to jump to on a standalone auth
|
|
81
|
+
page. It is opt-in because the layout is also embedded inside pages that already own a `main`.
|
|
82
|
+
|
|
83
|
+
- **BREAKING: `ds-auth-shell` is renamed `ds-auth-layout`** (`AuthShellComponent` → `AuthLayoutComponent`,
|
|
84
|
+
and `--ds-auth-shell-*` → `--ds-auth-layout-*`). "Shell" is not this library's word for a layout — the
|
|
85
|
+
app-level one was renamed `ds-app-shell` → `ds-app-layout` back in 0.7.0, and shipping an auth counterpart
|
|
86
|
+
called a shell in 0.8.0 reintroduced the split vocabulary that rename existed to remove. Mechanical:
|
|
87
|
+
rename the tag, the class and the six tokens. Nothing about the behaviour or the slots changes.
|
|
88
|
+
|
|
89
|
+
### Changed (internal, no action)
|
|
90
|
+
|
|
91
|
+
- **`--ds-radius-inner` now reaches the small affordances it was written for.** Thirty-three reads across
|
|
92
|
+
fifteen component stylesheets took `var(--radius-sm)` directly — dropdown options, field clear buttons,
|
|
93
|
+
calendar days, chips, tag and toast close buttons — so the role a consumer is told to retune reached
|
|
94
|
+
exactly one component. Nothing moves (the role's default IS `--radius-sm`, verified by measuring a page
|
|
95
|
+
before and after), but it changes what a square brand costs: zeroing the three radius roles used to leave
|
|
96
|
+
five surfaces rounded and now squares every one. Five focus-ring radii inside `:focus-visible` keep
|
|
97
|
+
following the raw scale deliberately — a ring traces a box, it is not a surface a brand designs.
|
|
98
|
+
|
|
99
|
+
### Added
|
|
100
|
+
|
|
101
|
+
- **Exit motion is swappable, the way entrances already were** — `--ds-modal-leave-keyframes`,
|
|
102
|
+
`--ds-drawer-leave-keyframes` and `--ds-bottom-sheet-leave-keyframes`, plus four global presets that
|
|
103
|
+
mirror the entrance vocabulary (`ds-fade-out`, `ds-scale-out`, `ds-slide-out`, `ds-slide-edge-out`).
|
|
104
|
+
This was blocked by a real constraint the code documented: teardown matched the animation NAME on
|
|
105
|
+
`animationend`, so renaming the keyframe broke closing entirely. The guard now checks that the event came
|
|
106
|
+
from the animated element rather than from a child, which frees the name — and that same check collapsed
|
|
107
|
+
the drawer's four direction-specific exits into one preset, since an exit reads `--_ds-exit-x/y/scale`
|
|
108
|
+
and falls back to the matching `--_ds-enter-*`. Point a token at your own **global** `@keyframes`; a
|
|
109
|
+
component-scoped name is renamed by Angular and will not resolve.
|
|
110
|
+
|
|
111
|
+
- **Signal Forms bind to every DS control, with no wrapper and no adapter** — `<ds-input [formField]="f.email" />`
|
|
112
|
+
and the form owns the value, the validation, `touched`, `disabled` and the error text. This was very nearly
|
|
113
|
+
true already and nobody knew: `FormValueControl` requires exactly one member, a `value` `model()`, and all
|
|
114
|
+
fifteen controls had it. Measured across all of them — thirteen bound with no library change at all. What
|
|
115
|
+
was fixed here: `min`/`max`/`maxLength` on `ds-input`, `ds-textarea` and `ds-number-stepper` now accept
|
|
116
|
+
`undefined` on the write side (the binder sends it for an unset bound; read types are untouched);
|
|
117
|
+
`readonly` joins `ds-input`, `ds-textarea` and `ds-select` as the contract spelling of the existing
|
|
118
|
+
`readOnly`, because signal forms binds by NAME and a `readonly()` rule was reaching nothing; `minLength`
|
|
119
|
+
and `pattern` are new native attributes on `ds-input` and `ds-textarea`; `hidden` is declared on both
|
|
120
|
+
control-value-accessor bases, so a `hidden()` rule removes the control on all thirteen that carry one; and
|
|
121
|
+
`focus()` resolves the element that holds the value, so `focusBoundControl()` reaches the stepper's number
|
|
122
|
+
box rather than its minus button and the tabbable radio rather than the first in the DOM. Not implemented:
|
|
123
|
+
`dirty`, `pending`, `disabledReasons`. Reactive and template-driven forms are untouched. Docs: **Practice →
|
|
124
|
+
Signal Forms**, with a live form and a contract table stating the measured state.
|
|
125
|
+
|
|
126
|
+
- **`ds-modal` takes a `[title-badge]` slot and a `subtitle`.** Two consumer screens had abandoned
|
|
127
|
+
`ds-modal` and hand-rolled a `.scrim` + `.panel` because the header could only hold one string — losing
|
|
128
|
+
the focus trap, focus restore, the scroll lock, Escape, the enter/leave animation and, in one case, the
|
|
129
|
+
footer, which put a destructive action beside the close button. Same shape as `ds-page-header`; `title`
|
|
130
|
+
stays the accessible name, so projected markup never enters `aria-labelledby`. Two tokens:
|
|
131
|
+
`--ds-modal-subtitle-text-color` and `-font-size`.
|
|
132
|
+
|
|
133
|
+
- **`[dividers]` on `ds-modal` / `ds-modal-card`, default `true`.** `[dividers]="false"` drops the header
|
|
134
|
+
and actions rules AND the vertical padding that existed to clear them, because those are one design
|
|
135
|
+
decision. Two consumers had set `--ds-modal-divider: transparent` and were left with a 35px gap where 16
|
|
136
|
+
was wanted; one needed `!important` to win it back.
|
|
137
|
+
|
|
138
|
+
- **`ds-table`: the rest of what mm-broker's fork did that the base could not.** Keyboard column resizing —
|
|
139
|
+
the handle is a focusable `role="separator"` with Arrow (16px), PageUp/PageDown (64px) and Home to hand
|
|
140
|
+
the column back to automatic sizing; a drag handle that answered only to a pointer made a resizable column
|
|
141
|
+
unusable without a mouse. `exportFetcher` may now resolve a `Blob` or a URL as well as rows, for a file
|
|
142
|
+
the backend already formatted, and `exportFailed` emits the rejection — swallowing it made a failed export
|
|
143
|
+
indistinguishable from a slow one. Two box tokens: `--ds-table-min-width` (a readability floor, default 0)
|
|
144
|
+
and `--ds-table-hscroll-bottom` (offsets the sticky scrollbar out of a padded container, default 0).
|
|
145
|
+
|
|
146
|
+
- **The three `ds-modal` regions take their padding from tokens** — `--ds-modal-pad-x` for the gutter all
|
|
147
|
+
three share, plus `--ds-modal-header-pad-y`, `-body-pad-y` and `-actions-pad-y`. Two consumers were
|
|
148
|
+
rewriting these, one with `!important`, because the regions are padded for a divider-separated layout:
|
|
149
|
+
set `--ds-modal-divider: transparent` and you are left with spacing sized for dividers that are no
|
|
150
|
+
longer there. Nothing moves by default. Note the tokens go on `ds-modal` AND `ds-modal-card` — a dialog
|
|
151
|
+
opened through `ModalService` renders the card with no `ds-modal` ancestor.
|
|
152
|
+
|
|
153
|
+
- **`maxItems` on `ds-breadcrumbs`** — collapses the middle of a deep trail into a crumb that says how
|
|
154
|
+
many it stands for, keeping the first and, crucially, the LAST. Without a cap the row is `nowrap` with
|
|
155
|
+
`overflow: hidden`, so an overlong trail is clipped from the END — hiding the current page, the one
|
|
156
|
+
crumb the reader needs most. Opt-in; every crumb still renders by default.
|
|
157
|
+
|
|
158
|
+
- **Dev warnings no longer repeat themselves.** Every component with one wrote the same four lines around
|
|
159
|
+
it — `isDevMode`, an `effect`, a condition, a `console.warn` — and each copy shared the same flaw: the
|
|
160
|
+
effect re-runs when ANY signal it read changes, so a warning about a static misconfiguration could be
|
|
161
|
+
logged again on every keystroke. They now go through one internal helper that fires at most once per
|
|
162
|
+
message. Eleven hand-written warnings across `ds-button`, `ds-stat` and `ds-table` moved onto it —
|
|
163
|
+
ten call sites at HEAD, since the table gained more with lazy loading. `ds-tabs` keeps its own, because
|
|
164
|
+
its effect also owns registry bookkeeping that a plain warning cannot express.
|
|
165
|
+
|
|
166
|
+
- **`maxVisibleChips` on `ds-autocomplete`** — caps the chips in the trigger and collapses the rest into
|
|
167
|
+
"+N more". Without it a multi-select trigger grows a line per selection and pushes the rest of the form
|
|
168
|
+
down the page, which is how it was reported. Same input name, same transform and same wording as
|
|
169
|
+
`ds-multi-select`, which already had it — the two multi-value pickers should not diverge on this.
|
|
170
|
+
Backspace still removes the last SELECTED chip, not the last visible one.
|
|
171
|
+
|
|
172
|
+
- **`ds-stat` takes a projected value** — `[dsStatValue]` for a tile whose headline is a badge, a status
|
|
173
|
+
dot or anything a number slot cannot hold. `value` is now optional and acts as the fallback, the same
|
|
174
|
+
shape `[delta]` already had; existing tiles are untouched. The slot is namespaced on purpose: twenty
|
|
175
|
+
components in this library have a `value` input, so a bare `value` attribute would have set theirs to
|
|
176
|
+
the empty string on the way past. A dev warning fires if `unit` is set with no `value`, since a
|
|
177
|
+
projected headline owns the whole line and the suffix would silently vanish.
|
|
178
|
+
|
|
179
|
+
- **The package now ships `design-system.md` and `components.md`.** `design-system.md` is no longer a
|
|
180
|
+
catalogue: it carries the RULES — which spacing token goes between what, which type role a piece of
|
|
181
|
+
text takes, the field-height contract, who owns a gap, and how to override a component (including the
|
|
182
|
+
two things that break it: reaching for an internal class, and portaled panels). The 491-line inventory
|
|
183
|
+
it used to be moved to `components.md`. Both are readable from `node_modules`, so a consumer's agents
|
|
184
|
+
and tooling can follow the system instead of guessing plausible token values.
|
|
185
|
+
|
|
186
|
+
- **`ds-tabs` warns when two strips claim the same `urlParam`.** Both write the same query parameter, so
|
|
187
|
+
each erases the other's tab and a reload restores whichever wrote last — nothing throws and the URL
|
|
188
|
+
looks plausible. It is the easy mistake when turning `urlParam` on across an app, because `"tab"` is the
|
|
189
|
+
obvious name every time. Dev-mode only.
|
|
190
|
+
|
|
191
|
+
- **Selected dropdown rows have their own hooks** — `--ds-option-selected-bg-color`, `-label-color`,
|
|
192
|
+
`-bg-color-hover` and `--ds-option-check-color`, defaulting to the theme roles they used to read
|
|
193
|
+
directly. A brand that wanted a different selected treatment previously had to RETARGET `--primary-*`
|
|
194
|
+
inside `.ds-dropdown-panel` and then track what else in the panel read the same role. Panel-level: one
|
|
195
|
+
partial paints select, autocomplete and multi-select alike. Nothing moves by default.
|
|
196
|
+
|
|
197
|
+
- **`ds-field-group` — several controls in one bordered box** (`select + input`, `input + button`,
|
|
198
|
+
`input + select`). The group owns the border, the radius, the divider and a single `:focus-within` ring;
|
|
199
|
+
the controls inside render naked. Segments hug their content, `grow` takes the slack. `size` uses the
|
|
200
|
+
field height scale, plus `invalid` and `fullWidth`. A control knows it is a segment by injecting
|
|
201
|
+
`DS_FIELD_GROUP` rather than being told with an input — the alternative is manual, and one segment where
|
|
202
|
+
it was forgotten draws its own border mid-row. Six controls can be segments: `ds-input`, `ds-select`,
|
|
203
|
+
`ds-search`, `ds-autocomplete`, `ds-date-picker` and `ds-button`. Not `ds-number-stepper` (a composite
|
|
204
|
+
already) or `ds-multi-select` (its chips wrap, which a fixed-height row cannot take). Grouped controls must not carry a `label` or `hint` — the message row
|
|
205
|
+
would break the glued line, so it is suppressed and a group-level one is not built.
|
|
206
|
+
|
|
207
|
+
- **`ds-table` lazy loading** — `[lazy]` plus a `(lazyLoad)` output emitting `{ first, rows }` for the
|
|
208
|
+
range now on screen. `data` becomes a sparse array `total` long: write each fetched row at its absolute
|
|
209
|
+
index, and every gap inside the window renders a skeleton row until it arrives. The scroller is sized
|
|
210
|
+
from `total` rather than from what has arrived, so the scrollbar tells the truth from the first frame.
|
|
211
|
+
Needs `virtualScroll` (there is no window to fetch against otherwise) and `total`; a request is not
|
|
212
|
+
re-sent while the range it covered is still on screen. Dev warnings cover all three ways to wire it
|
|
213
|
+
wrong, including `sortMode="client"`, which would sort only the rows that happen to have loaded.
|
|
214
|
+
|
|
215
|
+
- **`[quiet]` on `ds-menu-item`** — a muted row for a secondary action like "Sign out" under a divider,
|
|
216
|
+
the sibling of the existing `[error]`. Recolouring one item was previously impossible through the
|
|
217
|
+
token: `--ds-menu-item-label-color` resolves on the host against the value inherited from `ds-menu`, so
|
|
218
|
+
setting it per item did not win and the colour had to go on the inner element. `[error]` still wins if
|
|
219
|
+
both are set. Colour comes from `--ds-menu-item-quiet-label-color`.
|
|
220
|
+
|
|
221
|
+
- **21 hooks for type and box values that a `font:`/`border:`/`padding` shorthand had swallowed.** Same
|
|
222
|
+
shape every time: the value sat inside a shorthand, so overriding the one property meant a selector
|
|
223
|
+
out-ranking the shimmed component rule. `ds-description-item` completes the eyebrow set both halves
|
|
224
|
+
(`--ds-description-list-term-weight` / `-tracking` / `-transform`, `-details-font-size` / `-weight`) —
|
|
225
|
+
the same five `ds-field-label` and the modal eyebrow already exposed. `ds-segmented` gains
|
|
226
|
+
`--ds-segmented-btn-border` (for a hairline chip row), `-btn-pad-x` and label type; `ds-tabs` gains
|
|
227
|
+
`--ds-tab-pad-top` / `-bottom` (an underline tab wants bottom-only and could not say so), label type,
|
|
228
|
+
`--ds-tabs-strip-gap` and `--ds-tabs-panel-pad-top`; `ds-menu` gains item padding, item label type and
|
|
229
|
+
`--ds-menu-gap`; `ds-checkbox` gains `--ds-checkbox-label-weight`, the third label property where size
|
|
230
|
+
and colour were already hookable. Every default reproduces today's value.
|
|
231
|
+
|
|
232
|
+
- **The theme's radius and elevation roles now reach portaled panels.** A pane lives under `<body>`, so
|
|
233
|
+
nothing component-scoped could reach it: squaring `--ds-radius-panel` left a square app with round
|
|
234
|
+
dropdowns, and the only fix was re-declaring the roles on `.ds-overlay-pane` globally. Roles now travel
|
|
235
|
+
with the tokens each component already forwards — but only where the host actually overrides the root,
|
|
236
|
+
so an open panel still follows a theme switch instead of pinning the value it opened with.
|
|
237
|
+
|
|
238
|
+
- **`--ds-badge-white-space`** (default `nowrap`, so nothing moves). A badge in a narrow, fixed-layout
|
|
239
|
+
table column has to be allowed to wrap or its label clips, and the property was the one thing on that
|
|
240
|
+
element not reachable through a token — the workaround was a global rule against the private `.badge`.
|
|
241
|
+
|
|
242
|
+
- **`showPageSize` and `showLabel` on `ds-table`**, forwarded to its footer pager. Both have always existed
|
|
243
|
+
on the standalone `ds-pagination` but were unreachable once the pager was inside a table, so hiding the
|
|
244
|
+
size picker on a fixed-page-size table meant a global selector reaching into the DS. Default `true` — no
|
|
245
|
+
change unless set.
|
|
246
|
+
|
|
247
|
+
- **`--ds-table-head-pad-top` / `--ds-table-head-pad-bottom`.** Header cells were the one padding in the
|
|
248
|
+
table that stayed symmetric — body cells have had per-side hooks since 07-31 — so a header wanting its
|
|
249
|
+
label tight to the top with air above the rule could only be reached with `!important`. Both fall back to
|
|
250
|
+
the density value, so nothing moves until one is set.
|
|
251
|
+
|
|
252
|
+
- **`ds-autocomplete` can be built as a search field.** `dsAutocompletePrefix` / `dsAutocompleteSuffix`
|
|
253
|
+
content slots — the same names and the same contract as `ds-input`'s addon slots — plus `[showChevron]`
|
|
254
|
+
(default `true`) to drop the trailing arrow, which on a search field invites a click that would list
|
|
255
|
+
everything. Previously a leading glyph had to be absolutely positioned over the field and the chevron
|
|
256
|
+
hidden with a global selector reaching for `.autocomplete-chevron`. Unlike a fixed `variant="search"`,
|
|
257
|
+
the slots also cover the icon-**and**-chevron case a combobox often wants.
|
|
258
|
+
|
|
259
|
+
- **`ds-autocomplete.clear()`**, emptying both the selected value and the text the user typed. Setting
|
|
260
|
+
`value` to null from outside left the typed query on screen, because the query is component state with no
|
|
261
|
+
input bound to it — so a host resetting the field after navigating had to query the inner `<input>` and
|
|
262
|
+
dispatch a synthetic `input` event at it. It deliberately does not move focus.
|
|
263
|
+
|
|
264
|
+
- **`--ds-autocomplete-panel-maxh`**, so the dropdown's height before it scrolls no longer needs the private
|
|
265
|
+
`--picker-maxh` (which `ds-multi-select` also reads, making it the wrong lever for one component).
|
|
266
|
+
|
|
267
|
+
- **`--ds-autocomplete-panel-radius`, bringing the last panel into the radius role layer.** Its dropdown was
|
|
268
|
+
the one portaled surface still hard-coding `--radius-lg` while modal, popover, card, bottom-sheet and both
|
|
269
|
+
picker panels resolve `--ds-radius-panel`, so a consumer who squared the three radius roles got a square
|
|
270
|
+
app with one rounded panel and no hook to reach it. Nothing moves by default — the role still resolves to
|
|
271
|
+
`--radius-lg` — and the token is forwarded onto the portaled pane on open like the other panel tokens.
|
|
272
|
+
|
|
273
|
+
- **`ds-app-layout` takes a `scrollReset` strategy, and `LayoutNavigationService` is public** (both asked
|
|
274
|
+
for by the ai-sdlc starter after their `ds-app-layout` migration). Owning the scroll CONTAINER had
|
|
275
|
+
quietly meant owning the POLICY: `scrollToTop()` was public so a screen could ADD a reset, but nothing
|
|
276
|
+
could suppress one the layout decided to do. `scrollReset: 'path' | 'never' | 'always'` defaults to
|
|
277
|
+
`'path'`, which is exactly today's behaviour — no consumer sees a change unless they set it. `'always'`
|
|
278
|
+
also resets on a query- or fragment-only navigation (what a server-paged list wants); `'never'` hands the
|
|
279
|
+
decision to the screen.
|
|
280
|
+
— Exporting the navigation service removes a duplication the layout was causing: "did the path change?"
|
|
281
|
+
was being re-derived per consumer, and one of them had THREE answers that disagreed, because a
|
|
282
|
+
`split('?')` keeps the fragment `pathChanged` strips. It is root-provided and stateless, so exposing it
|
|
283
|
+
costs nothing.
|
|
284
|
+
|
|
285
|
+
- **`ds-icon` warns in dev when a name resolves to nothing** (asked for by the ai-sdlc starter after an audit
|
|
286
|
+
found misspelled names on three screens). An unknown name rendered an empty `<svg>` in silence: the types
|
|
287
|
+
cannot catch it, because `IconName` stays open (`| (string & {})`) so a consumer can register their own
|
|
288
|
+
glyphs through `provideDsIcons()`, and closing the union would reject every registered name. The warning
|
|
289
|
+
names the offending value and sits on the one branch that knows — production pays a single falsy check.
|
|
290
|
+
|
|
291
|
+
### Fixed
|
|
292
|
+
|
|
293
|
+
- **Opening `ds-date-picker` with the mouse no longer takes the caret out of the field.** Clicking the
|
|
294
|
+
calendar glyph moved focus into the day grid, which a mouse user did not ask for and which, with
|
|
295
|
+
`allowInput` on by default, pulled them out of a field they may have been typing in. The glyph now behaves
|
|
296
|
+
like a click on the field itself: focus follows what the field IS — typeable keeps the caret, read-only
|
|
297
|
+
focuses the grid. The keyboard path is unchanged, ArrowDown still enters the grid however the panel opened.
|
|
298
|
+
|
|
299
|
+
- **A settled `ds-autocomplete` no longer shows an empty text box beside its value.** In single mode the
|
|
300
|
+
chosen label has always rendered as its own element, but the filter input stayed 80px wide next to it and
|
|
301
|
+
took the caret, so a field with a value read as free text rather than a picker. With a value and the panel
|
|
302
|
+
closed the input now collapses to zero width — it keeps focus, so clicking still opens the panel and
|
|
303
|
+
typing still filters.
|
|
304
|
+
|
|
305
|
+
- **A column resize no longer moves columns the reader never touched.** Only the dragged column had a width,
|
|
306
|
+
so the browser redistributed the remainder across the auto-sized rest and they visibly jumped. The first
|
|
307
|
+
resize — pointer or keyboard — now freezes every visible column at what it currently measures, once.
|
|
308
|
+
|
|
309
|
+
- **The clipped-cell popover reaches template cells, and a narrowed header keeps its label.** Clip detection
|
|
310
|
+
walks descendants, so overflow inside a `dsCellTemplate` behaves like a plain truncated cell; a header
|
|
311
|
+
narrowed by resizing gets a `title` with the full label on hover. Scoped to columns that asked for
|
|
312
|
+
`truncate` — a handler on every cell would swallow the row click on an interactive table.
|
|
313
|
+
|
|
314
|
+
- **`sortValue` string ordering is case- and accent-insensitive** (`sensitivity: 'base'`), matching the
|
|
315
|
+
comparator consumers are migrating off, so a column of strings does not silently reorder.
|
|
316
|
+
|
|
317
|
+
- **`--ds-field-height` now reaches six more controls.** `ds-autocomplete`, `ds-multi-select`,
|
|
318
|
+
`ds-color-picker`, `ds-number-stepper`, `ds-split-button` and the `ModalService` confirm input each
|
|
319
|
+
spelled their height as the raw `--hit-*` value, so the knob the token name advertises did nothing for
|
|
320
|
+
them. All six are on the `field-box-height` contract now, and no raw `--hit-cozy` height is left in the
|
|
321
|
+
library. Same pixels at every size **except `ds-number-stepper` at `size="lg"`, which goes 44px → 48px**
|
|
322
|
+
to match the family's large field; the other sizes are unchanged.
|
|
323
|
+
|
|
324
|
+
- **Date and time pickers keep step with the fields beside them under `[data-density]`.** Both triggers
|
|
325
|
+
hard-coded their horizontal padding, which happened to equal `--field-pad-x` at default density but did
|
|
326
|
+
not shrink with it — so setting a density left a picker 8px wider than the `ds-input` next to it. Both now
|
|
327
|
+
resolve `--ds-date-picker-trigger-pad-x` / `--ds-time-picker-trigger-pad-x` from the field family.
|
|
328
|
+
|
|
329
|
+
- **`ds-card`'s box fills a stretched host**, so a grid row of cards with unequal content paints equal
|
|
330
|
+
heights instead of a stretched host wrapping a short bordered box. `ds-stat` already did this; cards
|
|
331
|
+
needed a `::ng-deep .card { height: 100% }` from the consumer. Nothing changes where the host is
|
|
332
|
+
content-sized, which is every card not in a stretching row.
|
|
333
|
+
|
|
334
|
+
- **`density="compact"` no longer defeats every `ds-table` padding hook.** It pinned `padding` straight onto
|
|
335
|
+
the cells, which out-specifies the `--ds-table-cell-pad-*` and head hooks, so a compact table silently
|
|
336
|
+
ignored all of them. It now retunes the same density tokens `[data-density]` uses — identical spacing, and
|
|
337
|
+
the hooks apply.
|
|
338
|
+
|
|
339
|
+
- **`ds-date-picker`'s trigger stays visibly active while its own panel is open.** The indicator was bound to
|
|
340
|
+
focus only, and opening from the calendar glyph moves focus into the day grid — so the trigger went dark
|
|
341
|
+
while its panel was open, and the refocus on close made it read as a flicker.
|
|
342
|
+
|
|
343
|
+
- **`ds-table`: the three things that still forced a consumer wrapper.** All from mm-broker folding its
|
|
344
|
+
2160-line `ids-data-table` fork onto the base.
|
|
345
|
+
— **`filterMode: 'client' | 'server' | 'none'`**, mirroring `sortMode` — it shipped defaulting to
|
|
346
|
+
`'client'` and the default was flipped to `'server'` later in this same release, above — plus
|
|
347
|
+
**`columnFilterOptions`** for the real value domain. A header filter on a server-paged table was wrong
|
|
348
|
+
twice over: the checklist could only offer values from the page in hand, and the local pass then filtered
|
|
349
|
+
what the server had already filtered. `'server'` tracks `columnFilters` and filters nothing; `'none'`
|
|
350
|
+
drops the affordance. A dev warning catches the silent case — `filter: 'set'` with `total` bound and no
|
|
351
|
+
declared mode.
|
|
352
|
+
— **`dsHeaderFilter`**, a template slot for a criterion the checklist cannot express (a date range, a
|
|
353
|
+
numeric threshold, an async lookup). The table keeps the header button, the popover and the active-filter
|
|
354
|
+
styling; `active` on the directive tells the highlight whether your criterion is set, because only you
|
|
355
|
+
know. The context carries `close`, so the panel can dismiss itself after applying.
|
|
356
|
+
— **A live region for sort state and row range.** The table announced loading and nothing else, so a
|
|
357
|
+
screen-reader user got no confirmation that the order changed and paging never announced the new range.
|
|
358
|
+
One `role="status"` now carries both, with loading taking precedence while it lasts. `sortAnnouncement`
|
|
359
|
+
and `rangeAnnouncement` take the facts and return the sentence, so translation and word order stay with
|
|
360
|
+
the consumer.
|
|
361
|
+
|
|
362
|
+
- **`ds-tabs` keeps the active tab in the URL: `urlParam="tab"`** (asked for by the ai-sdlc starter). The
|
|
363
|
+
input both switches it on and names the parameter; leave it out and the URL is untouched. Names come from
|
|
364
|
+
each `ds-tab`'s `value` — the identifier `tabClosed` already emits — so there is no second list to keep in
|
|
365
|
+
step. The evidence for shipping it: in one admin port THREE of the four tabbed screens never got the
|
|
366
|
+
hand-wiring at all, so only the screen whose author reached for a helper worked.
|
|
367
|
+
— Names, not indices (`?tab=1` would repoint every old link the moment a tab is inserted); the first tab
|
|
368
|
+
writes no parameter and every write replaces (clean address, and flipping tabs does not fill the Back
|
|
369
|
+
button); an unknown or missing name lands on tab 0 rather than throwing. Outside a routed context the
|
|
370
|
+
input is inert — the router is injected optionally, so a strip in a dialog is unaffected.
|
|
371
|
+
|
|
372
|
+
- **Options in the picker panels had no pressed state.** Hover only — so on a phone, where there is no
|
|
373
|
+
hover, tapping a row in `ds-select`, `ds-autocomplete` or `ds-multi-select` gave no feedback that it had
|
|
374
|
+
been hit. The equivalent rows elsewhere (`ds-menu-item`, `ds-list-item`) have had one since 0.7.x. Fixed
|
|
375
|
+
once in the shared dropdown-overlay partial, so all three pickers get it, with a selected-row variant that
|
|
376
|
+
stays in the brand family rather than stranding the selected label colour on a neutral fill.
|
|
377
|
+
|
|
378
|
+
- **`ds-textarea size="sm"` and `="lg"` got the md vertical padding.** The size variants set the inner
|
|
379
|
+
`<textarea>`'s vertical pad (`--space-2` / `--space-4`), but the `:host`-prefixed pin at the end of the
|
|
380
|
+
file — added so the docs' unencapsulated `.field .control` specimen could not zero it — out-ranks them
|
|
381
|
+
once emulated encapsulation shims both selectors: `[_nghost] .field[_ngcontent] .control[_ngcontent]
|
|
382
|
+
textarea[_ngcontent]` carries one more attribute than `.field.sm[_ngcontent] …`. So every textarea
|
|
383
|
+
rendered with 12px top and bottom regardless of `size`, and retuning
|
|
384
|
+
`--ds-input-pad-y` moved all three. There are now three pins, one per size, and the size blocks keep
|
|
385
|
+
only the horizontal padding they own. Consumers see it only on a non-md textarea; the md default is
|
|
386
|
+
unchanged.
|
|
387
|
+
|
|
11
388
|
## 0.8.0 — 2026-08-05
|
|
12
389
|
|
|
13
390
|
### Added
|