5 Commits

Include renames

Author	SHA1	Message	Date
sneak	eca2d15249	fix: Back from Settings no longer lands on a secret screen left by the gear (closes #461) ... Leaving the private key export or recovery phrase screen drops the selection it was showing, but the settings gear had just pushed the screen onto the Back stack, so Back from Settings landed on a password prompt that could only fail. Each screen's leave handler now also takes it off the top of the stack, which is what a reopened popup already does to these screens. Back from Settings goes to the address screen for the export screen; for the recovery phrase screen, opened from Settings, it stays on Settings once, as after a reopen. Jest tests drive the gear and then Back, and each screen's own Back, for both screens; leavePrivkeyScreen() in the e2e suite expects the address screen. Model: opus-5-5	2026-10-06 21:10:42 +00:00
clawbot	cb23611a17	fix: the private key export screen opens again in the same session (closes #460) ... show() found the address line through the element inside it, then replaced the line's contents with renderAddressHtml(), which deleted that element, so the next show() in the same popup session threw before it navigated. The line now carries the export-privkey-address id itself and is looked up by it. No other view that renders an address finds its container through a child. The jest DOM stub now takes an element out of the document when its parent's contents are replaced, and a new test opens the screen twice. The #253 e2e case no longer reopens the popup before its second open. Model: opus-5-5	2026-10-06 19:43:07 +02:00
clawbot	ab1c1846a7	fix: one wording for an empty password field on every screen (closes #265)	2026-08-17 08:59:59 +02:00
clawbot	09b602579a	fix: one password-failure message across every screen (closes #172) ... A rejected password was reported three different ways depending on which screen you were on, including the fragment "Wrong password." which is not a sentence. All six decryptWithPassword call sites now show the same full sentence. Strings only -- a wrong password still fails closed on every screen and still resolves no pending approval. A test pins the invariant per call site: each decryptWithPassword call is walked out to its enclosing try and forward to that block's catch, and the prose shown there must equal the canonical sentence. Per-file matching was not enough, since a file with two call sites kept passing while one of them diverged.	2026-08-12 12:03:39 +02:00
clawbot	23712b53cb	fix: wipe the exported private key from the DOM on any view leave (closes #221)	2026-08-12 10:54:37 +02:00