Artifact Viewer close icon can disappear after auto-opening in a background chat
Los mantenedores suelen responder en 1 día
Nadie ha tomado este issue todavía.
Evaluación
- Dificultad
- 4/5
- Tiempo estimado
- 3-5 días
- Aptitud para principiantes
- 45/100
- Tipo de issue
- Error
- Claridad
- Bastante claro
- Estado de actividad
- Activo
- Stack tecnológico
- typescript
Línea de trabajo
Empieza localizando la Artifact Viewer UI y su botón de cierre en la esquina superior derecha, y luego reproduce la secuencia de apertura automática del chat en segundo plano descrita en el issue. Traza el renderizado y el posicionamiento del visor al volver al chat; se considera terminado cuando la X de cierre sigue dibujándose visiblemente y se puede hacer clic en ella en ese escenario intermitente.
Escrito por el modelo de indexación a partir del texto del issue.
Descripción
Before filing
- I searched open and closed issues for duplicates.
- I reproduced this on the latest release.
- This is one bug, not several bundled together.
Closest existing issue
None found. I searched open and closed issues for artifact/preview/code viewer, close button/icon, invisible/hidden/disappearing, clipping, and background-chat auto-open behavior.
What's broken
After the Artifact Viewer appears automatically in a chat while that chat is in the background, returning to the chat can show the viewer without its top-right close X. The close button's hit target is still present and clickable, but the X icon is visually hidden behind or clipped by the viewer.
Steps to reproduce
- Launch Berd.
- Open a chat with prior history using
gpt-5.6-solthrough the Goose harness. - Start an agent turn that creates a document which causes the Artifact Viewer to auto-open.
- Navigate to another chat while that turn is running.
- After the Artifact Viewer has apparently auto-opened in the background chat, navigate back to that chat.
- Inspect the top-right corner of the Artifact Viewer.
This is intermittent; the sequence above describes the observed trigger rather than a guaranteed reproduction on every attempt.
What you expected to happen
The Artifact Viewer header should always display its close X in the top-right corner, including when the viewer auto-opened while its chat was in the background.
What actually happened
The X icon sometimes was not visible and appeared to be behind or clipped by the viewer. Clicking the location where the X should have been still closed the viewer, so the button remained interactive even though its icon was not painted visibly.
How often does it happen?
Intermittently — happens often but not always
Berd version
0.6.2
Operating system
macOS (Apple Silicon), macOS 26.5.2 (build 25F84)
Model and provider
gpt-5.6-sol through the Goose harness; underlying provider unknown. The symptom appears to be in the Artifact Viewer UI rather than model-specific behavior.
Relevant log output
no relevant log output
Screenshots, recordings, or other context
No screenshot or recording was captured while the intermittent state was visible. The important distinguishing detail is that the close button remains clickable at its normal position; only the X icon disappears visually.
- Lenguaje dominante
- TypeScript
- Estrellas
- 928
- Forks
- 121
- Merge medio
- 1 d 11 h
- PR fusionados (30 d)
- 71
Preparar el entorno
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 block/berd
-
Dificultad 2/5 1-3 horas Aptitud para principiantes 88/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
-
Dificultad 2/5 1-3 horas Aptitud para principiantes 78/100
Los mantenedores suelen responder en 1 día
-
Dificultad 2/5 1-3 horas Aptitud para principiantes 82/100
block/berd#166 · 1 comentario ·
Los mantenedores suelen responder en 1 día
-
Saving a custom provider does not set Goose's default provider/model, leaving Goose unavailableAbiertobug
Dificultad 2/5 1-3 horas Aptitud para principiantes 76/100
block/berd#140 · 1 comentario · 3 reacciones ·
Los mantenedores suelen responder en 1 día
Todos los issues de block/berd
Issues similares
-
priority: P2
Dificultad 2/5 1-3 horas Aptitud para principiantes 78/100
-
Dificultad 2/5 1-3 horas Aptitud para principiantes 65/100
prime-radiant-inc/evener#3291 ·
Los mantenedores suelen responder en 1 día
-
accessibility bug revealjs
Dificultad 2/5 1-3 horas Aptitud para principiantes 84/100
quarto-dev/quarto-cli#14961 ·
Los mantenedores suelen responder en 1 día
-
Dificultad 1/5 Menos de una hora Aptitud para principiantes 90/100
supabase/agent-skills#614 ·
-
Content
Dificultad 2/5 1-3 horas Aptitud para principiantes 68/100
RunestoneInteractive/rs#1559 · 1 comentario ·
Los mantenedores suelen responder en 2 días