The Settings network handler now redraws the red banner once the switch is saved. On Settings, a switch to Sepolia puts up the [TESTNET] banner and a switch back to mainnet takes it down. Before, only showView() and popup start redrew the banner, so it stayed wrong until the user left Settings.
The Chrome browser suite gains one test, right after the Settings section in tests/e2e/run.js. It switches to Sepolia and back on Settings and reads the banner after each switch. It reads the banner only once the switch's "Switched to ..." flash is up: the flash is the handler's last step and any screen change clears it, so the banner it reads is the one the switch left on Settings. Without the change to settings.js the test fails at the first switch.
Worth knowing:
The test expects exactly [TESTNET] because the suite runs a release build with runtime debug mode off.
If the test fails it leaves the wallet on Sepolia, and later tests that expect mainnet fail with it.
README: one paragraph in End-to-End Tests names the new test. The Screen Map already says the banner follows the active network, so it is unchanged.
Model: opus-5-5
Fixes https://git.eeqj.de/sneak/AutistMask/issues/511.
The Settings network handler now redraws the red banner once the switch is saved. On Settings, a switch to Sepolia puts up the `[TESTNET]` banner and a switch back to mainnet takes it down. Before, only `showView()` and popup start redrew the banner, so it stayed wrong until the user left Settings.
The Chrome browser suite gains one test, right after the Settings section in `tests/e2e/run.js`. It switches to Sepolia and back on Settings and reads the banner after each switch. It reads the banner only once the switch's "Switched to ..." flash is up: the flash is the handler's last step and any screen change clears it, so the banner it reads is the one the switch left on Settings. Without the change to `settings.js` the test fails at the first switch.
Worth knowing:
- The test expects exactly `[TESTNET]` because the suite runs a release build with runtime debug mode off.
- If the test fails it leaves the wallet on Sepolia, and later tests that expect mainnet fail with it.
- README: one paragraph in End-to-End Tests names the new test. The Screen Map already says the banner follows the active network, so it is unchanged.
Model: opus-5-5
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
Blocking a user prevents them from interacting with repositories, such as opening or commenting on pull requests or issues. Learn more about blocking a user.
Fixes #511.
The Settings network handler now redraws the red banner once the switch is saved. On Settings, a switch to Sepolia puts up the
[TESTNET]banner and a switch back to mainnet takes it down. Before, onlyshowView()and popup start redrew the banner, so it stayed wrong until the user left Settings.The Chrome browser suite gains one test, right after the Settings section in
tests/e2e/run.js. It switches to Sepolia and back on Settings and reads the banner after each switch. It reads the banner only once the switch's "Switched to ..." flash is up: the flash is the handler's last step and any screen change clears it, so the banner it reads is the one the switch left on Settings. Without the change tosettings.jsthe test fails at the first switch.Worth knowing:
[TESTNET]because the suite runs a release build with runtime debug mode off.Model: opus-5-5
Review: PASS
Model: opus-5-5