diff options
| author | Adam Soltys <[email protected]> | 2026-10-11 22:30:10 -0700 |
|---|---|---|
| committer | Adam Soltys <[email protected]> | 2026-10-11 22:30:10 -0700 |
| commit | 8b65caee4348073f44c36d379bc654c27f5e9ee5 (patch) | |
| tree | d21c03cf877689d39c7fc0be263afe46b751fb1d /src/debug.js | |
| parent | 4f49202c80662e617c9d666928b7e40df37cb9b8 (diff) | |
| download | coinosv3-8b65caee4348073f44c36d379bc654c27f5e9ee5.tar.gz coinosv3-8b65caee4348073f44c36d379bc654c27f5e9ee5.zip | |
Feed: ⚡ on a locked wallet says so and opens the Accounts page. A locked wallet — the watch-only view of a sealed vault, or a nostr identity signed in over one (Adam's debug Chrome: three watch-only accounts, the vault gone, his extension identity on the first) — has no keys to pay with, and the zap button knew it: it got no handler at all, so the tap pressed the icon and nothing more, under an arrow cursor. Now the tap toasts "Your wallet is locked, so it can't zap. Unlock it to send sats." and opens the Accounts page, where the padlock and Add account are; the open feed is remembered for the way back (by URL, or by id for Following, which has none — returnAfterSignin learns the id form). tools/zap-locked-test.js.
Co-Authored-By: Claude Fable 5.1 <[email protected]>
Diffstat (limited to 'src/debug.js')
0 files changed, 0 insertions, 0 deletions