fix: one wording for an empty password field on every screen (closes #265) #296

Merged
clawbot merged 1 commits from issue-265-empty-password-copy into next 2026-08-17 08:59:59 +02:00

1 Commits

Author SHA1 Message Date
3f3bfcb010 fix: one wording for an empty password field on every screen (closes #265)
All checks were successful
check / check (push) Successful in 28s
e2e / e2e-chrome (push) Successful in 46s
e2e / e2e-firefox (push) Successful in 16s
The private key export screen answered an empty password field with "Password
is required." where the other five screens that ask for the password say
"Please enter your password." Same condition, two sentences, and a user hitting
both had no reason to think they meant the same thing. The majority wording
wins; the export screen now says it too.

Strings only. Every screen still refuses to proceed on an empty field exactly
as before.

tests/passwordMessages.test.js already pinned the rejected-password sentence
per decryptWithPassword call site; it now pins the empty-field sentence the
same way, walking each decrypt's password variable back to the guard that
rejects it blank and requiring the prose there to be the canonical sentence and
nothing else. Anchoring on the decrypt keeps the wallet-creation screen out of
the set, where an empty field means a password being chosen rather than
entered -- a different condition with its own wording.

Every error container measured at a 360px viewport in the pinned Playwright
container against the built popup. The export screen's container holds at 20px
with the section below it at the same offset for the empty reserved state, the
old string and the new one.
2026-08-17 06:57:03 +00:00