BUGS: note the one Firefox console line that is navigation, not a fault

Co-Authored-By: Claude Opus 5 <noreply@anthropic.com>
This commit is contained in:
Mitchell-Johnson
2026-09-22 00:11:37 -07:00
co-authored by Claude Opus 5
parent 5412e316de
commit 5761ee09db
+7
View File
@@ -601,3 +601,10 @@ input, and a read-only token refused by all of them. The public demo page and in
Top tab on all four machines — including `grid`'s sixteen cores and thirteen filesystems, which Top tab on all four machines — including `grid`'s sixteen cores and thirteen filesystems, which
scroll inside their boxes — its rate control, its filter, and three skins repainting it. scroll inside their boxes — its rate control, its filter, and three skins repainting it.
`hamtv`'s eMMC really is called `hB8aP>`; that is what the device reports. `hamtv`'s eMMC really is called `hB8aP>`; that is what the device reports.
Firefox earns its place in this: three of the six above were invisible in Chromium, which
swallows a failed WebSocket where Firefox writes it to the console. One thing it reports is
*not* a fault — a page torn down by navigation while a terminal's socket is still shaking
hands logs "can't establish a connection". Sitting still on a page produces none, the address
is right, and the terminal belongs to the machine asked; `sockets.cjs` checks that ownership
rather than the noise.