docs(collection-map): tighten Refresh-button open question wording

This commit is contained in:
SJCoetz 2026-07-11 23:31:41 +02:00
parent 191668088c
commit 02458909f7

View file

@ -206,7 +206,7 @@ Unchanged.
- The status filter button group (`page.tsx:757-776`).
- The readiness filter button group (`page.tsx:780-800`).
- The search input (`page.tsx:803-812`).
- The Refresh button (`page.tsx:813-816`) — open question; see below.
- The Refresh button (`page.tsx:813-816`) — see the "Open question" section below.
## Out of scope
@ -220,13 +220,13 @@ Unchanged.
## Open question
The Refresh button (`page.tsx:813`) is technically not a filter, but it lives in the toolbar next to the filters. After the cleanup, should it:
The Refresh button (`page.tsx:813`) is technically not a filter, but it lives in the toolbar next to the filters. After the cleanup, three options:
(A) Stay in the top-right of the toolbar (next to Traffic + Fullscreen), or
(B) Move into the KPI strip as a small icon button on the "Mapped stops" tile, or
(C) Be removed entirely (operators wait for the next date change or the 20-second live poll already in place elsewhere)?
- **(A) Stay in the toolbar** — keep it where it is, just visually adjacent to Traffic + Fullscreen now that the filters are gone.
- **(B) Move into the KPI strip** — small icon button on the "Mapped stops" tile, so refresh lives next to the number it refreshes.
- **(C) Remove it entirely** — operators wait for the next date change or rely on the 20-second live poll already in place elsewhere in the app.
Default if you don't pick: **(A) — stay in the toolbar.** It costs nothing, the icon is universally understood, and removing it removes a manual escape hatch.
Default if the user doesn't pick: **(A) — stay in the toolbar.** It costs nothing, the icon is universally understood, and removing it removes a manual escape hatch.
## Tests