@ids-group-ltd/ids-design-system 0.11.1 → 0.11.2
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 +225 -31
- package/fesm2022/ids-group-ltd-ids-design-system.mjs +1336 -595
- package/fesm2022/ids-group-ltd-ids-design-system.mjs.map +1 -1
- package/migrations/0.11.0.json +0 -45
- package/migrations/0.11.1.json +9 -35
- package/migrations/0.11.2.json +158 -0
- package/migrations/0.2.0.json +17 -5
- package/migrations/0.4.0.json +1 -1
- package/migrations/0.7.1.json +3 -3
- package/migrations/0.9.0.json +2 -2
- package/package.json +1 -1
- package/styles/_dropdown-overlay.scss +29 -10
- package/styles/_tokens.scss +1 -1
- package/themes/README.md +3 -3
- package/types/ids-group-ltd-ids-design-system.d.ts +339 -28
package/CHANGELOG.md
CHANGED
|
@@ -8,6 +8,223 @@ While the package is on `0.x`, minor releases may contain breaking changes.
|
|
|
8
8
|
|
|
9
9
|
## Unreleased
|
|
10
10
|
|
|
11
|
+
## 0.11.2 — 2026-09-01
|
|
12
|
+
|
|
13
|
+
### Added
|
|
14
|
+
|
|
15
|
+
- **`PageUp` and `PageDown`.** Ten rows a press, which is the native `<select>` step and the APG
|
|
16
|
+
listbox example’s — a fixed number rather than a measured screenful, so the jump is the same
|
|
17
|
+
wherever the panel happens to be clipped. No picker had these.
|
|
18
|
+
|
|
19
|
+
- **`clear()` on `ds-select` and `ds-multi-select`.** `ds-autocomplete` has had it; the other two
|
|
20
|
+
offered only the in-trigger button, so an app with its own “reset filters” had to write the empty
|
|
21
|
+
value by hand and guess what empty means for that control. It does NOT move focus, deliberately:
|
|
22
|
+
the caller may be navigating away.
|
|
23
|
+
|
|
24
|
+
|
|
25
|
+
- **Panel header and footer slots.** The panel was a closed box between the filter row and the
|
|
26
|
+
options: "3 of 40 selected", a "clear all" button, a hint or a link under the list had nowhere to
|
|
27
|
+
go. `dsPanelHeaderTemplate` and `dsPanelFooterTemplate` fill a strip above and below, with
|
|
28
|
+
`count`, `total` and `query` in context. Both sit OUTSIDE the `listbox`, so nothing you put there
|
|
29
|
+
is counted as an option or breaks a reader's "N of M" position, and neither scrolls with the list —
|
|
30
|
+
the panel clips and the list is the scroller.
|
|
31
|
+
|
|
32
|
+
- **`dsGroupLabelTemplate`.** A group heading rendered its text and nothing else, so a count, a team
|
|
33
|
+
glyph or a second line was impossible. The heading ELEMENT stays the library's — it keeps the id the
|
|
34
|
+
group's `aria-labelledby` points at — and only its contents are yours.
|
|
35
|
+
|
|
36
|
+
- **The option row's geometry is tokens.** `--ds-option-gap`, `--ds-option-padding`,
|
|
37
|
+
`--ds-option-radius` and `--ds-option-row-gap`, plus `--ds-option-bg-color-active` for the
|
|
38
|
+
hover/keyboard fill. A denser panel meant re-declaring the row before, which is exactly how a second
|
|
39
|
+
copy of the panel ended up inside a component.
|
|
40
|
+
|
|
41
|
+
- **`searchPlaceholder` on `ds-autocomplete`.** Its `placeholder` was doing two jobs — the
|
|
42
|
+
empty-field caption and the hint for typing over a settled value. `ds-multi-select` already
|
|
43
|
+
separated them; now the name means one thing on both. Empty by default, so nothing moves.
|
|
44
|
+
|
|
45
|
+
- **The result count is announced.** A reader typed into the filter and heard nothing: no live region
|
|
46
|
+
existed in any picker. One is created per picker now, outside the listbox and empty at first — a
|
|
47
|
+
region created together with its text is the case screen readers reliably do not announce.
|
|
48
|
+
|
|
49
|
+
- **Type-ahead on `ds-select` and `ds-multi-select`.** Typing "ba" jumps to the first option starting
|
|
50
|
+
with "ba", the way a native `<select>` does, and repeating one letter cycles through the options
|
|
51
|
+
beginning with it. On a closed `ds-select` the jump commits, matching the native control.
|
|
52
|
+
`ds-autocomplete` is deliberately excluded: its trigger IS a text field, so typing there is the
|
|
53
|
+
filter and a jump would fight it.
|
|
54
|
+
|
|
55
|
+
- **`disabledReason` on an option, rendered by `ds-select`.** A disabled row said it could not be
|
|
56
|
+
picked and never why. On `ds-select` the reason reaches the row through `aria-describedby` and is
|
|
57
|
+
visually hidden — the row already looks disabled; the text is for whoever cannot see that. The
|
|
58
|
+
field is on the shared `DsOption`, so `SelectOption`, `MultiSelectOption` and `AutocompleteOption`
|
|
59
|
+
all accept it and it type-checks on all three pickers; `ds-multi-select` and `ds-autocomplete` do
|
|
60
|
+
not yet render it, so a reason set there is carried and not shown.
|
|
61
|
+
|
|
62
|
+
|
|
63
|
+
- **The keyboard cursor keeps its row in view.** On a list longer than the panel the arrows walked the
|
|
64
|
+
cursor out of sight — the reader pressed down and could not see where they were. All three pickers
|
|
65
|
+
scroll the active row into view now, on by default; `scrollActiveIntoView="false"` gives the scroll
|
|
66
|
+
position back to you. It uses `block: 'nearest'`, so a row that is already visible does not move and
|
|
67
|
+
the mouse is never fought.
|
|
68
|
+
|
|
69
|
+
- **`Home` and `End` on every picker.** They existed on `ds-select` alone, while ten other components
|
|
70
|
+
in the library already had them. The index arithmetic all three had written out separately — next,
|
|
71
|
+
previous, first, last, skipping disabled and wrapping — is one shared helper now, so the three
|
|
72
|
+
behave identically. It is internal: nothing new is exported.
|
|
73
|
+
|
|
74
|
+
- **`compareWith` on `ds-autocomplete`.** The component is generic over its value type but compared
|
|
75
|
+
with `===`, which is reference identity: a re-fetch that returned equal data as new objects silently
|
|
76
|
+
dropped the selection. Pass a comparator keyed on what identifies the value —
|
|
77
|
+
`[compareWith]="(a, b) => a?.id === b?.id"`. The default is unchanged, so string and number values
|
|
78
|
+
behave exactly as before. `ds-select` and `ds-multi-select` key on `string` and do not need it.
|
|
79
|
+
|
|
80
|
+
- **`loading`.** While options were being fetched the panel said "No matches", which is a lie the
|
|
81
|
+
consumer had no way to correct. It shows a spinner instead now, and the listbox reports
|
|
82
|
+
`aria-busy`. Spelled `booleanAttribute` to match `ds-button`, `ds-input` and `ds-loading-overlay`.
|
|
83
|
+
|
|
84
|
+
- **`opened` and `closed`.** There was no way to know a panel had opened, so a picker whose options
|
|
85
|
+
are fetched on demand had nowhere to start the request. `closed` is the name eight other components
|
|
86
|
+
already use; `opened` is its missing pair. They fire on the transition, not on every write, so
|
|
87
|
+
closing by Escape emits once rather than twice.
|
|
88
|
+
|
|
89
|
+
- **`filterWith` and `filterChange` — one input for both server-side search and a custom match.**
|
|
90
|
+
The query matcher was hardcoded to a case-insensitive substring of `label`: matching a second field,
|
|
91
|
+
ignoring diacritics or scoring fuzzily was impossible, and so was letting a server do the filtering.
|
|
92
|
+
`filterWith` takes a predicate for the first and the literal `'none'` for the second, where every
|
|
93
|
+
option handed in is rendered and `filterChange` reports what was typed. One input rather than two,
|
|
94
|
+
because they are one decision: who decides what the query matches.
|
|
95
|
+
|
|
96
|
+
- **`name`, `readOnly` and `clearable` on `ds-multi-select` and `ds-autocomplete`.** The last three
|
|
97
|
+
form-contract members that were `ds-select`'s alone. `name` reaches seven other controls in the
|
|
98
|
+
library, so the two pickers were the outliers; `readOnly` takes focus without opening, and carries
|
|
99
|
+
the same `readonly` binding alias `ds-select` has for signal forms; `clearable` uses the same button
|
|
100
|
+
and the same accessible name as `ds-select`'s.
|
|
101
|
+
|
|
102
|
+
|
|
103
|
+
- **`ds-table` row expansion: one-at-a-time, expand-all, and events.** The base feature shipped
|
|
104
|
+
already; these are the three edges it was missing. `expandMode="single"` collapses the open row
|
|
105
|
+
when another expander is clicked, so a detail panel cannot stack up down the page — enforced when
|
|
106
|
+
the user clicks, not on the binding, because `expandedIds` is the host's model to write and
|
|
107
|
+
rewriting it underneath would be the table arguing with its own consumer. `expandAllToggle` puts
|
|
108
|
+
a chevron in the expander column header, page-scoped when paginating exactly as select-all is.
|
|
109
|
+
`(rowExpanded)` and `(rowCollapsed)` name the row as it opens and closes, expand-all included,
|
|
110
|
+
which is where panel content gets lazy-loaded; a collapse the host writes into `expandedIds`
|
|
111
|
+
itself stays silent, and so does an id whose row is no longer in `data()` — an event carries a
|
|
112
|
+
row, and there is none to carry. Opening two rows or more now also reaches the table's live
|
|
113
|
+
region, which a full page of panels appearing from one keypress previously did not.
|
|
114
|
+
|
|
115
|
+
|
|
116
|
+
- **Column resizing works on a touch device, where the drag handle never could.** The handle
|
|
117
|
+
paints its line on `:hover` and `:focus-visible`; a coarse pointer produces neither, so it was
|
|
118
|
+
invisible — while `touch-action: none` still took the horizontal swipe that scrolls the table,
|
|
119
|
+
leaving a dead 8px strip at the right edge of every header. Under
|
|
120
|
+
`(hover: none) and (pointer: coarse)` the handle now stands down and width moves into the column
|
|
121
|
+
panel: each row carries −, + and Fit next to its visibility and order controls, and the panel
|
|
122
|
+
opens as a `ds-bottom-sheet` rather than a popover. The buttons render on desktop as well, where
|
|
123
|
+
the handle remains the primary route. All three routes share one step, so drag, arrow keys and
|
|
124
|
+
buttons move a column by the same amount, and all three clamp at the scroll viewport.
|
|
125
|
+
|
|
126
|
+
|
|
127
|
+
### Changed
|
|
128
|
+
|
|
129
|
+
- **Exported class member surface grew — only matters if you SUBCLASS a DS component.**
|
|
130
|
+
`SelectComponent`, `MultiSelectComponent`, `AutocompleteComponent`, `TableComponent`,
|
|
131
|
+
`LoadingOverlayComponent` and `ToastRegionComponent` all gained members for the inputs and outputs
|
|
132
|
+
above, and `DsPanelHeaderTemplateDirective`,
|
|
133
|
+
`DsPanelFooterTemplateDirective` and `DsGroupLabelTemplateDirective` are new classes.
|
|
134
|
+
Subclassing a DS component is unsupported but consumers do it, and a
|
|
135
|
+
member of yours that shares a name with one of ours stops the build. Rename yours, or add `override`
|
|
136
|
+
if you meant to replace ours — the compiler enumerates every collision, so building after the
|
|
137
|
+
upgrade is the whole check.
|
|
138
|
+
|
|
139
|
+
- **BREAKING for code that CONSTRUCTS a `ToastEntry`: `durationMs` is now a required
|
|
140
|
+
`readonly number`.** The field did not exist on the type before, so it arrives required rather
|
|
141
|
+
than widened: an object literal typed as `ToastEntry` — a test double, a hand-rolled region, a
|
|
142
|
+
store that holds toasts — stops compiling until it carries one. The entry has to know its own
|
|
143
|
+
duration now that the countdown belongs to the region rather than the service.
|
|
144
|
+
`ToastOptions.durationMs` is untouched — still optional, still `5000` by default, still `0` for a
|
|
145
|
+
loading toast — so a caller of `ToastService` writes nothing new.
|
|
146
|
+
|
|
147
|
+
- **BREAKING visually where a stack of toasts is part of the page: the newest toast enters at the
|
|
148
|
+
top of a top-anchored region.** Every toast was appended, so in a region resolving to a top
|
|
149
|
+
position — the default — the newest one landed at the BOTTOM of the stack, furthest from the
|
|
150
|
+
corner the stack grows out of, and the thing that had just happened was the last one you read. A
|
|
151
|
+
top position prepends now; a bottom position still appends. Either way the newest toast is the one
|
|
152
|
+
nearest the screen edge the region is anchored to.
|
|
153
|
+
|
|
154
|
+
- **`ds-select`'s option list caps 40px shorter.** The list's `max-height` was declared in
|
|
155
|
+
`ds-multi-select`'s own stylesheet; it sits in the shared panel partial now, so it reaches
|
|
156
|
+
`ds-select` and `ds-autocomplete` too. `ds-select`'s list was previously bounded only by the panel
|
|
157
|
+
cap `--ds-dropdown-panel-maxh` (320px) and now stops at `--picker-maxh` (280px) — roughly one
|
|
158
|
+
option row — which is the height the other two panels already used. `ds-autocomplete` had pinned
|
|
159
|
+
its panel to that value itself and does not move. Set `--picker-maxh` to take the height back, on
|
|
160
|
+
the panel where only that select should change or globally where all three should follow; the
|
|
161
|
+
panel cap is unchanged and is simply no longer what decides where a `ds-select` list stops.
|
|
162
|
+
|
|
163
|
+
- **`skeleton-mode` is gone from the inner `<table>` element of `ds-table` — only matters if you
|
|
164
|
+
reach in with `::ng-deep`.** The class was bound on that element, not the host, and nothing in the
|
|
165
|
+
library ever painted it, so a rule keyed on it was the only thing giving it meaning. If you have
|
|
166
|
+
one, key it off a class of your own on the host instead; if you do not, nothing about the rendered
|
|
167
|
+
table changes.
|
|
168
|
+
|
|
169
|
+
### Fixed
|
|
170
|
+
- **Dev-mode warnings no longer ship to production bundles.** They were guarded by
|
|
171
|
+
`isDevMode()`, which is a function CALL — a bundler cannot prove the branch dead, so all fourteen
|
|
172
|
+
warning sites and their message closures reached production builds. Each site is now guarded inline
|
|
173
|
+
with `typeof ngDevMode === 'undefined' || ngDevMode`, which `@angular/build` folds away whenever
|
|
174
|
+
script optimization is on, closures included. **Measured: 1 590 B gzip off an app using most of the
|
|
175
|
+
library, 827 B of it off a single `<ds-button>`.** Nothing changes for you — no API, no behaviour,
|
|
176
|
+
and the warnings still fire in development builds exactly as before.
|
|
177
|
+
|
|
178
|
+
|
|
179
|
+
- **A loading scrim stopped the pointer and let the keyboard walk straight under it.**
|
|
180
|
+
`ds-loading-overlay` paints an absolutely positioned scrim over its content, which intercepts
|
|
181
|
+
every pointer event — so a control behind it could not be clicked, and looked unavailable. Nothing
|
|
182
|
+
stopped focus: Tab reached the same control, Enter activated it, and `ds-table` with
|
|
183
|
+
`rowInteractive` would emit `(rowClicked)` for a row whose data the host was in the middle of
|
|
184
|
+
replacing. Neither `onRowClick` nor `onRowKey` consulted the loading state, and a row's
|
|
185
|
+
`tabindex` never did either. The overlay now marks the content it covers `inert` while loading,
|
|
186
|
+
which is the one mechanism that stops pointer and keyboard together and takes the covered controls
|
|
187
|
+
out of the accessibility tree; `aria-busy` stays on the host, so a reader is still told why.
|
|
188
|
+
`inertContent="false"` turns it off for a scrim that covers only PART of its content, and the
|
|
189
|
+
consumer then marks the covered subtree itself — `ds-table` does this, because its scrim starts
|
|
190
|
+
below the header and re-sorting during a refresh is exactly what puts the scrim up.
|
|
191
|
+
|
|
192
|
+
- **A toast queued behind `maxVisible` expired while it was still waiting.** The auto-dismiss
|
|
193
|
+
countdown started when `ToastService` was called, not when the toast reached the screen, so a
|
|
194
|
+
burst past the cap retired toasts that had never been visible — the more you fired at once, the
|
|
195
|
+
fewer were read, and the ones lost were the ones at the back. The countdown starts when the region
|
|
196
|
+
shows the toast now, promotion out of the queue included, so a queued toast gets its full duration
|
|
197
|
+
on screen. One gap remains: `ToastService.promise()` runs its own timers, so a promise toast held
|
|
198
|
+
behind the cap can still be removed before it is shown.
|
|
199
|
+
|
|
200
|
+
- **Dismissing a toast that was still queued promoted a different one instead of removing it.** The
|
|
201
|
+
id belonged to an entry that had not become visible yet, so the entry stayed in the queue and
|
|
202
|
+
another toast was pulled forward: the one you dismissed still appeared later, and one you had not
|
|
203
|
+
touched was hurried on screen ahead of its turn. A queued id is spliced out of the queue now and
|
|
204
|
+
nothing is promoted in its place.
|
|
205
|
+
|
|
206
|
+
- **A column resize handle announced no position and no limits.** The handle is a `role="separator"`,
|
|
207
|
+
which a screen reader presents as a slider, but an auto-sized column carried no `aria-valuenow` at
|
|
208
|
+
all — the user was handed a control with no current value and no way to hear how far it could go in
|
|
209
|
+
either direction. While the handle holds focus it now carries a measured `aria-valuenow` in px,
|
|
210
|
+
`aria-valuemin` of `48` and an `aria-valuemax` of the scroll viewport's width, which is the same
|
|
211
|
+
ceiling the drag, the arrow keys and the column-panel buttons clamp at. All three are present only
|
|
212
|
+
while the handle is focused.
|
|
213
|
+
|
|
214
|
+
- **A table's loading scrim slid off the table as it scrolled sideways.** `ds-loading-overlay` sat
|
|
215
|
+
inside the scroll container, and the scrim is `position: absolute; inset: 0` — so it was sized to a
|
|
216
|
+
single viewport of the table and then travelled with the content: at 400px of horizontal scroll it
|
|
217
|
+
sat 400px to the left of where it was needed, and every column the scroll had revealed was left
|
|
218
|
+
uncovered. The overlay wraps the scroll container now, so the scrim covers what is on screen at any
|
|
219
|
+
scroll offset.
|
|
220
|
+
|
|
221
|
+
- **A compact trigger showed one chip where several fitted.** `triggerDisplay="count"` and
|
|
222
|
+
`"labels"` make the trigger hug its content, so the width the chip fit measured was decided by the
|
|
223
|
+
chips it was about to cut — each pass shrank its own input and the split settled on one. The fit
|
|
224
|
+
reads the space AVAILABLE now, the trigger's parent, which no cut can move. `ds-autocomplete` gets
|
|
225
|
+
the same correction since both pickers measure through one helper, and a `width="fill"` trigger is
|
|
226
|
+
unaffected because there the two numbers are identical.
|
|
227
|
+
|
|
11
228
|
## 0.11.1 — 2026-08-31
|
|
12
229
|
|
|
13
230
|
### Added
|
|
@@ -198,6 +415,14 @@ While the package is on `0.x`, minor releases may contain breaking changes.
|
|
|
198
415
|
|
|
199
416
|
### Fixed
|
|
200
417
|
|
|
418
|
+
- **A compact trigger showed one chip where several fitted.** `triggerDisplay="count"` and
|
|
419
|
+
`"labels"` make the trigger hug its content, so the width the chip fit measured was decided by the
|
|
420
|
+
chips it was about to cut — each pass shrank its own input and the split settled on one. The fit
|
|
421
|
+
reads the space AVAILABLE now (the trigger's parent), which no cut can move. `ds-autocomplete` gets
|
|
422
|
+
the same correction, since both pickers measure through one helper, and a `width="fill"` trigger is
|
|
423
|
+
unaffected because there the two numbers are identical.
|
|
424
|
+
|
|
425
|
+
|
|
201
426
|
- **With the filter row hidden, there was no keyboard way to pick an option.** `Enter` and `Space`
|
|
202
427
|
were consumed by the trigger before the panel's own handler saw them, so the panel toggled shut
|
|
203
428
|
instead of selecting the active row: open, arrow down, Enter, nothing chosen. The trigger delegates
|
|
@@ -239,26 +464,6 @@ While the package is on `0.x`, minor releases may contain breaking changes.
|
|
|
239
464
|
its top-level items by index rather than by label, which is not unique.
|
|
240
465
|
|
|
241
466
|
|
|
242
|
-
- **Four published migration manifests were corrected, and a repo that upgraded before today may
|
|
243
|
-
be holding the result.** These files are executed: your upgrade tooling read them, acted and
|
|
244
|
-
reported done, so a defect in one is a defect in your codebase.
|
|
245
|
-
**`0.5.1#progress-variant-remap` certified the wrong component.** Its `verify` was the text
|
|
246
|
-
belonging to the badge item beside it, checking that chips render in their status colours — so
|
|
247
|
-
a `ds-progress` still binding `variant="warn"` or `variant="indeterminate"`, or TypeScript
|
|
248
|
-
still naming a removed `ProgressVariant` member, passed the check and shipped.
|
|
249
|
-
**Two items named too few locators to be found.**
|
|
250
|
-
`0.9.0#search-height-joins-field-scale` searched only `--ds-search-height`, so a short search
|
|
251
|
-
row pinned through `--hit-min` instead was never flagged; `0.10.1#fields-shared-base-class-members`
|
|
252
|
-
searched the bare base names, so a subclass written `extends` one of the internal field bases
|
|
253
|
-
went unfound and its `success` collision surfaced only at build.
|
|
254
|
-
**`0.10.1` also gained a delete row it never carried** — a modal body torn down on `(closed)`,
|
|
255
|
-
or held behind the open flag, purely so a re-opened `ds-date-picker` starts clean. The picker
|
|
256
|
-
clears itself now, and the teardown never fired reliably: re-opening inside the leave animation
|
|
257
|
-
cancels the close, so `closed` never comes.
|
|
258
|
-
`0.11.0#exported-class-members-grew` pointed its `detect` and `verify` at a base no consumer can
|
|
259
|
-
extend; corrected, with no consequence for anyone.
|
|
260
|
-
Re-run those items if your last upgrade crossed those versions.
|
|
261
|
-
|
|
262
467
|
### What you can now DELETE
|
|
263
468
|
|
|
264
469
|
None of this is required — skipping it leaves working code that is merely redundant. Each row is a
|
|
@@ -1227,17 +1432,6 @@ None of this is required — skipping it leaves working code that is merely redu
|
|
|
1227
1432
|
neither this token nor `--ds-radius-panel` — so only `--radius-md` itself moves it, and that moves
|
|
1228
1433
|
buttons, fields and tooltips with it.
|
|
1229
1434
|
|
|
1230
|
-
- **Two migration manifests were corrected and three more were written**, so re-read them if you
|
|
1231
|
-
subclass a DS component or upgrade across a version you skipped. `0.9.0`'s named no member collisions
|
|
1232
|
-
at all — the note that now fills the gap lists **fifteen** classes whose member surface had grown, plus
|
|
1233
|
-
four newly exported symbols that can shadow a local name — and `0.8.0`'s missed the private
|
|
1234
|
-
`saveLayout` that actually stopped a build (`restoreLayout` went in beside it). **`0.6.1`, `0.6.2` and
|
|
1235
|
-
`0.9.1` had no manifest at all**, and now every released version carries one: the auto-update planner
|
|
1236
|
-
prefers a manifest and otherwise re-derives the plan from changelog prose on every run, which is what
|
|
1237
|
-
an upgrade crossing those three used to do. `0.6.2`'s holds something actionable that no
|
|
1238
|
-
machine-readable file had ever stated — a `ds-bottom-sheet` with nothing focusable inside it stopped
|
|
1239
|
-
closing on Escape — which is exactly the kind a "just fixes" patch is assumed not to have.
|
|
1240
|
-
|
|
1241
1435
|
- **`ds-avatar` takes a `name`, and the rule that reads it is replaceable.** One binding now does both
|
|
1242
1436
|
jobs a caller used to wire by hand: it derives the initials and seeds the tint. **The tint hashes the
|
|
1243
1437
|
NAME, not the initials** — two letters collide wholesale, so Alice Brown and Adam Bell used to share a
|