Wordmark: uptime in the hover, and draw it only when the console opens #543

Closed
opened 2026-11-15 12:40:10 -05:00 by cmoriarty · 1 comment
Owner

Follow-up to braid#519 (the cursive wordmark).

What happens

  1. Hovering the wordmark shows "The Braid server answers." under the version. The green dot already says that, so the line tells you nothing.
  2. The wordmark draws itself again on some screen changes. It should draw once, when the console opens.

The replay comes from useThreading (ui/src/components/BackendPanel.tsx) and threadsOn (ui/src/components/chrome.tsx). It plays on a fresh mount and whenever the state goes from lost to heard. It is likely that some screen changes make the live stream reconnect for a moment, or remount the bar.

Fix

  • When all is well, the hover shows how long the server has been up: "Up 3 h 12 min", from started_at and now in /api/status. A problem still shows its own sentence in that place.
  • The threading plays once per page load: not on a remount, a reconnect or a screen change.

Done when

A browser test opens the console, visits the main screens, and data-threaded stays at 1. The hover shows the uptime.

Follow-up to braid#519 (the cursive wordmark). ## What happens 1. Hovering the wordmark shows "The Braid server answers." under the version. The green dot already says that, so the line tells you nothing. 2. The wordmark draws itself again on some screen changes. It should draw once, when the console opens. The replay comes from `useThreading` (`ui/src/components/BackendPanel.tsx`) and `threadsOn` (`ui/src/components/chrome.tsx`). It plays on a fresh mount and whenever the state goes from lost to heard. It is likely that some screen changes make the live stream reconnect for a moment, or remount the bar. ## Fix - When all is well, the hover shows how long the server has been up: "Up 3 h 12 min", from `started_at` and `now` in `/api/status`. A problem still shows its own sentence in that place. - The threading plays once per page load: not on a remount, a reconnect or a screen change. ## Done when A browser test opens the console, visits the main screens, and `data-threaded` stays at 1. The hover shows the uptime.
Author
Owner

The wordmark threads once per page load. The count is kept on the page, so a remounted bar cannot restart it, and a reconnect does not replay it. When all is well, the hover says Up 3 h 12 min, from the new started_at in /api/status.

Evidence: the wordmark's browser journey visits the main screens, drops the server and brings it back, and data-threaded stays at 1. It fails on the old code. A vitest covers the uptime's wording.

Shipped in pull request 550 (merge 3bed64d), change console-fixes-and-session-cap, archived in pull request 551.

The wordmark threads once per page load. The count is kept on the page, so a remounted bar cannot restart it, and a reconnect does not replay it. When all is well, the hover says `Up 3 h 12 min`, from the new `started_at` in `/api/status`. Evidence: the wordmark's browser journey visits the main screens, drops the server and brings it back, and `data-threaded` stays at 1. It fails on the old code. A vitest covers the uptime's wording. Shipped in pull request 550 (merge `3bed64d`), change `console-fixes-and-session-cap`, archived in pull request 551.
Sign in to join this conversation.
No labels
No milestone
No project
No assignees
1 participant
Notifications
Due date
The due date is invalid or out of range. Please use the format "yyyy-mm-dd".

No due date set.

Dependencies

No dependencies set

Reference
cmoriarty/braid#543
No description provided.