Hacktoberfest 2026: die Issues, die Maintainer für den Oktober markiert haben – offen und einsteigerfreundlich. Hacktoberfest-Issues durchsuchen

Voice dictation: layout shift after mic toggle puts Cancel under the cursor; second click discards dictation

Offen
  • Stimmt etwas nicht?
#4,843 0 Kommentare 1 Reaktion 0 zugewiesene Personen Auf GitHub ansehen

Dieses Issue hat noch niemand übernommen.

Bewertung

Schwierigkeit
4/5
Geschätzter Aufwand
3-5 Tage
Anfängerfreundlichkeit
55/100
Issue-Typ
Bug
Klarheit
Größtenteils klar
Aktivitätsstatus
Aktiv
Bereich
desktop, frontend

Rechercherichtung

Start by locating the chat composer and its voice dictation controls, then trace how the toolbar changes when dictation starts and how the Cancel and stop actions are wired. Reproduce the reported sequence with the pointer left in place; done when the second click stops dictation without discarding the transcript and the controls do not shift under the pointer.

Vom Indexierungsmodell aus dem Issue-Text verfasst.

Beschreibung

Short summary

Starting dictation from the composer's mic button shifts the layout and leaves the Cancel button under the pointer, right where the mic button just was. Clicking that spot again to stop dictation cancels it and discards everything dictated.

Affected version or release

1.1.29 (latest release at the time of filing)

Installation context

GitHub Copilot app on Windows 11 25H2 (build 26200, shown as "Windows 10.0.26200" in the table below). Affects the message composer in chat sessions (/chat).

Voice dictation settings (Settings > Voice dictation):

  • Push to talk: on
  • Shortcut: Ctrl+M
  • Input device: Line (2- ProFX)
  • Transcription model: nemotron-speech-streaming-en-0.6b-generic-cpu
What happened?

Each time I start dictation with the mic button, the layout shifts. Toggling on and then off at the same spot is the natural interaction, so I click the same location again to stop. After the shift, that location holds the Cancel button, so the click cancels the dictation and discards everything I dictated.

This happens with Push to talk on (see the settings above), when I start dictation from the mic button instead of the shortcut.

Steps to reproduce
  1. Open a chat session and place the mouse pointer over the mic button in the composer.
  2. Click the mic button to start voice dictation.
  3. Dictate a few sentences.
  4. Without moving the pointer, click the same spot again to stop dictation.

Actual: after step 2 the layout has shifted and the Cancel button is under the pointer. The click in step 4 activates Cancel and the dictated text is lost.

Expected behavior
  • Starting dictation does not move the control under the pointer, so toggling on and off in place works.
  • Clicking the same spot a second time stops dictation and keeps the transcript.
  • Cancel does not take the place of the control that was just clicked, and discarding a dictation is either confirmed or undoable.
Impact
  • Data loss: a single click discards all dictated input.
  • It is triggered by ordinary use (toggle on, then toggle off in place), not an unusual sequence.
  • The cost grows with dictation length, which discourages using dictation for longer prompts.
Suggested directions

Any one of these would address the problem:

  1. Keep the mic button in a fixed position and make it the stop control while dictating. Place Cancel away from that spot.
  2. Reserve space for the dictation controls so starting dictation does not reflow the composer toolbar.
  3. Add a safeguard for Cancel: ask for confirmation when a transcript exists, or offer Undo for a few seconds.
Additional context

Related: #4337 (closed) covers the composer controls after confirming a dictation with the checkmark.

Field Value
App version 1.1.29
OS Windows 10.0.26200
Theme GitHub
Path /chat
Tenure Week 16
Vorherrschende Sprache
Keine Sprachdaten
Sterne
2.2k
Forks
183
Keine gemergten PRs in 30 T.

Entwicklungsumgebung

Erste Schritte

  1. Lesen Sie das ganze Issue und danach den Beitragsleitfaden des Projekts.
  2. Schreiben Sie ins Issue, dass Sie es übernehmen — das erspart doppelte Arbeit.
  3. Forken Sie das Repository und arbeiten Sie in einem Branch.
  4. Öffnen Sie einen Pull Request, der die Issue-Nummer nennt.

Mehr aus github/app

Alle Issues in github/app

Ähnliche Issues

Weitere Issues zu Desktop Dev

Neue Issues direkt in Ihr Postfach

Eine kurze Übersicht über anfängerfreundliche GitHub-Issues.