6f3b56ad84
The `⏳ MM:SS` chip on an asked-with-timeout question was rendered once and then frozen — the operator saw stale info (e.g. 48s sitting unchanged for the whole TTL window) (issue #335). Stamp the deadline onto the chip as `data-deadline` and run a single page-wide setInterval that refreshes every `.q-ttl[data- deadline]`'s textContent each second. No re-render of the questions section; no new state on the client. No-op when no chips are on screen. Also pulls the bucketed seconds-to-string logic into a `formatTtl` helper so the renderer and the ticker share one source of truth. Closes #335. |
||
|---|---|---|
| .. | ||
| app.js | ||
| dashboard.css | ||
| index.html | ||