Each host row has a round dot left of the host's name. It has the same size and shape as the dots of the color legend in the footer, where gray means offline. The row's dot is gray in every state: beside a green 8ms, an orange 488ms and a timeout alike. Nothing in web/src/main.js ever gives it a color. Read against the legend, it marks every host offline.
What should happen: the dot takes the legend color of the row's latest figure. It is gray after a failed check, while paused and before the first result.
Decided: the dot is given a color, not removed. The pause code already sets the dot to gray (greyOutUI), which only makes sense for a dot that has a color. Removing the dot instead would mean deleting one element from hostRowHTML.
Definition of done
Each row's dot shows the latency color of its latest result, from the same table as the figure (CONFIG.latencyColors).
It is gray after a failed check, while paused and before the first result.
A unit test covers the dot's color for an answered check and for a failed one.
Model: opus-5-5
Each host row has a round dot left of the host's name. It has the same size and shape as the dots of the color legend in the footer, where gray means `offline`. The row's dot is gray in every state: beside a green `8ms`, an orange `488ms` and a `timeout` alike. Nothing in `web/src/main.js` ever gives it a color. Read against the legend, it marks every host offline.
Found by the acceptance test on https://git.eeqj.de/sneak/netwatch/issues/204.
**Steps**: open the page and wait for the figures.
**What happens**: every row's dot stays gray.
**What should happen**: the dot takes the legend color of the row's latest figure. It is gray after a failed check, while paused and before the first result.
Decided: the dot is given a color, not removed. The pause code already sets the dot to gray (`greyOutUI`), which only makes sense for a dot that has a color. Removing the dot instead would mean deleting one element from `hostRowHTML`.
## Definition of done
- [ ] Each row's dot shows the latency color of its latest result, from the same table as the figure (`CONFIG.latencyColors`).
- [ ] It is gray after a failed check, while paused and before the first result.
- [ ] A unit test covers the dot's color for an answered check and for a failed one.
Model: opus-5-5
Built in #218 (branch issue-207-color-host-dot): each row's dot takes the latency color of its latest figure, gray after a failed check, while paused and before the first result.
Model: opus-5-5
Built in https://git.eeqj.de/sneak/netwatch/pulls/218 (branch `issue-207-color-host-dot`): each row's dot takes the latency color of its latest figure, gray after a failed check, while paused and before the first result.
Model: opus-5-5
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.
Each host row has a round dot left of the host's name. It has the same size and shape as the dots of the color legend in the footer, where gray means
offline. The row's dot is gray in every state: beside a green8ms, an orange488msand atimeoutalike. Nothing inweb/src/main.jsever gives it a color. Read against the legend, it marks every host offline.Found by the acceptance test on #204.
Steps: open the page and wait for the figures.
What happens: every row's dot stays gray.
What should happen: the dot takes the legend color of the row's latest figure. It is gray after a failed check, while paused and before the first result.
Decided: the dot is given a color, not removed. The pause code already sets the dot to gray (
greyOutUI), which only makes sense for a dot that has a color. Removing the dot instead would mean deleting one element fromhostRowHTML.Definition of done
CONFIG.latencyColors).Model: opus-5-5
Built in #218 (branch
issue-207-color-host-dot): each row's dot takes the latency color of its latest figure, gray after a failed check, while paused and before the first result.Model: opus-5-5