Slash-command popup overlaps and bleeds through the branch/checkout repo dialog (z-index/layering bug)
- Lenguaje dominante
- Sin datos de lenguaje
- Estrellas
- 2.1k
- Forks
- 153
- Métricas de merge de PR
- Sin PR fusionados en 30 d
Descripción
### Summary
The slash-command (`/`) autocomplete popup renders **on top of and bleeds through** the "Pick a branch and checkout mode for each repo" dialog. Both layers are visible at the same time — the command list (`/inbox`, `/chronicle`, `/docx`, …) overlaps the repo rows and their branch dropdowns, making both unreadable. Looks like a z-index / layering (modal stacking) issue.
### Steps to reproduce
1. Open the "Pick a branch and checkout mode for each repo" screen (multi-repo branch selection).
2. With that dialog open, focus the prompt box and type `/` to trigger the slash-command menu.
3. The slash-command dropdown appears over the dialog, and the two layers visibly overlap / show through each other.
### Expected
The slash-command menu should either be suppressed while that dialog is open, or render in its own opaque layer that doesn't overlap/bleed through the repo+branch list.
### Actual
Both UIs render in the same space simultaneously — text from the repo list (e.g. "FE.MSecSCC", "WDATP.Infra.App.Tenant…", branch "main" dropdowns) shows through the slash-command popup, and vice versa.
### Environment
- GitHub Copilot desktop app, macOS (Apple Silicon).
### Additional context
Screenshot attached showing the overlap (repo/branch dialog behind, slash-command list in front, both visible through each other).
Guía de contribución
Línea de trabajo
Comienza reproduciendo el diálogo de selección de branch para varios repositorios y, después, abre el menú de slash-command desde el cuadro de entrada. Inspecciona las capas del diálogo y del popup para determinar si el menú debe suprimirse o renderizarse como una capa opaca que no se superponga; estará terminado cuando las filas de repositorios, los desplegables de branch y la lista de comandos sigan siendo legibles por separado.
Escrito por el modelo de indexación a partir del texto del issue.
Evaluación
- Área
- desktop, frontend
- Tipo de issue
- Error
- Dificultad
- 3/5
- Tiempo estimado
- 1-2 días
- Estado de actividad
- Tranquilo
- Claridad
- Bastante claro
- Aptitud para principiantes
- 48/100