web/src/main.js lines 913 to 914, at v1.0.0-rc1: the footer legend reads "<500ms" for orange and ">500ms" for red, so exactly 500 ms belongs to neither. The code (CONFIG.latencyColors, lines 35 to 41, "the first entry whose limit the latency is below") colours 500 ms red, and the unit test at test/unit/main.test.js line 567 checks that. The other legend boundaries match the code.
How to see it: compare the footer to README.md Color coding (line 368: "| >= 500ms | Red |") and to latencyClass(500, "online"), which is text-red-500.
What is right: the legend says what the code does: ">=500ms" (or "500ms+") for red, as the README table has it.
Severity: low. Cosmetic.
Definition of done
The footer legend's red entry reads ">=500ms" (or an equivalent that includes 500), matching README.md Color coding and CONFIG.latencyColors.
A unit test renders the footer (or checks the legend text) and fails if a boundary in it disagrees with CONFIG.latencyColors.
TODO.md updated in the same commit; commit title ends (closes #N) with this issue's number.
Model: fable-5-1
`web/src/main.js` lines 913 to 914, at `v1.0.0-rc1`: the footer legend reads "<500ms" for orange and ">500ms" for red, so exactly 500 ms belongs to neither. The code (`CONFIG.latencyColors`, lines 35 to 41, "the first entry whose limit the latency is below") colours 500 ms red, and the unit test at `test/unit/main.test.js` line 567 checks that. The other legend boundaries match the code.
**How to see it**: compare the footer to `README.md` Color coding (line 368: "| >= 500ms | Red |") and to `latencyClass(500, "online")`, which is `text-red-500`.
**What is right**: the legend says what the code does: ">=500ms" (or "500ms+") for red, as the README table has it.
**Severity**: low. Cosmetic.
## Definition of done
- [ ] The footer legend's red entry reads ">=500ms" (or an equivalent that includes 500), matching `README.md` Color coding and `CONFIG.latencyColors`.
- [ ] A unit test renders the footer (or checks the legend text) and fails if a boundary in it disagrees with `CONFIG.latencyColors`.
- [ ] `TODO.md` updated in the same commit; commit title ends ` (closes #N)` with this issue's number.
Model: fable-5-1
clawbot
self-assigned this 2026-10-14 16:08:47 +02:00
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.
web/src/main.jslines 913 to 914, atv1.0.0-rc1: the footer legend reads "<500ms" for orange and ">500ms" for red, so exactly 500 ms belongs to neither. The code (CONFIG.latencyColors, lines 35 to 41, "the first entry whose limit the latency is below") colours 500 ms red, and the unit test attest/unit/main.test.jsline 567 checks that. The other legend boundaries match the code.How to see it: compare the footer to
README.mdColor coding (line 368: "| >= 500ms | Red |") and tolatencyClass(500, "online"), which istext-red-500.What is right: the legend says what the code does: ">=500ms" (or "500ms+") for red, as the README table has it.
Severity: low. Cosmetic.
Definition of done
README.mdColor coding andCONFIG.latencyColors.CONFIG.latencyColors.TODO.mdupdated in the same commit; commit title ends(closes #N)with this issue's number.Model: fable-5-1