Accessibility bug: 1.26.0 broke dictation with Dragon

[deborahgu]

Describe the bug When using Dragon to dictate, after upgrading to 1.26.0, dictation became completely unavailable.

To Reproduce Steps to reproduce the behavior:

1. Install Dragon (in my case Dragon Pro individual 14 on Windows)
2. Open a file for editing and going to insert mode
3. Dictate some words (eg. "pound sign spacebar here is an English-language comment")
4. A wild selection of the characters in the words dictated, repeated an arbitrary number of times, appearing an arbitrary order.

Expected behavior I expect of the dictated phrase to appear in the editor.

Screenshots

Environment (please complete the following information):

• Extension (VsCodeVim) version: 1.26.0
• VSCode version: Version: 1.82.0 (user setup) Commit: 8b617bd08fd9e3fc94d14adb8d358b56e3f72314 Date: 2023-09-06T22:07:07.438Z Electron: 25.8.0 ElectronBuildId: 23503258 Chromium: 114.0.5735.289 Node.js: 18.15.0 V8: 11.4.183.29-electron.0 OS: Windows_NT x64 10.0.19045```
• OS: Windows 10

Additional context

I didn't spend time debugging this, and I did not test it with built-in Windows Speech Recognition; I can if you want me to. While the characters are spewing onto the screen at high speed, there might be some very fast intellisense pop-ups showing up, so I wondered if there was possibly some interaction happening there.

I know that Dragon isn't widely available, so I'm happy to screen share/help debug if I know where to look.

[rukai]

I observed the same issue with dictation via talon voice. In my case I'm running on linux.

[dpow-hrs]

I'm also having the same problem, also talon voice on Linux. https://talonvoice.com/

[deborahgu]

If it's happening in Talon as well that makes it a lot easier to test.

[xsrvmy]

Is this the same issue as the asian IME issue people have been reporting by any chance?

[neonpixii]

I can confirm i'm also having the same issue using Talon, and downgrading to the previous version of vscodevim fixed the issue.

[J-Fields]

Can someone please confirm whether this is fixed in v1.26.1?