webui(events): the capture/map/bind chain is navigable twice on one page #1664

Open
opened 2026-10-27 13:41:18 +00:00 by sam · 0 comments
Owner

The Events page offers the same three destinations through two full navigation affordances stacked one above the other.

The numbered step strip (Capture → Map → Bind, with counts) is a clickable <ol> of buttons, and directly beneath it the Tabs list repeats the same three panels as Inspector | Mappings | Bindings, with the same counts from the same counts source. Both drive the same ?tab= query parameter through the same show(), so the page renders one control set twice under two different label vocabularies for the same three things.

This is deliberate rather than a regression — counts.ts documents it ('The three-step strip and the tab chips both show one number per step'), and EventsPage.vue wires both to the one handler. It is filed because the result reads as a duplicated wizard, and because the two vocabularies (Capture/Map/Bind vs Inspector/Mappings/Bindings) name the same three panels differently in the same view.

Deciding which one survives is a design call, not a code one: dropping the strip makes the chain the tab list and loses the numbered-flow framing; dropping the tab list leaves the strip as the only control and makes the current tab legible only through the strip's own highlight.


Imported from beads archie-core-xt6b · GitHub #1240 · type bug · priority P3 · created 2026-10-05

The Events page offers the same three destinations through two full navigation affordances stacked one above the other. The numbered step strip (`Capture → Map → Bind`, with counts) is a clickable `<ol>` of buttons, and directly beneath it the `Tabs` list repeats the same three panels as `Inspector | Mappings | Bindings`, with the same counts from the same `counts` source. Both drive the same `?tab=` query parameter through the same `show()`, so the page renders one control set twice under two different label vocabularies for the same three things. This is deliberate rather than a regression — `counts.ts` documents it ('The three-step strip and the tab chips both show one number per step'), and `EventsPage.vue` wires both to the one handler. It is filed because the result reads as a duplicated wizard, and because the two vocabularies (Capture/Map/Bind vs Inspector/Mappings/Bindings) name the same three panels differently in the same view. Deciding which one survives is a design call, not a code one: dropping the strip makes the chain the tab list and loses the numbered-flow framing; dropping the tab list leaves the strip as the only control and makes the current tab legible only through the strip's own highlight. --- _Imported from beads `archie-core-xt6b` · GitHub #1240 · type bug · priority P3 · created 2026-10-05_
sam added the lowbug labels 2026-10-27 13:41:18 +00:00
sam self-assigned this 2026-10-27 13:41:18 +00:00
sam referenced this issue from a commit 2026-11-08 12:44:04 +00:00
sam referenced this issue from a commit 2026-11-08 12:55:02 +00:00
sam added the deferred label 2026-11-15 17:26:14 +00:00
Sign in to join this conversation.
1 Participants
Notifications
Due Date
No due date set.
Dependencies

No dependencies set.

Reference: sam/archie#1664