@adobe-commerce/elsie 2.1.0-beta.8 → 2.1.0
This diff represents the content of publicly available package versions that have been released to one of the supported registries. The information contained in this diff is provided for informational purposes only and reflects changes between package versions as they appear in their respective public registries.
- package/CHANGELOG.md +119 -0
- package/package.json +2 -2
package/CHANGELOG.md
CHANGED
|
@@ -1,5 +1,124 @@
|
|
|
1
1
|
# @adobe-commerce/elsie
|
|
2
2
|
|
|
3
|
+
## 2.1.0
|
|
4
|
+
|
|
5
|
+
### Minor Changes
|
|
6
|
+
|
|
7
|
+
- e8f81dd: **Incrementer**: Add optional `label` prop that renders a visible
|
|
8
|
+
`<label>` element associated with the input field via `htmlFor`/`id`. This
|
|
9
|
+
addresses WCAG 3.3.2 (Labels or Instructions) which requires form fields to
|
|
10
|
+
have visible labels.
|
|
11
|
+
- d9ac070: feat(a11y): add LiveRegion component and Button loading state for
|
|
12
|
+
WCAG 4.1.3
|
|
13
|
+
|
|
14
|
+
- New `LiveRegion` component: a visually-hidden, always-mounted
|
|
15
|
+
`role="status"` span for announcing status changes to screen readers without
|
|
16
|
+
focus movement. Accepts `message` (string toggled between empty and the
|
|
17
|
+
label) and `politeness` ("polite" | "assertive"). Use this alongside
|
|
18
|
+
`Skeleton` and `ProgressSpinner` instead of relying on those components' own
|
|
19
|
+
`role="status"` which fires unreliably when they are conditionally mounted.
|
|
20
|
+
- `Button` now accepts `loading?: boolean` (sets `aria-busy` on the button
|
|
21
|
+
element) and `loadingLabel?: string` (renders a sibling `LiveRegion` outside
|
|
22
|
+
the button element — live regions must not be nested inside interactive
|
|
23
|
+
elements).
|
|
24
|
+
|
|
25
|
+
- 4cecbe2: Bump `preact` from `~10.22.1` to `~10.29.7` and `@preact/signals`
|
|
26
|
+
from `1.3.0` to `^2.3.1`, matching the preact version most external consumers
|
|
27
|
+
already have installed.
|
|
28
|
+
|
|
29
|
+
Preact 10.29 narrowed its generic `HTMLAttributes<Target>` typings: `value`,
|
|
30
|
+
`checked`, `alt`, `width`, `height`, `loading`, `srcSet`, `required`, and
|
|
31
|
+
`name` moved out into per-element interfaces instead of being available on
|
|
32
|
+
every element generically. This restores the type declarations for the
|
|
33
|
+
components that were affected (`Input`, `TextArea`, `Checkbox`, `Image`,
|
|
34
|
+
`Incrementer`, `Button`, `ActionButton`, `Picker`, `InputFile`, `Accordion`,
|
|
35
|
+
`CartItem`, `Slot`) — no runtime or prop-API changes, just typings that would
|
|
36
|
+
otherwise break consumers' own TypeScript builds.
|
|
37
|
+
|
|
38
|
+
- cadd9f3: feat(lib): add `sanitizeHtml` and `createSanitizedHtml` helpers
|
|
39
|
+
(backed by DOMPurify) for safely rendering untrusted HTML via
|
|
40
|
+
`dangerouslySetInnerHTML`. By default only basic inline formatting tags are
|
|
41
|
+
allowed (`DEFAULT_ALLOWED_TAGS`); callers can extend or replace the
|
|
42
|
+
allow-list.
|
|
43
|
+
|
|
44
|
+
### Patch Changes
|
|
45
|
+
|
|
46
|
+
- af12113: Accessibility color contrast fixes (WCAG 1.4.11, 1.4.3):
|
|
47
|
+
|
|
48
|
+
- **ProgressSpinner**: Use `--color-neutral-600` for inactive border (3.94:1
|
|
49
|
+
vs previous 1.46:1)
|
|
50
|
+
- **Button disabled states**: Use `--color-neutral-700` for text in all
|
|
51
|
+
variants (4.21:1 on neutral-300, 5.74:1 on white vs previous 1.36:1/1.91:1)
|
|
52
|
+
|
|
53
|
+
- 9a3dabd: Fix multiple accessibility issues in the `InputPassword` and `Field`
|
|
54
|
+
components:
|
|
55
|
+
|
|
56
|
+
- The input `aria-label` now uses the consumer-provided `floatingLabel` or
|
|
57
|
+
`placeholder` instead of a hardcoded "Password" translation, so the
|
|
58
|
+
accessible name matches the visible label (WCAG 2.5.3 Label in Name).
|
|
59
|
+
- The show/hide toggle button `aria-label` now includes the field label (e.g.
|
|
60
|
+
"Click to show password: New Password") so each instance is uniquely
|
|
61
|
+
identifiable by screen readers (WCAG 2.4.6 Headings and Labels).
|
|
62
|
+
- The `PasswordStatusIndicator` now receives a unique `id` via `useId()` and
|
|
63
|
+
the input `aria-describedby` references it, programmatically associating
|
|
64
|
+
password requirement messages with their field (WCAG 3.3.1 Error
|
|
65
|
+
Identification).
|
|
66
|
+
- The `Field` component no longer overrides the child's `aria-describedby`
|
|
67
|
+
with `undefined` when no error is present, preserving any existing
|
|
68
|
+
association.
|
|
69
|
+
|
|
70
|
+
- fe6e31d: Fix the `elsie concurrently` builder passing `killOthers` to the
|
|
71
|
+
`concurrently` package, which was renamed to `killOthersOn` in
|
|
72
|
+
`concurrently@10`. Since `concurrently` doesn't validate unknown options, the
|
|
73
|
+
mismatch silently no-opped `-k`/`--kill-others`, leaving sibling processes
|
|
74
|
+
(e.g. the `http-server` serving `storybook-static`) running after another
|
|
75
|
+
process in the group exited — hanging commands like `test-storybook-ci` until
|
|
76
|
+
an external timeout killed them.
|
|
77
|
+
- 1256599: Cap the `eslint-plugin-cypress` peer dependency range at `<7.0.0`.
|
|
78
|
+
The unbounded `>=3.0.0` range let npm's resolver consider
|
|
79
|
+
`eslint-plugin-cypress@7`, which peer-requires `eslint@>=10` and conflicts
|
|
80
|
+
with elsie's own `eslint@^9.39.5` dependency — even though
|
|
81
|
+
`eslint-plugin-cypress` remains an optional peer. Versions up to `6.4.4` still
|
|
82
|
+
support `eslint@>=9`, so the range now stays within what's actually
|
|
83
|
+
compatible.
|
|
84
|
+
- 089ba5c: fix(a11y): prevent dummy update when keyboard focus moves to
|
|
85
|
+
Incrementer buttons and add aria-valuetext for VoiceOver
|
|
86
|
+
- d59c153: Fix `Modal` accessibility: while the modal is open, sibling content
|
|
87
|
+
in `document.body` is now hidden from assistive technology with
|
|
88
|
+
`aria-hidden="true"`, preventing screen reader users from navigating outside
|
|
89
|
+
the modal with arrow keys. The attribute is removed automatically when the
|
|
90
|
+
modal closes. Other portal roots (e.g. nested modals or toasts) and elements
|
|
91
|
+
that already declare `aria-hidden` are left untouched.
|
|
92
|
+
- c9674f9: fix(a11y): add aria-current="page" to active pagination button and
|
|
93
|
+
fix active indicator contrast (WCAG 1.4.11, 4.1.2)
|
|
94
|
+
- 6957e90: Fix `PasswordStatusIndicator` requirement status changes (e.g. the
|
|
95
|
+
length or character-class error icon) not being announced by screen readers.
|
|
96
|
+
The container now carries `role="status"` and `aria-live="polite"` so
|
|
97
|
+
assistive technology announces requirement changes as they happen (WCAG
|
|
98
|
+
4.1.3).
|
|
99
|
+
- 238981b: Pin Preact to 10.22.1, the latest version verified against the
|
|
100
|
+
affected consumer checkout flow without the AEM Asset Slot `insertBefore`
|
|
101
|
+
crash. Also restore `@preact/signals` 1.3.0, the compatible Signals release
|
|
102
|
+
used with this Preact version. Preact 10.23.0 introduced child-diffing changes
|
|
103
|
+
that expose the existing detached render-root and raw DOM graft behavior.
|
|
104
|
+
- 406a36d: Restore the existing Slot implementation and temporarily downgrade
|
|
105
|
+
Preact from 10.29 to 10.28.4, the latest pre-10.29 release, to avoid
|
|
106
|
+
intermittent `insertBefore` crashes in AEM Asset image Slots while the
|
|
107
|
+
underlying DOM graft and render-root ownership changes are developed and
|
|
108
|
+
validated separately.
|
|
109
|
+
- fea748d: Pin Preact to 10.27.0, the latest version verified not to throw with
|
|
110
|
+
the existing detached render-root mechanism. Preact 10.27.1 and newer
|
|
111
|
+
reproduce intermittent `insertBefore` crashes in AEM Asset image Slots.
|
|
112
|
+
- 85e5b20: fix(a11y): keep RadioButton's focusable input anchored to its visible
|
|
113
|
+
label when the page scrolls, preventing focus from appearing obscured or
|
|
114
|
+
off-screen (WCAG 2.4.11)
|
|
115
|
+
- 896c6c9: reCAPTCHA form types are now configurable via feature flag.
|
|
116
|
+
COMPANY_CREATE is no longer in the default form-type map. B2B storefronts pass
|
|
117
|
+
`{ b2bEnabled: true }` to `setConfig()` to include it in the configuration
|
|
118
|
+
query.
|
|
119
|
+
- a920177: fix(Incrementer): prevent quantity input flicker during in-progress
|
|
120
|
+
typing, and prevent double onValue call when debounce fires before blur
|
|
121
|
+
|
|
3
122
|
## 2.1.0-beta.8
|
|
4
123
|
|
|
5
124
|
### Patch Changes
|
package/package.json
CHANGED
|
@@ -1,6 +1,6 @@
|
|
|
1
1
|
{
|
|
2
2
|
"name": "@adobe-commerce/elsie",
|
|
3
|
-
"version": "2.1.0
|
|
3
|
+
"version": "2.1.0",
|
|
4
4
|
"license": "SEE LICENSE IN LICENSE.md",
|
|
5
5
|
"description": "Domain Package SDK",
|
|
6
6
|
"engines": {
|
|
@@ -32,7 +32,7 @@
|
|
|
32
32
|
"devDependencies": {
|
|
33
33
|
"@adobe-commerce/event-bus": "~1.1.1",
|
|
34
34
|
"@adobe-commerce/fetch-graphql": "~1.3.1",
|
|
35
|
-
"@adobe-commerce/recaptcha": "1.3.0
|
|
35
|
+
"@adobe-commerce/recaptcha": "1.3.0",
|
|
36
36
|
"@adobe-commerce/storefront-design": "~1.1.1",
|
|
37
37
|
"@chromatic-com/storybook": "^5",
|
|
38
38
|
"@dropins/build-tools": "~1.2.1"
|