@ids-group-ltd/ids-design-system 0.9.1 → 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.
@@ -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,9 +21,12 @@ 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
 
package/package.json CHANGED
@@ -1,6 +1,6 @@
1
1
  {
2
2
  "name": "@ids-group-ltd/ids-design-system",
3
- "version": "0.9.1",
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
+ }