@ids-group-ltd/ids-design-system 0.9.0 → 0.10.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.
@@ -20,7 +20,7 @@
20
20
  "kind": "behavior",
21
21
  "old": "--radius-md (8px) on the ds-select / ds-multi-select panel",
22
22
  "new": "--ds-radius-panel (12px)",
23
- "note": "CHANGED DEFAULT, visual: the dropdown panel behind ds-select and ds-multi-select has a 12px corner, was 8px. It was the one panel outside the radius role layer - modal, popover, date-picker, time-picker, autocomplete, bottom-sheet, card, stat and page-footer all resolve --ds-radius-panel already - so it both disagreed with its siblings and could not be retuned through the role a consumer is told to use. ACTION: none unless you want the old corner, in which case set --ds-select-panel-radius: 8px, or --ds-radius-panel: 8px to move every panel together. CHECK: a screen where a dropdown opens beside a popover or a date picker - that is where the 4px difference was visible and is now gone.",
23
+ "note": "CHANGED DEFAULT, visual: the dropdown panel behind ds-select and ds-multi-select has a 12px corner, was 8px. It was the one panel outside the radius role layer - modal, popover, date-picker, time-picker, autocomplete, bottom-sheet, card, stat and page-footer all resolve --ds-radius-panel already - so it both disagreed with its siblings and could not be retuned through the role a consumer is told to use. ACTION: none unless you want the old corner, in which case set --ds-radius-panel: 8px - which moves EVERY panel together, and is the only lever there is. (Corrected 2026-08-11: this note used to offer --ds-select-panel-radius: 8px for restoring just this panel. No such token exists - the dropdown resolves --ds-radius-panel directly - so setting it does nothing. ds-autocomplete does carry a per-panel --ds-autocomplete-panel-radius; the two dropdowns do not.) CHECK: a screen where a dropdown opens beside a popover or a date picker - that is where the 4px difference was visible and is now gone.",
24
24
  "searchHints": [
25
25
  "--radius-md",
26
26
  "dropdown-panel",
@@ -118,6 +118,32 @@
118
118
  "tabChanged",
119
119
  "queryParamMap"
120
120
  ]
121
+ },
122
+ {
123
+ "id": "exported-class-members-grew",
124
+ "kind": "behavior",
125
+ "old": "extends TableComponent",
126
+ "new": null,
127
+ "note": "This release's single class-member-collision entry, the counterpart of 0.8.0's: it covers EVERY exported class whose member surface changed, so a consumer who EXTENDS a DS component resolves them in one pass. Subclassing a DS component is unsupported (design-system.md), but where it happens the names collide and the build stops: TS4114 demands `override`, TS2415 fires on a redeclared private, TS2416 on a differing signature. This is not hypothetical - migrating to 0.8.0, one consumer's ids-data-table (which extends TableComponent) failed on exactly three of them. WHAT GAINED MEMBERS: (1) TableComponent, by far the largest - lazy, lazyLoad, showLabel, showPageSize, filterMode, columnFilterOptions, sortAnnouncement, rangeAnnouncement and exportFailed as inputs/outputs, plus protected filterModeResolved, headerFilters, headerFilterByKey, headerFilterFor(), headerFilterContext(), statusMessage, sortMessage, rangeMessage, virtualCount, rowSlots, exportStatus, resolvedColumnWidth(), onResizeKey() and onHeaderEnter(). Note isStriped() now takes an ABSOLUTE row index rather than a window-relative one, so a subclass that overrode it computes the wrong row. (2) Both CVA bases (DsControlValueAccessor, DsBooleanControlValueAccessor) gained the `hidden` input and a `focus()` method - inherited by every field control, so a subclass with its own focus() needs `override`. (3) InputComponent and TextareaComponent gained readonlyBinding, isReadOnly, minLength, pattern and patternAttribute; SelectComponent gained readonlyBinding and isReadOnly. (4) ModalComponent and ModalCardComponent each gained `subtitle` and `dividers`. (5) AutocompleteComponent gained maxVisibleChips, showChevron, clear(), visibleTags and overflowCount. (6) BreadcrumbsComponent gained maxItems and allItems; MenuItemComponent gained `quiet`; AppLayoutComponent gained scrollReset; AuthLayoutComponent gained `landmark`; TabsComponent gained urlParam and urlParams; LayoutScrollService gained configureReset(). (7) NEW exported symbols that can shadow a local name: FieldGroupComponent, DS_FIELD_GROUP, HeaderFilterDirective and HeaderFilterContext. WHAT WAS REMOVED: TableComponent's private `distinctValuesOf()` is gone, replaced by `optionsFor()`, which prefers the new `columnFilterOptions` input and falls back to the rows in hand — a subclass that called or redeclared the old name loses it silently at the call site and noisily at the declaration. ACTION: rename the subclass's own member, or add `override` where the base's semantics genuinely match - and re-read isStriped() if you overrode it. Consumers who only use the <ds-...> elements in templates need no change.",
128
+ "searchHints": [
129
+ "extends TableComponent",
130
+ "extends InputComponent",
131
+ "extends TextareaComponent",
132
+ "extends SelectComponent",
133
+ "extends ModalComponent",
134
+ "extends AutocompleteComponent",
135
+ "extends BreadcrumbsComponent",
136
+ "extends AppLayoutComponent",
137
+ "extends AuthLayoutComponent",
138
+ "extends TabsComponent",
139
+ "extends DsControlValueAccessor",
140
+ "extends DsBooleanControlValueAccessor",
141
+ "extends ",
142
+ "override readonly",
143
+ "isStriped",
144
+ "TS4114",
145
+ "distinctValuesOf"
146
+ ]
121
147
  }
122
148
  ],
123
149
  "informational": [
@@ -126,7 +152,6 @@
126
152
  "SIGNAL FORMS WORK — no adapter, no wrapper, no DS import. Put [formField] from @angular/forms/signals on any DS control and the form owns the value, validation, touched and disabled state. This was ALWAYS nearly true and nobody knew: FormValueControl requires exactly one member, a `value` model(), and every DS control already had it. Measured across all fifteen controls - thirteen bound with no library change at all. Additive, NO ACTION. WHAT CHANGED HERE, and it is why the other four rules now work too: min/max/maxLength on ds-input, ds-textarea and ds-number-stepper accept undefined on the WRITE side (the binder sends it for an unset bound; the read type is untouched); `readonly` joins ds-input, ds-textarea and ds-select as the contract spelling of the existing readOnly, because signal forms binds by NAME and a readonly() rule was reaching nothing; `minLength` and `pattern` are new native attributes on ds-input and ds-textarea; and `hidden` is declared on both control-value-accessor bases, so a hidden() rule now removes the control on all thirteen that carry one. focus() is implemented too, so focusBoundControl() - the usual way to reach the first invalid field after a failed submit - lands on the element that holds the value rather than on the host, which is a <ds-*> element and not focusable, so focus previously went nowhere. It resolves per control: the stepper's number box rather than its minus button, the tabbable radio rather than the first in the DOM, a picker's trigger rather than an input inside its closed panel. NOT implemented: dirty, pending and disabledReasons - the form still tracks them, and they are blocked on a visual decision rather than wiring. ERROR TEXT still comes from your validator: required(path.email, { message: '...' }) or a provideDsConfig field.errorMessages mapping, otherwise the field goes red with no words and only a dev warning explains why. Docs: the Practice > Signal Forms page, with a live form and the measured contract table.",
127
153
  "ds-modal / ds-modal-card gained [dividers] (default true = today's rendering). Additive, NO ACTION - but DELETE-LIST MATERIAL if you set --ds-modal-divider: transparent. Two consumer apps did exactly that, and both were then left with header and actions padding sized to clear a rule that was no longer drawn, stacking into a 35px gap where 16px was wanted; one needed !important plus a stylelint-disable to win it back. [dividers]=\"false\" drops the rules AND the padding in one move, because those are one design decision. If you kept a deliberate --ds-modal-divider colour, nothing changes. If you set it transparent, replace it with [dividers]=\"false\" and delete whatever padding overrides you wrote afterwards - and note --ds-modal-body-pad-y now falls to 0 in that mode, so set it explicitly if you want a value in both.",
128
154
  "ds-modal / ds-modal-card gained a [title-badge] content slot and a subtitle input, so a dialog header can carry a status chip and a second line without abandoning the component. Additive, NO ACTION - both are absent by default and the header renders exactly as before. WORTH A LOOK IF YOU HAND-ROLLED A DIALOG: a consumer audit found two screens that dropped ds-modal purely because the header could not hold `title + ds-badge` over a `carrier - type` line, and re-implemented the scrim, the body scroll lock, backdrop-click and Escape by hand - losing the focus trap, focus restore, the enter/leave animation and, in one case, the footer, which put a destructive action next to the close button. The shape matches ds-page-header: [title-badge] projects beside the title, subtitle is a plain string under it. The accessible name is still the title string - projected markup never enters aria-labelledby. Retune with --ds-modal-subtitle-text-color and --ds-modal-subtitle-font-size.",
129
- "HUMAN GUIDE: migrations/unreleased/README.md walks this release in order — where to look for each change, the one call that needs judgement per table (sortMode/filterMode), and a section this project had never written before: WHAT YOU CAN NOW DELETE. Two dogfooding audits found that most consumer workarounds were written against hooks that already existed, because nothing ever told them a thing had been tokenised. Read section 3 even if the upgrade itself is clean.",
130
155
  "NEW COMPONENT ds-field-group: several controls in one bordered box (select + input, input + button, search + date-picker). Additive, NO ACTION. If you hand-rolled a glued row by stripping borders off two controls and wrapping them, this replaces it - wrap them in <ds-field-group> and mark the stretching one with grow. Six controls can be segments: ds-input, ds-select, ds-search, ds-autocomplete, ds-date-picker, ds-button. ds-number-stepper and ds-multi-select are excluded by design. Grouped controls must not be given a label or hint - the message row would break the glued line and is suppressed.",
131
156
  "ds-table gained [lazy] + (lazyLoad) for fetching rows as they scroll into view. Additive and opt-in, NO ACTION. If you paged a long list yourself to keep it responsive, this is the alternative: set lazy with virtualScroll and total, make data a SPARSE array total long, and write each fetched row at its ABSOLUTE index - gaps inside the window render skeleton rows. Note sortMode must not be \"client\" (it would sort only the rows that happen to have arrived); the new server default is already right.",
132
157
  "--ds-field-height now reaches ds-autocomplete, ds-multi-select, ds-color-picker, ds-number-stepper, ds-split-button and the ds-modal confirm input. All six spelled their height as the raw --hit-* value, so the token the name advertises did nothing for them; they read the field scale now. Pixel-identical at every size EXCEPT ds-number-stepper at size=\"lg\" (its own actionable entry above). NO ACTION unless you had already worked around the gap by pinning height on one of these - that pin can go.",
@@ -152,6 +177,28 @@
152
177
  "ds-table sortValue string comparison now uses sensitivity: \"base\" alongside numeric: true, so mixed-case and accented values sort together. No action; if you relied on case-sensitive ordering, pass your own sortValue returning a normalized key.",
153
178
  "ds-date-picker keeps its trigger indicator while the panel is open (an \"open\" class alongside the focus rules). Visual only, NO ACTION. If you styled .trigger:focus-within yourself to work around the trigger going dark, you can drop it.",
154
179
  "ds-autocomplete in single mode collapses its filter input once a value is chosen and the panel is closed, so the field reads as a picker instead of a text box. Visual only, NO ACTION. Clicking the field still opens the panel and expands the input, and typing still filters. If you set --ds-autocomplete-input-minw to work around the empty box, you can drop it.",
155
- "ds-date-picker: clicking the calendar glyph no longer moves focus into the day grid. It now behaves like a click on the field - with allowInput (the default) the caret stays in the field, and a read-only field still focuses the grid. No action; ArrowDown on the field enters the grid as before. If you scripted tests that assumed a glyph click lands focus on a day button, they need updating."
180
+ "ds-date-picker: clicking the calendar glyph no longer moves focus into the day grid. It now behaves like a click on the field - with allowInput (the default) the caret stays in the field, and a read-only field still focuses the grid. No action; ArrowDown on the field enters the grid as before. If you scripted tests that assumed a glyph click lands focus on a day button, they need updating.",
181
+ "WHAT YOU CAN NOW DELETE - the half a release note usually leaves out. Two dogfooding audits (mm-ecm 2026-08-06, mm-broker 2026-08-07) read consumer stylesheets as a record of what this library made them write, and both found the same thing: most of the workarounds were written against hooks that ALREADY existed, because a release note says what broke and never says what became unnecessary. Each line below is SEARCH-FOR -> WHY IT CAN GO. None of it is required: skipping it leaves working code that is merely redundant. How to sweep for the rest: grep your styles for ::ng-deep, !important, and any selector naming a DS internal class (.button, .trigger, .option, .modal) - each hit is either an entry below or a genuine gap worth reporting.",
182
+ "DELETE-LIST: if you have `.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\"]`",
183
+ "DELETE-LIST: if you have `--radius-sm: 0` to square a checkbox -> `--ds-checkbox-radius`",
184
+ "DELETE-LIST: if you have `.title.title { font-size }` inside a modal -> `--ds-modal-title-font-size`",
185
+ "DELETE-LIST: if you have Pagination label type overrides -> `--ds-pagination-label-*`",
186
+ "DELETE-LIST: if you have `.size { display: none }` on a pager -> `[showPageSize]=\"false\"` — and it is now forwarded through `ds-table` too",
187
+ "DELETE-LIST: if you have `.actions:empty { display: none }` on a modal -> The library already ships it",
188
+ "DELETE-LIST: if you have `--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",
189
+ "DELETE-LIST: if you have A defensive hover rule on the selected dropdown row -> The `:not(.is-selected)` branch already handles it",
190
+ "DELETE-LIST: if you have `ds-menu-divider { padding: 0 }` -> `--ds-menu-divider-spacing`, which already defaults to 0",
191
+ "DELETE-LIST: if you have 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",
192
+ "DELETE-LIST: if you have A global rule squaring `.ds-overlay-pane` -> Radius and elevation roles now travel onto portaled panes when the host overrides them",
193
+ "DELETE-LIST: if you have Absolutely positioning a search glyph over an autocomplete, or hiding `.autocomplete-chevron` -> `dsAutocompletePrefix` and `[showChevron]=\"false\"`",
194
+ "DELETE-LIST: if you have Querying the autocomplete's inner `<input>` and dispatching a synthetic `input` event to clear it -> `clear()`",
195
+ "DELETE-LIST: if you have A hand-built KPI tile whose value is a badge -> `ds-stat` takes a projected `[dsStatValue]`",
196
+ "DELETE-LIST: if you have 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",
197
+ "DELETE-LIST: if you have 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",
198
+ "DELETE-LIST: if you have `[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",
199
+ "DELETE-LIST: if you have `white-space: normal` forced onto a badge in a table cell -> `--ds-badge-white-space`",
200
+ "DELETE-LIST: if you have `::ng-deep .card { height: 100% }` for equal-height cards -> The card's box fills a stretched host on its own",
201
+ "DELETE-LIST: if you have `!important` on `ds-table` cell padding under `density=\"compact\"` -> Compact no longer out-specifies the padding hooks",
202
+ "DELETE-LIST: if you have A wrapper around `ds-table` for sort/range announcements, keyboard column resize, or a header filter the checklist cannot express -> All three ship: the live region, the `role=\"separator\"` handle, and `dsHeaderFilter`"
156
203
  ]
157
204
  }
@@ -0,0 +1,10 @@
1
+ {
2
+ "version": "0.9.1",
3
+ "items": [],
4
+ "informational": [
5
+ "Nothing in this release changes the package's runtime. Its entire src/ diff is JSDoc, which feeds the generated token and component reference; every component behaves exactly as it did on 0.9.0.",
6
+ "THREE documented behaviours were guessable wrong, so check these if you use them - the code always worked this way, only the reference was silent. (1) ds-time-columns `value` is always HH:mm in 24h and `format` changes only the DISPLAY, so a picker showing 12h still emits 24h - code that parsed the emitted value as 12h was wrong. (2) ds-time-columns `minTime`/`maxTime` DISABLE the out-of-range rows rather than removing them, so the columns keep their height as a bound moves - a layout that assumed the list shortens was wrong. (3) ds-calendar-day `tabIndex` is a roving tabindex owned by the grid (exactly one cell at 0, the rest at -1), not a tab position to set per day - setting it per cell fights the grid's keyboard model.",
7
+ "41 public tokens and props gained descriptions in the reference: 10 --ds-* tokens (the whole --ds-password-rules-* set, --ds-multi-select-panel-bg-color and --ds-menu-item-radius among them) and 31 inputs and outputs across ds-calendar-day, ds-time-columns, ds-field-message, ds-divider, ds-sidenav-footer and the three layout primitives. Names, types and defaults are unchanged.",
8
+ "Every version's migration manifest now carries its DELETE-LIST entries, so an upgrade tool can act on what a release made UNNECESSARY and not only on what it broke. 0.9.0 has 21 of them. They existed before only in a prose file no tooling read, and that file has been retired."
9
+ ]
10
+ }
@@ -139,6 +139,14 @@ resolution: rename the subclass's own member, or add `override` where the base's
139
139
  match. Keep the feature bullets themselves in `informational` — the item is the collision, not the
140
140
  feature.
141
141
 
142
+ **Do not compile that list by eye — run `npm run class-surface`.** It diffs the exported member
143
+ surface between the last tag and HEAD and prints it per class. Twice now the list was assembled by
144
+ reading the diff and twice it was wrong in a way a consumer found first: 0.8.0 named the public
145
+ additions but not the private `saveLayout` that broke their build, and 0.9.0 shipped with no entry
146
+ while sixteen classes had grown. Two things the tool cannot see, so check them by hand: a member
147
+ whose SIGNATURE changed (same name, so it compiles and then misbehaves — `TableComponent.isStriped()`
148
+ went window-relative to absolute) and a member that moved to a base class.
149
+
142
150
  ## Per-entry checklist
143
151
 
144
152
  - [ ] `id` is a stable, unique kebab slug.
@@ -21,24 +21,36 @@ One file per released version — `migrations/<version>.json` — mirroring that
21
21
 
22
22
  **Why:** the auto-update plugin reads the prose changelog with an LLM planner — correct, but
23
23
  re-derived on every consumer run. A shipped manifest makes the plan deterministic: the planner
24
- validates and prefers it, falling back to prose only when a version has no manifest. Every published
25
- version `0.1.0`–`0.5.0` ships a manifest (older ones authored retroactively); new versions add theirs
26
- at release time.
24
+ validates and prefers it, falling back to prose only when a version has no manifest. **Every
25
+ published version has one**, so the fallback should never fire — the earliest were authored
26
+ retroactively, and `0.6.1`, `0.6.2` and `0.9.1` were backfilled on 2026-08-11 after an audit found
27
+ them missing. A patch release is not exempt: 0.6.2 turned out to carry an actionable change (a sheet
28
+ with nothing focusable in it stopped closing on Escape), which is exactly the kind a "just fixes"
29
+ release is assumed not to have.
27
30
 
28
31
  See `AUTHORING.md` for how to write a good entry.
29
32
 
30
- **Prose guides per version.** The `<version>.json` manifest is the terse machine mirror. When a
31
- release needs a longer human walkthrough (a worked before/after, a mental model, edge cases the
32
- `note` can't hold), put it in a sibling folder named for that version: `migrations/<version>/*.md`
33
- (e.g. `migrations/0.5.1/badge-statuses.md`, `migrations/unreleased/README.md`). The folder never matches the `*.json` glob, so tooling
34
- ignores it; the manifest `note` and the CHANGELOG point at the guide by path.
35
-
36
- **A guide should carry the half a manifest cannot: what the consumer can now DELETE.** Two
37
- dogfooding audits (mm-ecm 08-06, mm-broker 08-07) read consumer stylesheets as a record of what
38
- this library made them write, and both found the same thing — most workarounds were written
39
- against hooks that ALREADY existed, because a release note says what broke and never says what
40
- became unnecessary. `unreleased/README.md` §3 is the first guide to carry that list; treat it as
41
- the shape to follow.
33
+ **Do NOT write a prose guide per release — 0.9.0 tried it and it was retired the same day.**
34
+ `migrations/unreleased/README.md` restated the manifest in a form nothing reads: the auto-update
35
+ plugin loads `<version>.json`, and the only content the manifest did not already carry was the
36
+ delete-list. Worse, it went stale inside one release — three late changes never reached it — and a
37
+ stale duplicate misleads where no file would merely be silent. Its content now lives in the two
38
+ places that ARE read: the `DELETE-LIST:` entries in `<version>.json`, and a "What you can now
39
+ DELETE" table in that version's CHANGELOG block.
40
+
41
+ **A sibling folder `migrations/<version>/*.md` is still legal for the rare case a `note` genuinely
42
+ cannot hold** — a worked before/after with code on both sides, like `migrations/0.5.1/badge-statuses.md`.
43
+ The folder never matches the `*.json` glob, so tooling ignores it, and `tools/changelog-release.mjs`
44
+ promotes `migrations/unreleased/` alongside the manifest if one exists. The test before writing one:
45
+ **would a tool or an agent ever open it?** If the answer is "a human might", it belongs in the
46
+ CHANGELOG instead.
47
+
48
+ **What the manifest must carry that a release note usually omits: what the consumer can now DELETE.**
49
+ Two dogfooding audits (mm-ecm 08-06, mm-broker 08-07) read consumer stylesheets as a record of what
50
+ this library made them write, and both found the same thing — most workarounds were written against
51
+ hooks that ALREADY existed, because a release note says what broke and never says what became
52
+ unnecessary. Ship those as `DELETE-LIST: if you have <X> -> <why it can go>` entries in
53
+ `informational`; 0.9.0 has 21 of them and is the shape to follow.
42
54
 
43
55
  **Authoring:** drafted at release time alongside the CHANGELOG entry (the `/changelog` workflow
44
56
  drafts it from the release diff; the release author reviews). The prose changelog stays canonical
package/package.json CHANGED
@@ -1,6 +1,6 @@
1
1
  {
2
2
  "name": "@ids-group-ltd/ids-design-system",
3
- "version": "0.9.0",
3
+ "version": "0.10.0",
4
4
  "description": "IDS Group Angular design system: components, tokens, themes",
5
5
  "license": "MIT",
6
6
  "homepage": "https://ids-ds.proto.ids-group.co.uk/",
@@ -0,0 +1,32 @@
1
+ // `display: contents` by default: the wrapper adds no box, so a trigger that wraps
2
+ // its chips lays out as if it were not there — consumers style against that.
3
+ //
4
+ // Fit mode needs `min-width: 0` with `overflow: hidden`: a flex item refuses to
5
+ // shrink below its content, so without them the frame that renders every chip —
6
+ // the one being measured — would widen the trigger instead of quietly clipping.
7
+ // See chip-overflow.ts for why clipping, not wrapping, makes that safe.
8
+ @mixin chip-row {
9
+ display: contents;
10
+
11
+ &.fit {
12
+ display: flex;
13
+ flex-wrap: nowrap;
14
+ align-items: center;
15
+ min-width: 0;
16
+ overflow: hidden;
17
+
18
+ // The trigger owns chip spacing in both modes; inheriting it keeps one source
19
+ // rather than a copy of each picker's own gap token, which differ.
20
+ gap: inherit;
21
+
22
+ // A chip squeezed by the row must clip, never wrap: a wrapped label makes
23
+ // that one chip two lines tall, which grows the trigger — the exact failure
24
+ // the cap exists to prevent, and what a phone-width trigger did. Measured on
25
+ // a 412px viewport: one chip at 46px beside two at 29px and 31px.
26
+ > * {
27
+ flex: 0 1 auto;
28
+ min-width: 0;
29
+ white-space: nowrap;
30
+ }
31
+ }
32
+ }
@@ -16,6 +16,14 @@
16
16
  --_option-selected-bg-color-hover: var(--ds-option-selected-bg-color-hover, var(--primary-muted));
17
17
  --_option-check-color: var(--ds-option-check-color, var(--primary));
18
18
 
19
+ /* Panel-level for the same reason as the option hooks above: retuning ONE
20
+ picker's corner is not a thing a design system should encourage, but moving
21
+ every panel — modal, popover, date picker — to reach the dropdowns is too
22
+ blunt. This is the middle lever, and `--ds-radius-panel` stays its default so
23
+ an untouched theme is unchanged. 0.9.0's notes promised a per-component
24
+ `--ds-select-panel-radius`, which never existed; this is what they meant. */
25
+ --_dropdown-panel-radius: var(--ds-dropdown-panel-radius, var(--ds-radius-panel));
26
+
19
27
  .dropdown-panel {
20
28
  // Fill the cdk-overlay-pane width (set from trigger.getBoundingClientRect()
21
29
  // in dropdown.component.ts). Without `width: 100%` the panel is a flex
@@ -23,7 +31,7 @@
23
31
  width: 100%;
24
32
  background: var(--surface-overlay);
25
33
  border: var(--border-width-default) solid var(--border-default);
26
- border-radius: var(--ds-radius-panel);
34
+ border-radius: var(--_dropdown-panel-radius);
27
35
  box-shadow: var(--shadow-popover);
28
36
  padding: var(--space-1);
29
37
  max-height: 320px;
@@ -148,7 +156,6 @@
148
156
  &.is-disabled {
149
157
  color: var(--text-disabled);
150
158
  cursor: not-allowed;
151
- opacity: var(--opacity-muted);
152
159
  }
153
160
  }
154
161
  }
@@ -0,0 +1,29 @@
1
+ // `display: flex` on the host is load-bearing: the group stretches the host, but a
2
+ // block host gives the box no height to resolve a percentage against, and the value
3
+ // ends up at the top of the row instead of its centre.
4
+ @mixin field-group-segment($box) {
5
+ width: auto;
6
+ display: flex;
7
+
8
+ .label,
9
+ ds-field-message {
10
+ display: none;
11
+ }
12
+
13
+ #{$box} {
14
+ border: 0;
15
+ border-radius: 0;
16
+ background: transparent;
17
+ flex: 1;
18
+ height: auto;
19
+
20
+ &:hover,
21
+ &:focus,
22
+ &:focus-visible,
23
+ &:focus-within {
24
+ border: 0;
25
+ box-shadow: none;
26
+ outline: 0;
27
+ }
28
+ }
29
+ }
@@ -0,0 +1,38 @@
1
+ // Keyed off `data-field-state` on the host, which each field binds from
2
+ // `resolveFieldMessage`'s `controlState`. The tinted-fill variant of warning and
3
+ // success is parked in docs/todo.md.
4
+ //
5
+ // The colour arguments exist so a component can pass its own `--ds-<name>-*-error`
6
+ // resolver: hardcoding the family token here would silently drop overrides
7
+ // published since 0.7.x.
8
+ @mixin field-state(
9
+ $box,
10
+ $error-border: var(--error),
11
+ $error-bg: var(--error-subtitle),
12
+ $error-focus-shadow: var(--ds-field-focus-shadow-error),
13
+ $warning-border: var(--warning-text),
14
+ $success-border: var(--success)
15
+ ) {
16
+ // `:not(.in-group)` on all three: a segment ties `.in-group` at (0,3,0) and this
17
+ // mixin is included last, so without it the fill repaints one segment mid-row.
18
+ :host([data-field-state='error']:not(.in-group)) #{$box} {
19
+ border-color: #{$error-border};
20
+ background-color: #{$error-bg};
21
+
22
+ &:focus-within,
23
+ &:focus-visible {
24
+ box-shadow: #{$error-focus-shadow};
25
+ }
26
+ }
27
+
28
+ // --warning is yellow-400, 1.47:1 against a white field — invisible as a
29
+ // boundary, where WCAG 1.4.11 asks 3:1. --warning-text (yellow-700) is the
30
+ // first rung of the ramp that clears it, at 4.59:1.
31
+ :host([data-field-state='warning']:not(.in-group)) #{$box} {
32
+ border-color: #{$warning-border};
33
+ }
34
+
35
+ :host([data-field-state='success']:not(.in-group)) #{$box} {
36
+ border-color: #{$success-border};
37
+ }
38
+ }
@@ -15,6 +15,14 @@
15
15
  // Windows High Contrast DROPS box-shadow, so a shadow-only indicator disappears
16
16
  // entirely there. This is the one place that gap can be closed once.
17
17
 
18
+ // Base indicator for anything focusable that styles none itself, so it cannot fall
19
+ // through to the browser default. `:where()` keeps it at ZERO specificity, so every
20
+ // component and app rule still wins.
21
+ :where(:focus-visible) {
22
+ outline: none;
23
+ box-shadow: var(--ds-control-focus-shadow);
24
+ }
25
+
18
26
  :root[data-focus='ring'] {
19
27
  --ds-field-focus-shadow: var(--focus-ring);
20
28
  --ds-field-focus-shadow-error: var(--focus-ring-error);
package/styles/_link.scss CHANGED
@@ -47,6 +47,27 @@
47
47
  flex-shrink: 0;
48
48
  }
49
49
 
50
+ /* ds-button warns `variant="text"` off in favour of this class, and an action
51
+ that is not navigation has to be a <button> — which arrives with UA chrome
52
+ none of the rules above touch (measured: 13.3px inside 14px text, plus padding
53
+ and an outset border). `:where()` keeps the reset at this class's specificity,
54
+ so a consumer's rule still wins on source order.
55
+
56
+ Absences are deliberate and invisible in code: no `font-weight`, so `.quiet` /
57
+ `.standalone` keep deciding it, and no `display`, because inline-block is what
58
+ lays a standalone button out predictably. `appearance` is the reverse — no
59
+ effect in Chrome, needed where native chrome outlives a zeroed border. */
60
+ &:where(button) {
61
+ appearance: none;
62
+ padding: 0;
63
+ border: 0;
64
+ background: none;
65
+ font-family: inherit;
66
+ font-size: inherit;
67
+ line-height: inherit;
68
+ text-align: inherit;
69
+ }
70
+
50
71
  &.quiet {
51
72
  color: var(--text-secondary);
52
73
 
@@ -217,7 +217,8 @@
217
217
  Each token has a real consumer in the codebase; symmetric "unused"
218
218
  numeric stops are deliberately omitted. */
219
219
  --opacity-disabled: 0.5; /* full disabled state on interactive components */
220
- --opacity-muted: 0.6; /* legacy alias — being phased out in favour of --text-* roles */
220
+ --opacity-muted: 0.6; /* legacy alias, no component reads it since the disabled
221
+ states moved onto --text-disabled + --opacity-disabled */
221
222
  --opacity-text-disabled: 0.38; /* disabled text alpha (WCAG-derived) */
222
223
  --opacity-scrim: 0.55; /* modal/drawer backdrop overlay (light theme) */
223
224
  --opacity-state-hover: 0.08; /* hover layer over surface (overlay vs surface swap) */
@@ -302,7 +303,7 @@
302
303
  --hit-min: 32px; /* dense desktop default (alias of --hit-cozy-tier-0) */
303
304
  --hit-cozy: 40px; /* default control height */
304
305
  --hit-comfy: 44px; /* WCAG min for touch */
305
- --hit-touch: 48px; /* mobile-friendly — also used by floating-label fields */
306
+ --hit-touch: 48px; /* mobile-friendly */
306
307
 
307
308
  --icon-2xs: 10px;
308
309
  --icon-xs: 12px;
@@ -436,11 +437,7 @@
436
437
  --field-h-sm: var(--hit-min);
437
438
  --field-h-md: var(--hit-cozy);
438
439
  --field-h-lg: var(--hit-touch);
439
- --field-h-floating: var(--hit-touch);
440
440
  --field-textarea-min: 96px;
441
- --field-floating-label-fs: var(--font-size-2xs);
442
- --field-floating-label-lh: 14px;
443
- --field-floating-label-top: 8px;
444
441
  --field-num-stepper-w: var(--space-8);
445
442
 
446
443
  /* OTP / PIN input — one box per digit. */
@@ -470,6 +467,7 @@
470
467
  --sidenav-pad-brand-b: var(--space-6); /* logo bottom padding */
471
468
  --sidenav-logo-size: var(--hit-sm); /* 28px — square brand mark */
472
469
  --sidenav-collapsed-item: var(--hit-cozy); /* 40px — collapsed nav-item hit area */
470
+ --sidenav-collapsed-glyph: var(--icon-lg); /* 20px — matches the size the item template renders its icon at */
473
471
  --sidenav-section-pad-b: var(--space-1-5); /* nav-section bottom padding */
474
472
  --sidenav-item-rail-width: 3px; /* active-item left rail */
475
473
 
@@ -485,7 +483,6 @@
485
483
 
486
484
  /* Field internals */
487
485
  --field-textarea-rows-min: 60px; /* min-h for inline textarea inside the field wrapper */
488
- --field-floating-pad-t: 18px; /* top padding when --floating, leaves room for label */
489
486
  --field-select-pad-r: var(--space-6); /* select chevron clearance */
490
487
  --field-affix-overlap: var(--border-width-default); /* affix bleed over field border */
491
488
 
@@ -679,7 +676,6 @@
679
676
  --badge-dot-size: 4px;
680
677
  --status-dot-size: 5px;
681
678
  --sidenav-w: 200px;
682
- --field-floating-label-top: 4px;
683
679
  --segmented-btn-h: 20px;
684
680
 
685
681
  /* Ultra also compresses field + table padding (tighter than compact/comfy). */
@@ -688,6 +684,10 @@
688
684
  --table-cell-pad-x: var(--space-2);
689
685
  --table-cell-pad-y: var(--space-1);
690
686
  --table-head-pad-y: var(--space-1);
687
+
688
+ /* One rung, not two: a card's frame reads as padding lost long before its cells
689
+ do, so 24 → 16 while the cells inside it go 16 → 8. */
690
+ --ds-container-pad: var(--space-4);
691
691
  }
692
692
  [data-density="compact"] {
693
693
  --hit-cozy: 32px;
@@ -700,7 +700,6 @@
700
700
  --badge-dot-size: 5px;
701
701
  --status-dot-size: 6px;
702
702
  --sidenav-w: 220px;
703
- --field-floating-label-top: 6px;
704
703
  --segmented-btn-h: 24px;
705
704
  }
706
705
  [data-density="cozy"] {
@@ -0,0 +1,14 @@
1
+ // `position: absolute` needs a positioned ancestor: without one the node resolves
2
+ // against the initial containing block and can grow the consuming page's root
3
+ // scroller into a second scrollbar.
4
+ @mixin visually-hidden {
5
+ position: absolute;
6
+ width: 1px;
7
+ height: 1px;
8
+ padding: 0;
9
+ margin: -1px;
10
+ overflow: hidden;
11
+ clip-path: inset(50%);
12
+ white-space: nowrap;
13
+ border: 0;
14
+ }