3 Commits

Include renames

Author	SHA1	Message	Date
sneak	1effa7c6eb	fix: a network switch in Settings leaves no balance from the previous network stored (closes #653) ... The switch is now made on the stored record that its save has just read. The switched fields are then copied into the page's state. A save writes only the fields that the page changed since its last save. A switch made on the page's state alone mishandled what another page stored since then: - A balance from the previous network stayed under the new network. - A token tracked on the previous network moved to the new network. - An endpoint URL saved for the previous network was replaced by the page's older one. Tests store each of these before the switch and check the stored record after it. Model: opus-5-5	2026-10-27 07:22:50 +00:00
clawbot	2691702f80	fix: an open popup follows a network switch the background saves (closes #650) ... When the background saves a network switch after the user approves a site's request, or another popup page saves one, an open popup takes the new network from the stored record inside a save, holding the lock, and checks the record once at start-up for a switch saved before it listened. The network it takes is not counted as the popup's own change, even when that save fails to write. It then leaves the page as a switch in Settings does. A switch in Settings is now made inside its own save too, so one picked while a follow waits for the lock is made after it. The popup never switches the network itself. Model: opus-5-5	2026-10-21 04:26:51 +02:00
clawbot	e517219038	fix: a balance refresh that returns after a network switch writes nothing (closes #577) ... The popup's doRefreshAndRender() and the background's backgroundRefresh() each note the network a refresh starts on and write its balances only if that network is still the active one when the requests return. Otherwise nothing is written and lastBalanceRefresh stays as the switch left it. The background checks inside updateState(). The popup refreshes a copy of its wallets and copies the results onto `state` from inside its save, under the lock, only if both its own network and the stored record's still match, so a switch the background makes is caught too. saveState() takes an optional function, run there on the stored record before the page's state is compared, that may change `state` or return false to cancel the write. Model: opus-5-5	2026-10-20 22:59:51 +02:00