hotkey to move to next/previous error should not move NVDA's focus outside the editor

[Neurrone]

• VSCode Version: Code - Insiders 1.20.0-insider (f4ed56b, 2018-01-09T05:13:28.256Z)
• OS Version: Windows_NT x64 10.0.15063
• Extensions (2)

  Extension	Author (truncated)	Version
  vscode-markdownlint	Dav	0.12.0
  markdown-preview-enhanced	shd	0.3.2

Steps to Reproduce:

1. Create a file that has a lint error. The example I used was:

# Heading 1

* HTML
- LaTeX

## heading with trailing space  

2. Save the file as "test.md". With NVDA running and vscode-markdownlint, press f8 or shift+f8.

Expected result:

The error/warning is read. Keyboard focus stays in the editor, and I move to the offending line.

Actual result:

Keyboard focus exits the text area and lands on the text of the error. For e.g, NVDA would say

[markdownlint] MD004/ul-style: Unordered list style [Expected: asterisk; Actual: dash]

Focus is now on the text of the alert. I can quickly move to the edit area and press enter to enter forms mode, and focus is placed on the originating line.

It would be neat if the focus stayed inside the editor though to save this extra step.

[isidorn]

This works fine for me on macOS.
The focus stays in the editor and the error is read out.

@Neurrone can you still reproduce this with latest vscode?

[Neurrone]

@isidorn yup, this is still happening. If I press f8, my focus moves outside the textarea to where the error message is.