fix: a network switch in Settings updates the testnet banner at once (closes #511)
check / check (push) Canceled after 0s
e2e / e2e-chrome (push) Canceled after 0s
e2e / e2e-firefox (push) Canceled after 0s

The Settings network handler now redraws the red banner once the switch
is saved, so it appears on a switch to Sepolia and goes on a switch back
to mainnet while Settings is still on screen. Before, the banner changed
only when the next screen came up. The Chrome browser suite switches
both ways on Settings and reads the banner each time.

Model: opus-5-5
This commit was merged in pull request #619.
This commit is contained in:
2026-10-19 22:53:11 +02:00
parent 30dca1454e
commit 96446f4661
4 changed files with 68 additions and 2 deletions
+2 -1
View File
@@ -128,7 +128,8 @@ function showView(name) {
}
// Create or update the debug/insecure warning banner.
// Called on every view switch and after the settings debug toggle changes.
// Called on every view switch, after the settings debug toggle changes, and
// after a network switch in Settings.
// The banner is shown when the compile-time DEBUG constant is true OR when
// the user has enabled runtime debug mode via the settings easter egg, OR
// when the active network is a testnet.
+3 -1
View File
@@ -343,11 +343,13 @@ function init(ctx) {
// switch request.
notify({ type: "AUTISTMASK_NETWORK_CHANGED", chainId: net.chainId });
resetRenderedViews();
// Settings itself is brought up to date for the new network here.
// Settings itself, and the testnet banner above it, are brought up
// to date for the new network here.
markViewRendered("settings");
$("settings-rpc").value = state.rpcUrl;
$("settings-blockscout").value = state.blockscoutUrl;
renderTrackedTokens();
updateDebugBanner(state.currentView);
showFlash("Switched to " + net.name + ".");
});