Slash-command popup overlaps and bleeds through the branch/checkout repo dialog (z-index/layering bug)
- Vorherrschende Sprache
- Keine Sprachdaten
- Sterne
- 2.1k
- Forks
- 153
- PR-Merge-Kennzahlen
- Keine gemergten PRs in 30 T.
Beschreibung
### 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).
Beitragsleitfaden
Rechercherichtung
Beginne damit, den Dialog zur Branch-Auswahl für mehrere Repositories nachzustellen, und öffne anschließend das Slash-Command-Menü über das Eingabefeld. Untersuche die Layering-Ebenen des Dialogs und des Popups, um festzustellen, ob das Menü unterdrückt oder als opake, nicht überlappende Ebene gerendert werden sollte; fertig ist es, wenn die Repository-Zeilen, die Branch-Dropdowns und die Befehlsliste weiterhin separat lesbar bleiben.
Vom Indexierungsmodell aus dem Issue-Text verfasst.
Bewertung
- Bereich
- desktop, frontend
- Issue-Typ
- Bug
- Schwierigkeit
- 3/5
- Geschätzter Aufwand
- 1-2 Tage
- Aktivitätsstatus
- Ruhig
- Klarheit
- Größtenteils klar
- Anfängerfreundlichkeit
- 48/100