When starting a search or a replacement, JAWS does not deactivate the virtual cursor if we have form mode activation set to manual.

[kastwey]

Steps to reproduce:

1. Open a file with VS Code.
2. Run JAWS.
3. In VS Code, press Insert+F6 to open the JAWS Settings center.
4. Type "Forms mode" in the search text field, and find the "form mode" result.
5. Disable automatic activation of forms mode and set it to manual.
6. Save the changes and close the settings center.
7. Now, in VS Code, press Ctrl+F to go to search.

Expected behaviour:

The JAWS virtual cursor should remain disabled, allowing us to use the keys to type in the search edit box.

Current behaviour:

The virtual cursor is activated, and when we type, we are executing HTML keyboard shortcuts instead of typing in the edit box. We have to press Enter to activate forms mode (equivalent to deactivating the virtual cursor) and then we can type in the edit box.

As I mentioned above, this is not due to the form mode activation type configuration, since in previous versions this error did not occur.

If I have some time, I will compile old versions of VS Code until I find the point of regression.

[kastwey]

cc @meganrogge @isidorn

[meganrogge]

Thanks for the issue, it would be great if you could please bisect to the point of the regression as I do not have a windows computer at the moment.

Please run the following command to find the build. It will start previous releases of VS Code insiders to see where the regression was introduced:

• npx @vscode/vscode-bisect@latest
• follow the instructions until you found the offending build
• report back the commit range in this issue

Thanks!

/label info-needed