I’ve found a reproducible issue with Wispr Flow dictation.
Manual paste into the app works normally with Ctrl+V.
However, when Wispr Flow tries to insert dictated text into the app, the app opens settings instead, as if Ctrl+, has been pressed.
I’ve tested this quite a bit:
Manual Ctrl+V into the app works
Ctrl+, opens the app settings
Wispr Flow dictation works in other apps
The issue happens whether I trigger Wispr with Ctrl+Down or Mouse Button 5, so it does not look like a shortcut conflict
Wispr’s “Paste last transcript” shortcut, Shift+Alt+Z, does nothing in the app
Wispr’s “Copy last transcript” shortcut, Shift+Alt+X, followed by manual Ctrl+V, works perfectly
So the transcript is being generated correctly, and the app accepts normal clipboard paste. The issue seems to be specifically with the way the app handles Wispr’s automated/simulated paste or injected keyboard input.
Could you check whether the app’s shortcut handling is intercepting synthetic Ctrl key events differently from physical keyboard events, especially while a text input field is focused?
A fix might be to make text fields prioritise standard paste handling over global shortcuts, or to avoid triggering Ctrl+, settings when the event comes from an automated paste/dictation tool.
I’ve found a reproducible issue with Wispr Flow dictation.
Manual paste into the app works normally with Ctrl+V.
However, when Wispr Flow tries to insert dictated text into the app, the app opens settings instead, as if Ctrl+, has been pressed.
I’ve tested this quite a bit:
Manual Ctrl+V into the app works
Ctrl+, opens the app settings
Wispr Flow dictation works in other apps
The issue happens whether I trigger Wispr with Ctrl+Down or Mouse Button 5, so it does not look like a shortcut conflict
Wispr’s “Paste last transcript” shortcut, Shift+Alt+Z, does nothing in the app
Wispr’s “Copy last transcript” shortcut, Shift+Alt+X, followed by manual Ctrl+V, works perfectly
So the transcript is being generated correctly, and the app accepts normal clipboard paste. The issue seems to be specifically with the way the app handles Wispr’s automated/simulated paste or injected keyboard input.
Could you check whether the app’s shortcut handling is intercepting synthetic Ctrl key events differently from physical keyboard events, especially while a text input field is focused?
A fix might be to make text fields prioritise standard paste handling over global shortcuts, or to avoid triggering Ctrl+, settings when the event comes from an automated paste/dictation tool.