Wide Home hover leaves the matching preview blank
Los mantenedores suelen responder en 1 día
Nadie ha tomado este issue todavía.
Evaluación
- Dificultad
- 3/5
- Tiempo estimado
- 1-2 días
- Aptitud para principiantes
- 82/100
- Tipo de issue
- Error
- Claridad
- Bien especificado
- Estado de actividad
- Activo
- Stack tecnológico
- go
- Área
- cli, testing-qa
Línea de trabajo
Start by running the seeded tmux test TestTUIE2E/hover_previews_the_match_under_the_pointer in ./internal/e2e. Trace selection ownership through app.homeHover, homeView.previewLine, and app.homeDetail in internal/tui3/home.go, then check the related unit coverage. Done means both hover scenarios render the hovered match and stale pointer events cannot override newer keyboard input.
Escrito por el modelo de indexación a partir del texto del issue.
Descripción
What happened
REGRESSION seen on commit 17ae56d34 (staging-20260921-17ae56d3496f) on 2026-09-21. Lane C, hover_previews_the_match_under_the_pointer, showed the search matches Seed Gamma, Seed Beta, and Seed Alpha, but the detail side stayed blank:
hovering `Seed Beta` did not move the card onto it
On v0.3.0 (9258f7052), the same focused subtest passed and previewed the hovered match. This is likely related to docs/changes/unreleased/1071-approvals-wheel.md, which says: Mouse hover no longer overrides a later keyboard selection. The most recent navigation method owns the single selection.
Replication
Deterministic (no model).
Run the seeded, focused tmux subtest; it needs no model key:
go test -tags e2e -count=1 -v ./internal/e2e -run '^TestTUIE2E/hover_previews_the_match_under_the_pointer$'
Today it exits nonzero with the failure quoted above while the right-hand card remains blank.
Field (real models).
No real-model run is needed: the seeded Home fixture reproduces in roughly 30 seconds and the v0.3.0 run of the same subtest is the control.
Where
The relevant hover and detail seams are app.homeHover, homeView.previewLine, and app.homeDetail in internal/tui3/home.go. The report identifies selection ownership as the likely area, but does not establish a code-level cause.
The fix
On wide Home, moving the pointer onto a search result must make that result the current selection and render its preview card. Keyboard input may subsequently take ownership, but an earlier keyboard selection must not suppress a newer hover.
Acceptance
- e2e: Through
TestTUIE2E/hover_previews_the_match_under_the_pointerin tmux, hoverSeed Beta, assert the detail card containsSeed Beta, is not blank, and exit 0. - e2e: Through the same seeded Home, select
Seed Alphaby keyboard and then hoverSeed Gamma; assert exactly one selection and a detail card containingSeed Gamma. - Unit: The selection-owner transition from keyboard to a newer pointer event changes
previewLineto the hovered row; a stale pointer event cannot override newer keyboard input. - The manual page
internal/manual/chat/home.mdquotes the hover-preview behavior, and the change entry'sinvalidatesnames the old belief that retaining keyboard ownership should suppress later hover.
Filed from the 2026-09-21 staging verification of 17ae56d34; the lane reports, frames and e2e logs are in the owner's handoff folder for this promotion.
- Lenguaje dominante
- Go
- Estrellas
- 115
- Forks
- 14
- Merge medio
- 9 h 38 min
- PR fusionados (30 d)
- 749
Preparar el entorno
Aún no hemos revisado los archivos de configuración de este proyecto. Empieza por su README y consulta nuestra guía para la primera contribución para los pasos generales.
Primeros pasos
- Lee el issue completo y luego la guía de contribución del proyecto.
- Comenta en el issue que vas a ocuparte — evita que dos personas hagan lo mismo.
- Haz un fork del repositorio y trabaja en una rama.
- Abre un pull request que haga referencia al número del issue.
Más de Agent-Field/CodeAF
-
area:chat feature
Dificultad 2/5 1-3 horas Aptitud para principiantes 88/100
Agent-Field/CodeAF#1510 ·
Los mantenedores suelen responder en 1 día
-
Dificultad 2/5 1-3 horas Aptitud para principiantes 82/100
Agent-Field/CodeAF#1489 ·
Los mantenedores suelen responder en 1 día
-
area:chat bug good first issue sev:papercut
Dificultad 2/5 1-3 horas Aptitud para principiantes 78/100
Agent-Field/CodeAF#1470 ·
Los mantenedores suelen responder en 1 día
-
area:chat bug good first issue sev:papercut
Dificultad 2/5 1-3 horas Aptitud para principiantes 85/100
Agent-Field/CodeAF#1469 ·
Los mantenedores suelen responder en 1 día
-
area:chat bug sev:papercut
Dificultad 2/5 1-3 horas Aptitud para principiantes 88/100
Agent-Field/CodeAF#1468 ·
Los mantenedores suelen responder en 1 día
Todos los issues de Agent-Field/CodeAF
Issues similares
-
bug needs triage
Dificultad 2/5 1-3 horas Aptitud para principiantes 78/100
Los mantenedores suelen responder en 1 día
-
bug P2 reliability
Dificultad 2/5 1-3 horas Aptitud para principiantes 88/100
afreidah/s3-orchestrator#1564 ·
Los mantenedores suelen responder en 1 día
-
Dificultad 2/5 1-3 horas Aptitud para principiantes 84/100
blinklabs-io/gouroboros#2577 ·
Los mantenedores suelen responder en 1 día
-
agentic-workflows
Dificultad 2/5 1-3 horas Aptitud para principiantes 68/100
Los mantenedores suelen responder en 1 día
-
Dificultad 2/5 1-3 horas Aptitud para principiantes 88/100
Los mantenedores suelen responder en 1 día