@ids-group-ltd/ids-design-system 0.9.1 → 0.10.1
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 +970 -3
- package/components.md +13 -13
- package/fesm2022/ids-group-ltd-ids-design-system.mjs +1473 -910
- package/fesm2022/ids-group-ltd-ids-design-system.mjs.map +1 -1
- package/migrations/0.10.0.json +407 -0
- package/migrations/0.10.1.json +159 -0
- package/migrations/0.6.1.json +9 -0
- package/migrations/0.6.2.json +24 -0
- package/migrations/0.8.0.json +4 -2
- package/migrations/0.9.0.json +27 -1
- package/migrations/0.9.1.json +10 -0
- package/migrations/AUTHORING.md +8 -0
- package/migrations/README.md +6 -3
- package/package.json +1 -1
- package/styles/_chip-row.scss +32 -0
- package/styles/_dropdown-overlay.scss +9 -2
- package/styles/_field-group-segment.scss +29 -0
- package/styles/_field-state.scss +38 -0
- package/styles/_focus.scss +8 -0
- package/styles/_link.scss +21 -0
- package/styles/_tokens.scss +6 -9
- package/styles/_visually-hidden.scss +14 -0
- package/types/ids-group-ltd-ids-design-system.d.ts +593 -479
|
@@ -0,0 +1,159 @@
|
|
|
1
|
+
{
|
|
2
|
+
"version": "0.10.1",
|
|
3
|
+
"items": [
|
|
4
|
+
{
|
|
5
|
+
"id": "opacity-muted-token-removed",
|
|
6
|
+
"kind": "removed-api",
|
|
7
|
+
"old": "--opacity-muted",
|
|
8
|
+
"new": null,
|
|
9
|
+
"note": "The --opacity-muted custom property (0.6) is deleted from the token scale. No component has read it since 0.10.0 moved the disabled states onto --text-disabled + --opacity-disabled, so REMOVING IT CHANGES NOTHING THE LIBRARY RENDERS. Two consumer cases. (1) You SET it - most likely on ds-button or ds-icon-button, the override 0.10.0's DELETE-LIST already warned about: delete the declaration, it was a no-op then and is a no-op now (those two resolve their disabled state from oklch(from accent ...) colours, and --ds-button-label-color-disabled / --ds-icon-button-icon-color-disabled are the real hooks). (2) You READ it in your own CSS, i.e. var(--opacity-muted) appears in a value you wrote: that now resolves to nothing and the declaration is dropped, so pick the token that names the job instead - --opacity-disabled (0.5) where opacity is the ONLY disabled signal, --opacity-text-disabled (0.38) for disabled text - or inline 0.6 if what you actually wanted was de-emphasis rather than a disabled state. Do not re-declare --opacity-muted yourself to keep it alive: 'muted' is a de-emphasis level and disabled is a state, and sharing one number between them is what put this token on the DELETE-LIST in the first place.",
|
|
10
|
+
"searchHints": [
|
|
11
|
+
"--opacity-muted",
|
|
12
|
+
"var(--opacity-muted",
|
|
13
|
+
"opacity-muted"
|
|
14
|
+
]
|
|
15
|
+
},
|
|
16
|
+
{
|
|
17
|
+
"id": "list-item-slots-outside-activator",
|
|
18
|
+
"kind": "behavior",
|
|
19
|
+
"old": "ds-list-item ::ng-deep .activator",
|
|
20
|
+
"new": null,
|
|
21
|
+
"note": "ds-list-item's DOM changed: `[leading]` and `[trailing]` are now siblings of `.activator` rather than children of it, so a row can hold a checkbox or a kebab alongside a row-level action. NO INPUT OR OUTPUT CHANGED -- title, subtitle, clickable, selected, disabled and activated all behave as before, and a plain row looks identical. WHAT MOVED: the row's `display: flex`, its `--ds-list-item-pad-*` padding, its `--ds-list-item-gap`, the hover tint and the selected tint all sit on the HOST now; `.activator` is just the text button and has no padding of its own. ACTION: a `::ng-deep .activator` override that set padding, gap, background or hover now applies to the text only -- move it to `ds-list-item` itself. Also fixed alongside: `selected` set `aria-current` on the inner button, so it was inert whenever `clickable` was false; it is on the host now, which means a non-clickable row marked selected is finally announced as current. TARGET: ds-list-item (the host)",
|
|
22
|
+
"searchHints": [
|
|
23
|
+
"ds-list-item",
|
|
24
|
+
".activator",
|
|
25
|
+
"list-item-pad",
|
|
26
|
+
"list-item-gap",
|
|
27
|
+
"aria-current",
|
|
28
|
+
"leading",
|
|
29
|
+
"trailing",
|
|
30
|
+
"clickable"
|
|
31
|
+
]
|
|
32
|
+
},
|
|
33
|
+
{
|
|
34
|
+
"id": "button-borderless-disabled-label-recipe",
|
|
35
|
+
"kind": "behavior",
|
|
36
|
+
"old": "ds-button[variant=\"ghost\"][disabled], ds-button[variant=\"text\"][disabled], ds-button[variant=\"outline\"][disabled]",
|
|
37
|
+
"new": null,
|
|
38
|
+
"note": "The DEFAULT disabled label colour changed for the three variants whose fill cannot carry the state. Was the shared `oklch(from <accent> 70% 0.035 h)`; is now `color-mix(in srgb, <label> 40%, var(--surface-default))` -- the lightness now moves toward the surface instead of being pinned at 70%. WHY: pinned at 70% the disabled label was two points of OKLCH lightness from the enabled one in the DARK theme (--primary-strong is L 67.9% there), a 1.11:1 gap, so a disabled ghost was indistinguishable from an active one. A fixed lightness cannot serve both themes -- in light disabled is lighter than the accent, in dark the accent is already light so disabled must go darker; only the surface knows that direction. Measured after: light 2.54 -> 3.41:1, dark 1.11 -> 2.91:1. `variant=\"outline\"` is included even though it has a border, because its DISABLED border resolves to only 1.30:1 against the page -- lower than its own enabled border at 1.49:1 -- so the label was carrying the state there too. NO ACTION NEEDED unless you relied on the exact old colour: `--ds-button-label-color-disabled` is the same hook and still wins, so an app that already sets it sees no change. If you matched the old #949EB5 by hand anywhere (a mock, a screenshot test, a hand-written CSS twin of the disabled state), for the default primary it is now #A5B4F8 in light and #3D4979 in dark. The label stays tinted rather than going grey -- chroma rises with the mix (0.036 -> 0.099 in light) -- which was chosen deliberately. LIMITATION: the mix target is --surface-default, a stand-in for the real backdrop, so a borderless button sitting on a tinted ground gets a label mixed against the page colour instead. `variant=\"solid\"` and `variant=\"tonal\"` are NOT affected and keep the shared recipe. TARGET: --ds-button-label-color-disabled (unchanged hook, new default)",
|
|
39
|
+
"searchHints": [
|
|
40
|
+
"ds-button",
|
|
41
|
+
"variant=\"ghost\"",
|
|
42
|
+
"variant=\"text\"",
|
|
43
|
+
"variant=\"outline\"",
|
|
44
|
+
"--ds-button-label-color-disabled",
|
|
45
|
+
"label-color-disabled",
|
|
46
|
+
"#949EB5",
|
|
47
|
+
"disabled",
|
|
48
|
+
"oklch"
|
|
49
|
+
]
|
|
50
|
+
},
|
|
51
|
+
{
|
|
52
|
+
"id": "icon-button-standard-disabled-icon-recipe",
|
|
53
|
+
"kind": "behavior",
|
|
54
|
+
"old": "ds-icon-button[variant=\"standard\"][disabled]",
|
|
55
|
+
"new": null,
|
|
56
|
+
"note": "The DEFAULT disabled glyph colour changed for variant=\"standard\" ONLY -- the one variant with no fill and no border, so the glyph colour is the whole signal. Was the shared `oklch(from <accent> 70% 0.035 h)`; is now `color-mix(in srgb, <icon colour> 40%, var(--surface-default))`. WHY: pinned at L 70% the disabled glyph sat only ten points of OKLCH lightness from the enabled one in the DARK theme (the enabled glyph is --text-secondary at L 80% there), a 1.46:1 gap. Light was already fine at 4.17:1 because the enabled glyph is L 35% there -- this is a dark-theme fix. Measured after: light 4.17 -> 5.19:1, dark 1.46 -> 3.58:1. NO ACTION NEEDED unless you relied on the exact old colour: `--ds-icon-button-icon-color-disabled` is the same hook and still wins. If you matched the old value by hand, for the default it was #969EB5 (light) / #949EB5 (dark) and is now #AEB1B8 (light) / #575D69 (dark). variant=\"filled\", \"tonal\" and \"outlined\" are NOT affected and keep the shared recipe -- filled deliberately so, because its glyph is --c-on (white) and mixing white into a white surface would not move it. TARGET: --ds-icon-button-icon-color-disabled (unchanged hook, new default)",
|
|
57
|
+
"searchHints": [
|
|
58
|
+
"ds-icon-button",
|
|
59
|
+
"variant=\"standard\"",
|
|
60
|
+
"--ds-icon-button-icon-color-disabled",
|
|
61
|
+
"icon-color-disabled",
|
|
62
|
+
"#969EB5",
|
|
63
|
+
"disabled",
|
|
64
|
+
"oklch"
|
|
65
|
+
]
|
|
66
|
+
},
|
|
67
|
+
{
|
|
68
|
+
"id": "fields-success-is-a-string",
|
|
69
|
+
"kind": "behavior",
|
|
70
|
+
"old": "ds-input [success]=\"true\"",
|
|
71
|
+
"new": null,
|
|
72
|
+
"note": "TWO changes in one, and only the first needs edits. (1) BREAKING on `ds-input`: `success` was `input(false, { transform: booleanAttribute })` and is now `input<string>('')`. A `[success]=\"true\"` binding now sets the literal text \"true\" as the message. Replace `[success]=\"true\" hint=\"Available\"` with `success=\"Available\"` -- the text moves out of `hint` and into `success`. A `[success]=\"someBoolean\"` binding must become `[success]=\"someBoolean ? 'Looks good' : ''\"`, since an empty string is now what means \"no success state\". (2) ADDITIVE: the same `success` input now also exists on ds-textarea, ds-select, ds-multi-select, ds-autocomplete, ds-date-picker, ds-time-picker, ds-otp-input and ds-color-picker, which had no success state at all. WHY THE TYPE CHANGED: `error` and `warning` already carried their own text, so `success` was the only state that could not say anything -- it was a flag that recoloured `hint` green, which meant the message had to be smuggled through a different input. It is now the fourth rung of the same ladder: error, errors, warning, success, hint. CONSEQUENCE: a success border with NO message is no longer expressible, exactly as it never was for `warning`. NOT added to ds-checkbox, ds-radio-group, ds-switch or ds-slider -- they have no bordered box, so the state would appear in the message line alone. `invalid` is unchanged and remains the flag partner of `error`. NOTE ON KIND: this is not a value remap even though it looks like one — there is no old value that maps to a new one, because the replacement TEXT did not exist before and has to be authored (usually by moving it out of `hint`).",
|
|
73
|
+
"searchHints": [
|
|
74
|
+
"success",
|
|
75
|
+
"[success]",
|
|
76
|
+
"ds-input",
|
|
77
|
+
"ds-textarea",
|
|
78
|
+
"ds-select",
|
|
79
|
+
"ds-date-picker",
|
|
80
|
+
"data-field-state",
|
|
81
|
+
"field-state",
|
|
82
|
+
"hint"
|
|
83
|
+
]
|
|
84
|
+
},
|
|
85
|
+
{
|
|
86
|
+
"id": "fields-shared-base-class-members",
|
|
87
|
+
"kind": "behavior",
|
|
88
|
+
"old": "class MyField extends TextareaComponent (or any DS field)",
|
|
89
|
+
"new": null,
|
|
90
|
+
"note": "INTERNAL REFACTOR, no public API change -- listed only because it matters to SUBCLASSERS. The seven inputs every field shares (`hint`, `error`, `warning`, `errors`, `invalid`, `touched`, `reserveMessage`) plus the `reserveMessageResolved` helper are now declared once on a new `DsFieldBase` instead of being hand-copied into each of the fourteen fields. Every input keeps its name, type, default and documentation; the generated docs API reference was diffed and lost nothing. `DsControlValueAccessor` and `DsBooleanControlValueAccessor` now extend `DsFieldBase`, and `ds-radio` extends it directly. ACTION only if you SUBCLASS a DS field and declare a member with one of those seven names: it is now an inherited member rather than an own member, so an incompatible re-declaration fails to compile where it may previously have shadowed. Redeclaring with the same shape still works. `success`, `label`, `required` and `optional` were deliberately NOT lifted and remain per-component. SEPARATELY, a genuine new collision: `success` is a NEW member on the eight bordered fields that lacked it (ds-autocomplete, ds-color-picker, ds-date-picker, ds-multi-select, ds-otp-input, ds-select, ds-textarea, ds-time-picker), so a subclass of any of those declaring `success` now fails with TS4114. Beware the report itself here: `npm run class-surface` lists those seven moved names as LOST from fourteen field components, which is an artefact of counting declarations per FILE — they moved UP into DsFieldBase and every field still has them by inheritance. AUTHORING already flags a member that moved to a base class as something the tool cannot see. TARGET: the same class, with hint/error/warning/errors/invalid/touched/reserveMessage inherited from DsFieldBase",
|
|
91
|
+
"searchHints": [
|
|
92
|
+
"extends TextareaComponent",
|
|
93
|
+
"extends InputComponent",
|
|
94
|
+
"DsFieldBase",
|
|
95
|
+
"DsControlValueAccessor",
|
|
96
|
+
"reserveMessage",
|
|
97
|
+
"reserveMessageResolved",
|
|
98
|
+
"touched"
|
|
99
|
+
]
|
|
100
|
+
},
|
|
101
|
+
{
|
|
102
|
+
"id": "fields-invalid-no-longer-recolours-hint",
|
|
103
|
+
"kind": "behavior",
|
|
104
|
+
"old": "[invalid]=\"true\" hint=\"<message>\"",
|
|
105
|
+
"new": null,
|
|
106
|
+
"note": "BREAKING. `invalid` used to promote `hint` to the ERROR state -- a red message rendered through role=\"alert\". It now paints the control and sets aria-invalid only, and `hint` stays a neutral grey hint. ACTION: wherever a field binds `[invalid]` together with `hint` and expected the hint to read as the error, move the text to `error` and drop the `[invalid]` binding -- `error` implies the invalid state. So `[invalid]=\"true\" hint=\"Must be before end date\"` becomes `error=\"Must be before end date\"`. A dynamic form is `[error]=\"showError() ? 'Must be before end date' : ''\"`. WHY: the idiom lost the real hint (with both set, the help text was replaced rather than shown alongside), announced help text as an alert, and made a template unreadable because whether `hint` was a hint or an error depended on another attribute. It was the last input borrowing another's text. NO ACTION when `[invalid]` is used WITHOUT `hint` -- that is still supported and is exactly what the input is for: the error state with the message living elsewhere (a form-level error summary, one message for a whole ds-field-group), plus aria-invalid. `invalid` is not deprecated. TARGET: error=\"<message>\"",
|
|
107
|
+
"searchHints": [
|
|
108
|
+
"[invalid]",
|
|
109
|
+
"invalid",
|
|
110
|
+
"hint=",
|
|
111
|
+
"[hint]",
|
|
112
|
+
"error=",
|
|
113
|
+
"[error]",
|
|
114
|
+
"aria-invalid",
|
|
115
|
+
"role=\"alert\""
|
|
116
|
+
]
|
|
117
|
+
},
|
|
118
|
+
{
|
|
119
|
+
"id": "fields-warning-kind-is-reserved",
|
|
120
|
+
"kind": "behavior",
|
|
121
|
+
"old": "a validator returning { warning: ... }",
|
|
122
|
+
"new": null,
|
|
123
|
+
"note": "The DsFieldError kind `warning` is now RESERVED, exported as DS_FIELD_WARNING_KIND. An error carrying it paints the field's warning state and shows its message, but leaves the control valid: aria-invalid stays off and a submit guard reading validity is not blocked. MOSTLY ADDITIVE -- it gives a form model a way to raise a non-blocking remark, which Angular's AbstractControl has no channel for. ACTION ONLY IF you already have a validator using the key `warning` (reactive/template-driven) or a signal-forms ValidationError with kind 'warning' for a BLOCKING error: it now reads as advisory, so the field stops being invalid and the submit stops being blocked. Rename that key to anything else -- e.g. `warningLimit`, `softLimit` -- and the old behaviour returns. Ranked below the explicit `warning` input, and shown only after interaction like any other validation message. DsFieldError and DsFieldErrorsInput are now exported as well, for writing a typed validator. TARGET: the same, now treated as ADVISORY rather than blocking",
|
|
124
|
+
"searchHints": [
|
|
125
|
+
"warning",
|
|
126
|
+
"DS_FIELD_WARNING_KIND",
|
|
127
|
+
"ValidationErrors",
|
|
128
|
+
"ValidationError",
|
|
129
|
+
"errors",
|
|
130
|
+
"DsFieldError",
|
|
131
|
+
"aria-invalid"
|
|
132
|
+
]
|
|
133
|
+
},
|
|
134
|
+
{
|
|
135
|
+
"id": "segmented-pill-moves-to-an-inner-track",
|
|
136
|
+
"kind": "behavior",
|
|
137
|
+
"old": "ds-segmented",
|
|
138
|
+
"new": null,
|
|
139
|
+
"note": "ds-segmented now stacks a label, the pill and a message row, so the PILL moved off :host onto an inner .track. The pill's own custom properties stayed on :host and inherit down, so a token override (--ds-segmented-*) is unaffected and needs nothing. ACTION only for a ::ng-deep rule that treated the HOST as the pill — a background, a border-radius, a display:grid, a border — which now paints the whole stack instead of the control: retarget it at `ds-segmented .track`. ALSO NEW, and additive: the component provides NG_VALUE_ACCESSOR and resolves its message through resolveFieldMessage, so [(ngModel)], formControlName, signal forms, and the label / hint / error / warning / errors inputs all work as they do on the other fields. Nothing that worked before stops working.",
|
|
140
|
+
"searchHints": [
|
|
141
|
+
"ds-segmented",
|
|
142
|
+
"::ng-deep",
|
|
143
|
+
"segmented",
|
|
144
|
+
".track",
|
|
145
|
+
"--ds-segmented"
|
|
146
|
+
]
|
|
147
|
+
}
|
|
148
|
+
],
|
|
149
|
+
"informational": [
|
|
150
|
+
"ds-table's row-action kebab and column-picker trigger now read --ds-table-icon-btn-color, --ds-table-icon-btn-color-hover and --ds-table-icon-btn-focus-color, each defaulting to the value that was previously hardcoded (--icon-default, --icon-strong, --accent). Purely additive. ACTION only if you recoloured your own row trigger and are now adopting rowActions: set these three instead of repainting --icon-default globally.",
|
|
151
|
+
"ds-modal and ds-modal-card take per-side padding: --ds-modal-header-pad-top/-pad-bottom, --ds-modal-body-pad-top/-pad-bottom and --ds-modal-actions-pad-top/-pad-bottom. Each defaults to its region's existing --ds-modal-<region>-pad-y, which still works and still sets both edges, so this is purely additive and nothing moves unless you set one. ACTION only if you have been reaching past the API to pad a region asymmetrically - a rule on .modal > .header / > .body / > .actions, most likely carrying !important because the component's own padding outranks a descendant selector: that rule can now be a token on the host instead.",
|
|
152
|
+
"ds-date-picker: clearing or replacing `value` from outside now clears the picker's own typing error (typedInvalid / rangeInvalid). NO code change is required, but two workarounds can be REMOVED: (a) tearing a modal body down on `closed` just to get a fresh picker -- which never worked when the modal was reopened inside its 300ms leave animation, since the close is cancelled and `closed` never fires; (b) any manual `[error]` juggling used to mask the stale message. Blur validation is unchanged: a full-but-bad date still errors on blur.",
|
|
153
|
+
"A ds-menu inside a ds-popover now clips its rows to the panel's rounded corners, so a first or last row's fill — a hover tint, or a destructive item's red — no longer paints two square corners through the panel's rounded ones. The cause was a clip of the wrong SHAPE, not a missing one: ds-menu has overflow: hidden, but its :host-context(.popover) block flattened border-radius while leaving overflow in force. The popover now publishes --ds-menu-clip-radius (its own radius less its border) and the menu clips to that, so a brand overriding --ds-popover-radius is followed automatically. Nothing to do; --ds-menu-item-radius still defaults to 0, because the MENU owns the edge corners rather than the row.",
|
|
154
|
+
"Message inputs absorb null and undefined instead of crashing. hint, error, warning and success took a bare string and the resolver called .trim() on whatever arrived, so [error]=\"form.errors?.message\" pushed null in and threw a TypeError during render whenever the expression was empty. All four now transform at the input boundary — trimmed, with null/undefined becoming ''. DELETE-LIST: the `?? ''` you wrapped such a binding in.",
|
|
155
|
+
"A disabled ds-icon-button variant=\"standard\" mixes its glyph toward the surface: color-mix(in srgb, <icon> 40%, var(--surface-default)), replacing the shared fixed-lightness recipe. It is the only variant with neither a fill nor a border, so the glyph carries the whole state, and the old recipe left it 1.46:1 from the enabled icon in dark (light 4.17 -> 5.19:1, dark 1.46 -> 3.58:1). Scoped to standard on purpose: filled's icon is --c-on, and white mixed into a white surface does not move. --ds-icon-button-icon-color-disabled is the same hook and still wins; only the default under it changed.",
|
|
156
|
+
"ds-field-message: the `state` input never picked an icon, though its docblock and the generated API reference both said it did (`state` \"decides colour and icon\"; `icon` \"overrides the glyph the state would pick\"). `icon` is a plain input<IconName|null>(null) with no per-state default. Behaviour is unchanged — only the documentation was wrong. If you left `icon` unset expecting a glyph from the state, pass one explicitly.",
|
|
157
|
+
"SegmentedComponent gained eight members when it joined the form systems (label, disabled, isDisabled, message, invalidResolved, fieldMessage, hintId, uid), so it is the tenth class in this release's class-surface report and the only genuinely new collision surface beyond `success`. A subclass of it declaring any of those names now fails with TS4114."
|
|
158
|
+
]
|
|
159
|
+
}
|
|
@@ -0,0 +1,9 @@
|
|
|
1
|
+
{
|
|
2
|
+
"version": "0.6.1",
|
|
3
|
+
"items": [],
|
|
4
|
+
"informational": [
|
|
5
|
+
"ds-date-picker's panel now closes when ANY ancestor scroll container scrolls, not only the one 0.6.0 watched. Nothing to change: a panel that used to hang over the page while a nested pane scrolled underneath now dismisses itself.",
|
|
6
|
+
"ds-date-picker masked typing works on mobile keyboards. Segment-aware editing was wired to keydown, which soft keyboards (Gboard among them) do not report faithfully; the mobile path now goes through beforeinput. If you shipped a workaround that bypassed the masked field on touch devices, it can go.",
|
|
7
|
+
"ds-date-picker's panel no longer sets aria-modal. The calendar is non-modal - the page stays interactive behind it - so the attribute told screen readers something untrue. No API changed; an assistive-tech test that asserted aria-modal on this panel needs updating."
|
|
8
|
+
]
|
|
9
|
+
}
|
|
@@ -0,0 +1,24 @@
|
|
|
1
|
+
{
|
|
2
|
+
"version": "0.6.2",
|
|
3
|
+
"items": [
|
|
4
|
+
{
|
|
5
|
+
"id": "bottom-sheet-escape-scoped-to-panel",
|
|
6
|
+
"kind": "behavior",
|
|
7
|
+
"old": "ds-bottom-sheet",
|
|
8
|
+
"new": null,
|
|
9
|
+
"note": "ds-bottom-sheet's Escape handler moved from the DOCUMENT to its own panel, matching ds-modal and ds-drawer. Why it changed: with stacked overlays a background sheet was swallowing the Escape meant for whatever sat on top. ACTION, and it is a real one: Escape now has to land on the panel, which the focus trap arranges by auto-capturing focus inside it - so a sheet whose body contains NOTHING FOCUSABLE can no longer be closed with Escape. If you have such a sheet (a purely informational one, say), give it a focusable element: the close button in its header is enough. CHECK: open each sheet, press Escape without clicking anything first.",
|
|
10
|
+
"searchHints": [
|
|
11
|
+
"ds-bottom-sheet",
|
|
12
|
+
"bottom-sheet",
|
|
13
|
+
"keydown.escape",
|
|
14
|
+
"document:keydown"
|
|
15
|
+
]
|
|
16
|
+
}
|
|
17
|
+
],
|
|
18
|
+
"informational": [
|
|
19
|
+
"ds-sidenav takes a projected [brand] slot, so a real logo (img, SVG, any markup) can replace or sit beside the string `brand` input. The string input is unchanged and still renders its auto letter-mark. The brand row, previously gated on `brand` being set, now always renders and hides itself with :empty, so an empty rail looks exactly as it did.",
|
|
20
|
+
"DELETE-LIST: if you overlaid or absolutely positioned a logo on top of ds-sidenav's brand row because there was no slot for one -> project it into [brand] instead.",
|
|
21
|
+
"ds-date-picker mobile Backspace/Delete removes ONE digit and crosses separators, instead of wiping the whole segment. Gboard reports those keys with a full-segment composing region, which hit the editor's selection-clear branch and erased e.g. all of MM on one tap. Desktop behaviour was always correct and is unchanged.",
|
|
22
|
+
"ds-bottom-sheet no longer jolts host-app content up and back down as it opens. The entering panel, still translated below the frame, was contributing scrollable overflow to consumer shells that are a containing block for fixed descendants (a `filter`/`transform` ancestor plus overflow:hidden - a centred phone frame is the usual case), and the focus trap's scroll-into-view yanked that shell. The overlay now uses overflow:clip. DELETE-LIST: a scrollTop pin or a scroll-lock hack written against that jolt can go."
|
|
23
|
+
]
|
|
24
|
+
}
|
package/migrations/0.8.0.json
CHANGED
|
@@ -22,7 +22,7 @@
|
|
|
22
22
|
"kind": "behavior",
|
|
23
23
|
"old": "extends InputComponent",
|
|
24
24
|
"new": null,
|
|
25
|
-
"note": "This release's single class-member-collision entry: it covers EVERY exported class whose member surface changed, so a consumer who EXTENDS a DS component can resolve them in one pass. Subclassing a DS component is unsupported (design-system.md § Components), but where it happens the names collide: TS4114 demands `override`, TS2415 fires on a redeclared private member, TS2416 on a differing signature. (1) The 14 message-bearing FIELD classes (Input, Textarea, Select, DatePicker, TimePicker, Autocomplete, Checkbox, Switch, RadioGroup, Radio, OtpInput, Slider, ColorPicker, MultiSelect) REMOVED the protected `messageState` computed, and DatePickerComponent also removed `messageText`; all 14 ADDED the `error`, `warning`, `errors` and `touched` inputs plus protected `message` and `invalidResolved`, with DatePickerComponent also gaining private `localError` and `dateInvalid`. (2) Both CVA base classes (`DsControlValueAccessor`, `DsBooleanControlValueAccessor`) gained a protected `touchedSelf`. (3) `AppLayoutComponent` gained public `railOverlay` and `railId`. (4) `TableComponent` REMOVED the `clientSort` input and gained `sortModeResolved`, `sortableCol()`, `exporting`, `runExport()`, `virtualizing`, `virtualRowHeight`, `virtualWindow`, `windowData` and `isStriped()`, plus the `persistLayout`, `storageKey`, `exportButton`, `exportFilename`, `exportFetcher`, `virtualScroll` and `virtualRowSize` inputs. (5) `ButtonComponent` gained `ariaControls`; `IconButtonComponent` gained `ariaExpanded` and `ariaControls`. (6) `CheckboxComponent`, `SwitchComponent` and `RadioComponent` REMOVED the protected `devMode`. (7) `LayoutScrollService` gained `scroller`, `scrollTo()`, `configureRestore()`, `consumePendingOffset()` and `contentReady()`. (8) The `close()` method on SelectComponent, AutocompleteComponent, MultiSelectComponent, DatePickerComponent, TimePickerComponent, ColorPickerComponent and PopoverComponent gained an optional `cause` parameter, as did TimePickerComponent's `onEscape()` — an override declared as `close()` still satisfies the base, so this one only bites a subclass that re-declares the parameter list differently. ACTION: rename the subclass's own member, or add `override` where the base's semantics genuinely match; a subclass that overrode `messageState` should move its logic to an `error` / `warning` binding on the element instead, since the message is now resolved centrally. Consumers who only use the <ds-...> elements in templates need no change.",
|
|
25
|
+
"note": "This release's single class-member-collision entry: it covers EVERY exported class whose member surface changed, so a consumer who EXTENDS a DS component can resolve them in one pass. Subclassing a DS component is unsupported (design-system.md § Components), but where it happens the names collide: TS4114 demands `override`, TS2415 fires on a redeclared private member, TS2416 on a differing signature. (1) The 14 message-bearing FIELD classes (Input, Textarea, Select, DatePicker, TimePicker, Autocomplete, Checkbox, Switch, RadioGroup, Radio, OtpInput, Slider, ColorPicker, MultiSelect) REMOVED the protected `messageState` computed, and DatePickerComponent also removed `messageText`; all 14 ADDED the `error`, `warning`, `errors` and `touched` inputs plus protected `message` and `invalidResolved`, with DatePickerComponent also gaining private `localError` and `dateInvalid`. (2) Both CVA base classes (`DsControlValueAccessor`, `DsBooleanControlValueAccessor`) gained a protected `touchedSelf`. (3) `AppLayoutComponent` gained public `railOverlay` and `railId`. (4) `TableComponent` REMOVED the `clientSort` input and gained `sortModeResolved`, `sortableCol()`, `exporting`, `runExport()`, `virtualizing`, `virtualRowHeight`, `virtualWindow`, `windowData` and `isStriped()`, plus the `persistLayout`, `storageKey`, `exportButton`, `exportFilename`, `exportFetcher`, `virtualScroll` and `virtualRowSize` inputs, and the PRIVATE methods `saveLayout()` and `restoreLayout()` - a private collides too (TS2415), and `saveLayout` is the one that actually bit a consumer whose own table declared the same name. (5) `ButtonComponent` gained `ariaControls`; `IconButtonComponent` gained `ariaExpanded` and `ariaControls`. (6) `CheckboxComponent`, `SwitchComponent` and `RadioComponent` REMOVED the protected `devMode`. (7) `LayoutScrollService` gained `scroller`, `scrollTo()`, `configureRestore()`, `consumePendingOffset()` and `contentReady()`. (8) The `close()` method on SelectComponent, AutocompleteComponent, MultiSelectComponent, DatePickerComponent, TimePickerComponent, ColorPickerComponent and PopoverComponent gained an optional `cause` parameter, as did TimePickerComponent's `onEscape()` — an override declared as `close()` still satisfies the base, so this one only bites a subclass that re-declares the parameter list differently. ACTION: rename the subclass's own member, or add `override` where the base's semantics genuinely match; a subclass that overrode `messageState` should move its logic to an `error` / `warning` binding on the element instead, since the message is now resolved centrally. Consumers who only use the <ds-...> elements in templates need no change.",
|
|
26
26
|
"searchHints": [
|
|
27
27
|
"extends InputComponent",
|
|
28
28
|
"extends SelectComponent",
|
|
@@ -36,7 +36,9 @@
|
|
|
36
36
|
"extends DsControlValueAccessor",
|
|
37
37
|
"extends ",
|
|
38
38
|
"messageState",
|
|
39
|
-
"override readonly"
|
|
39
|
+
"override readonly",
|
|
40
|
+
"saveLayout",
|
|
41
|
+
"TS4114"
|
|
40
42
|
]
|
|
41
43
|
},
|
|
42
44
|
{
|
package/migrations/0.9.0.json
CHANGED
|
@@ -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
|
|
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": [
|
|
@@ -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
|
+
}
|
package/migrations/AUTHORING.md
CHANGED
|
@@ -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.
|
package/migrations/README.md
CHANGED
|
@@ -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
|
|
25
|
-
version
|
|
26
|
-
|
|
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
|
@@ -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(--
|
|
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
|
+
}
|
package/styles/_focus.scss
CHANGED
|
@@ -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
|
|
package/styles/_tokens.scss
CHANGED
|
@@ -217,7 +217,6 @@
|
|
|
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 */
|
|
221
220
|
--opacity-text-disabled: 0.38; /* disabled text alpha (WCAG-derived) */
|
|
222
221
|
--opacity-scrim: 0.55; /* modal/drawer backdrop overlay (light theme) */
|
|
223
222
|
--opacity-state-hover: 0.08; /* hover layer over surface (overlay vs surface swap) */
|
|
@@ -302,7 +301,7 @@
|
|
|
302
301
|
--hit-min: 32px; /* dense desktop default (alias of --hit-cozy-tier-0) */
|
|
303
302
|
--hit-cozy: 40px; /* default control height */
|
|
304
303
|
--hit-comfy: 44px; /* WCAG min for touch */
|
|
305
|
-
--hit-touch: 48px; /* mobile-friendly
|
|
304
|
+
--hit-touch: 48px; /* mobile-friendly */
|
|
306
305
|
|
|
307
306
|
--icon-2xs: 10px;
|
|
308
307
|
--icon-xs: 12px;
|
|
@@ -436,11 +435,7 @@
|
|
|
436
435
|
--field-h-sm: var(--hit-min);
|
|
437
436
|
--field-h-md: var(--hit-cozy);
|
|
438
437
|
--field-h-lg: var(--hit-touch);
|
|
439
|
-
--field-h-floating: var(--hit-touch);
|
|
440
438
|
--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
439
|
--field-num-stepper-w: var(--space-8);
|
|
445
440
|
|
|
446
441
|
/* OTP / PIN input — one box per digit. */
|
|
@@ -470,6 +465,7 @@
|
|
|
470
465
|
--sidenav-pad-brand-b: var(--space-6); /* logo bottom padding */
|
|
471
466
|
--sidenav-logo-size: var(--hit-sm); /* 28px — square brand mark */
|
|
472
467
|
--sidenav-collapsed-item: var(--hit-cozy); /* 40px — collapsed nav-item hit area */
|
|
468
|
+
--sidenav-collapsed-glyph: var(--icon-lg); /* 20px — matches the size the item template renders its icon at */
|
|
473
469
|
--sidenav-section-pad-b: var(--space-1-5); /* nav-section bottom padding */
|
|
474
470
|
--sidenav-item-rail-width: 3px; /* active-item left rail */
|
|
475
471
|
|
|
@@ -485,7 +481,6 @@
|
|
|
485
481
|
|
|
486
482
|
/* Field internals */
|
|
487
483
|
--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
484
|
--field-select-pad-r: var(--space-6); /* select chevron clearance */
|
|
490
485
|
--field-affix-overlap: var(--border-width-default); /* affix bleed over field border */
|
|
491
486
|
|
|
@@ -679,7 +674,6 @@
|
|
|
679
674
|
--badge-dot-size: 4px;
|
|
680
675
|
--status-dot-size: 5px;
|
|
681
676
|
--sidenav-w: 200px;
|
|
682
|
-
--field-floating-label-top: 4px;
|
|
683
677
|
--segmented-btn-h: 20px;
|
|
684
678
|
|
|
685
679
|
/* Ultra also compresses field + table padding (tighter than compact/comfy). */
|
|
@@ -688,6 +682,10 @@
|
|
|
688
682
|
--table-cell-pad-x: var(--space-2);
|
|
689
683
|
--table-cell-pad-y: var(--space-1);
|
|
690
684
|
--table-head-pad-y: var(--space-1);
|
|
685
|
+
|
|
686
|
+
/* One rung, not two: a card's frame reads as padding lost long before its cells
|
|
687
|
+
do, so 24 → 16 while the cells inside it go 16 → 8. */
|
|
688
|
+
--ds-container-pad: var(--space-4);
|
|
691
689
|
}
|
|
692
690
|
[data-density="compact"] {
|
|
693
691
|
--hit-cozy: 32px;
|
|
@@ -700,7 +698,6 @@
|
|
|
700
698
|
--badge-dot-size: 5px;
|
|
701
699
|
--status-dot-size: 6px;
|
|
702
700
|
--sidenav-w: 220px;
|
|
703
|
-
--field-floating-label-top: 6px;
|
|
704
701
|
--segmented-btn-h: 24px;
|
|
705
702
|
}
|
|
706
703
|
[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
|
+
}
|