4 Commits

Include renames

Author	SHA1	Message	Date
sneak	50326ad933	fix: the address screen shows a token just added at its fetched balance, not 0.0000 (closes #516) ... A balance refresh that returns now draws the balances on AddressDetail or AddressToken again when that screen is up, not only the wallet list; their transaction lists are left alone. A token added on AddToken reads `quantity unknown` instead of 0.0000 until a refresh that started with it tracked has fetched every address's token balances. To tell an address whose token balances the explorer did not return, the refresh takes them off its copy of the wallets before fetching. Model: opus-5-5	2026-10-21 02:43:13 +00:00
clawbot	9c67e87ae5	fix: tracked tokens are kept per network, and bundled picks are offered on mainnet only (closes #523) ... A network switch puts the outgoing network's tracked tokens away in a new persisted field, networkTrackedTokens, and brings back the incoming network's list, or an empty one, as endpoints are kept; the background's switch uses the same function. The two add-token screens offer their common-token picks on Ethereum Mainnet only. After a switch in Settings, Back renders the screen it lands on again, and the stack is cut at the first screen that cannot be rendered from saved state, or at AddressToken for any token but the native one; the cut stack is saved with the switch. ConfirmTx drawn again keeps the network it was reviewed on. A contract lookup that answers after a switch adds nothing. Model: opus-5-5	2026-10-19 11:50:39 +02:00
clawbot	ad1b4f0557	fix: a popup reload no longer logs the requests it cancels on most screens (closes #475) ... The transaction lists and ENS name lookups on the address and token screens, the address scan after a wallet is created, the endpoint checks in Settings, the wait screen's receipt check, the Send screen's Max fee estimate and the token lookup on both add-token screens now check the signal the popup aborts on pagehide before reporting a failed request. scanForAddresses(), resolveEnsNames() and lookupTokenInfo() take the signal. End-to-end tests reload the popup on the address screen and during the address scan with their requests held. Jest tests show each of these reports a real failure and stays silent once the popup has closed. The transaction detail and confirmation screens are left out: they discard the popup context that carries the signal. Model: opus-5-5	2026-10-06 22:09:08 +02:00
clawbot	5bf8b5ff1f	fix: keep the flash line to its one line at any message length (closes #252) ... The flash line reserves one line, so a message that wrapped pushed the screen below it down. #flash-msg no longer wraps: text too long for it is cut with an ellipsis, and showFlash() puts the whole message in its title. Every message is also reworded to at most 50 characters so none is cut, and the add-token screens flash a fixed line for any error other than the two lookup messages, logging the detail. A new end-to-end test writes a message several lines long into the line and fails if the line or the screen below it moves. Model: opus-5-5	2026-10-04 10:22:51 +02:00