Steps to reproduce:
for (int i = 1; i <= 10; i++)
{
printf("%d\n", i);
}
- Use the above code to output an integer from 1 to 10 in the VS Code terminal
- Set "Paragraph style" to "Single line break" or "Multi line break" in NVDA settings Panel;
- Press Ctrl+` to switch to the VS Code terminal;
- Press Ctrl+UpArrow/DownArrow;
Actual behavior:
After a few seconds of silence NVDA reports "No previous paragraph","No next paragraph".
Expected behavior:
NVDA should be able to navigate the output within the terminal. Like setting the "Paragraph style" to "Handled by application".
NVDA logs, crash dumps and other attachments:
System configuration
NVDA installed/portable/running from source:
Installed
NVDA version:
alpha-27446
Windows version:
Windows 10 22H2 (AMD64) build 19045.2364
Name and version of other software in use when reproducing the issue:
Vs Code 1.74.2
Other information about your system:
None
Other questions
Does the issue still occur after restarting your computer?
Yes
Have you tried any other versions of NVDA? If so, please report their behaviors.
None
If NVDA add-ons are disabled, is your problem still occurring?
Yes
Does the issue still occur after you run the COM Registration Fixing Tool in NVDA's tools menu?
Yes
Steps to reproduce:
Actual behavior:
After a few seconds of silence NVDA reports "No previous paragraph","No next paragraph".
Expected behavior:
NVDA should be able to navigate the output within the terminal. Like setting the "Paragraph style" to "Handled by application".
NVDA logs, crash dumps and other attachments:
System configuration
NVDA installed/portable/running from source:
Installed
NVDA version:
alpha-27446
Windows version:
Windows 10 22H2 (AMD64) build 19045.2364
Name and version of other software in use when reproducing the issue:
Vs Code 1.74.2
Other information about your system:
None
Other questions
Does the issue still occur after restarting your computer?
Yes
Have you tried any other versions of NVDA? If so, please report their behaviors.
None
If NVDA add-ons are disabled, is your problem still occurring?
Yes
Does the issue still occur after you run the COM Registration Fixing Tool in NVDA's tools menu?
Yes