test: a failing e2e test leaves no fixture switch or send screen behind (closes #318)

A test that turns a fixture switch on for itself alone turns it off in a
finally, so a failure no longer reddens the tests after it. The two tests
that drive the popup's own send also return it to the address screen,
reopening the popup to leave a wait for a receipt. The lying-decimals()
test asserts that nothing was broadcast as soon as the send ends, before
waiting for the failure screen. ethCallResult() answers an override of 0
instead of falling back to the explorer's scale.

Model: opus-5-5

TODO.md

@@ -57,16 +57,6 @@ but the review is broader than any of them.
   60-second wait. The fixture's `decimals()` override tells 0 from no override,
   so a token with no decimal places can be fixtured.
 
-- 2026-10-05: Chrome draws the popup in its monospace font
-  ([#418](https://git.eeqj.de/sneak/AutistMask/issues/418)), as Firefox does.
-  Chrome adds a stylesheet of its own to extension pages that sets the font on
-  `body`, and it beat Tailwind's `font-mono`: Tailwind 4 puts its classes in a
-  cascade layer, and a rule outside any layer wins over them. `body` now carries
-  `font-mono!`, which marks the class important. Both end-to-end suites check
-  the popup's font. The same stylesheet also makes Chrome draw the popup's text
-  at 12px rather than the 14px `text-sm` asks for; that is unchanged, and filed
-  as [#456](https://git.eeqj.de/sneak/AutistMask/issues/456).
-
 - 2026-10-05: Dead code removed and copied view helpers shared
   ([#168](https://git.eeqj.de/sneak/AutistMask/issues/168)). AddressDetail and
   AddressToken each defined their own `isoDate()` and `timeAgo()` in place of

src/popup/index.html

@@ -6,10 +6,7 @@
         <title>AutistMask</title>
         <link rel="stylesheet" href="styles.css" />
     </head>
-    <!-- Chrome gives extension pages a stylesheet of its own that sets the
+    <body class="bg-bg text-fg font-mono text-sm">
-         font on body, and a Tailwind class beats it only when marked
-         important: hence font-mono! rather than font-mono. -->
-    <body class="bg-bg text-fg font-mono! text-sm">
         <div id="app" class="p-2 pr-5 overflow-x-hidden">
             <!-- ============ GLOBAL TITLE BAR ============ -->
             <div

tests/e2e/firefox/run.js

@@ -108,20 +108,6 @@ step("popup loads and reaches the welcome view", async (env) => {
     assert(title === "AutistMask", "unexpected popup title: " + title);
 });
 
-// The same check as the Chrome suite's (#418), so both browsers are held to
-// the same font.
-step("the popup is drawn in the monospace font it declares", async (env) => {
-    const font = await env.driver.execute(
-        "return getComputedStyle(document.body).fontFamily;",
-    );
-    // --font-mono in src/popup/styles/main.css, as the browser writes it out.
-    assert(
-        font ===
-            'ui-monospace, SFMono-Regular, "SF Mono", Menlo, Consolas, "Liberation Mono", monospace',
-        "the popup is drawn in " + font + ", not in --font-mono",
-    );
-});
-
 step("wallet creation through the UI reaches the main view", async (env) => {
     const d = env.driver;
     await d.click("#btn-welcome-add");

tests/e2e/run.js

@@ -93,20 +93,6 @@ test("popup loads and reaches the welcome view", async (env) => {
     assert(title === "AutistMask", "unexpected popup title: " + title);
 });
 
-// Chrome's own stylesheet for extension pages sets the font on body; see the
-// comment above <body> in src/popup/index.html.
-test("the popup is drawn in the monospace font it declares (#418)", async (env) => {
-    const font = await env.page.evaluate(
-        () => getComputedStyle(document.body).fontFamily,
-    );
-    // --font-mono in src/popup/styles/main.css, as the browser writes it out.
-    assert(
-        font ===
-            'ui-monospace, SFMono-Regular, "SF Mono", Menlo, Consolas, "Liberation Mono", monospace',
-        "the popup is drawn in " + font + ", not in --font-mono",
-    );
-});
-
 // The empirical half of #182. The manifest change is only a claim about
 // what the CSP permits; this is the observation. Two things have to hold
 // together, and the run covers both: the popup realm compiles WASM (here),