@dropins/storefront-auth 4.0.1-beta.1 → 4.0.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 +27 -0
- package/package.json +1 -1
package/CHANGELOG.md
CHANGED
|
@@ -1,5 +1,32 @@
|
|
|
1
1
|
# @dropins/storefront-auth
|
|
2
2
|
|
|
3
|
+
## 4.0.1
|
|
4
|
+
|
|
5
|
+
### Patch Changes
|
|
6
|
+
|
|
7
|
+
- 0a4341a: Bump SDK stable versions
|
|
8
|
+
- 857e7aa: Fix visual heading text not marked as heading across sign in, sign up, reset password and update password forms
|
|
9
|
+
- 5b8e0df: Fix incorrect and missing `autocomplete` attributes on form fields.
|
|
10
|
+
|
|
11
|
+
The email field on sign in, sign in popover, forgot password, and create account previously used `autocomplete="username"`, which does not tell browsers and password managers the field expects an email address. It now uses `autocomplete="email"`.
|
|
12
|
+
|
|
13
|
+
The first name and last name fields on create account were missing an `autocomplete` attribute entirely; they now use `given-name` and `family-name` respectively.
|
|
14
|
+
|
|
15
|
+
The password and confirm password fields on the sign up form used incorrect/invalid `autocomplete` values (`current-password` and `confirmPassword`, the latter not a valid HTML5 token). Both now use `new-password`, the correct value for a field that sets a new password.
|
|
16
|
+
|
|
17
|
+
This helps browsers and assistive technology correctly identify the purpose of each field, making autofill and form-filling easier for everyone, including people using screen readers or who have difficulty typing.
|
|
18
|
+
|
|
19
|
+
- 57f64d7: Fix VALIDATE_TOKEN query incompatibility with ACCS.
|
|
20
|
+
|
|
21
|
+
The token validation query previously included `customer { group { uid } }`, a field not available in ACCS backends, causing a schema error during drop-in initialization.
|
|
22
|
+
|
|
23
|
+
The query is now split into two variants:
|
|
24
|
+
|
|
25
|
+
- A minimal ACCS-compatible query used by default
|
|
26
|
+
- A query that includes `group { uid }` for Adobe Commerce Optimizer (ACO) price book resolution, used only when `adobeCommerceOptimizer: true` is set in the init config
|
|
27
|
+
|
|
28
|
+
No changes are required for existing implementations. Merchants not using ACO are unaffected. Merchants using ACO continue to receive the `auth/group-uid` event as before.
|
|
29
|
+
|
|
3
30
|
## 4.0.1-beta.1
|
|
4
31
|
|
|
5
32
|
### Patch Changes
|
package/package.json
CHANGED