Reported by jteh on 2010-05-26 22:41
When you move to a command console with object navigation, NVDA connects to this console, which allows this console to be reviewed. While this is useful, it presents three problems:
- When you move to the console using object navigation, the console is connected, but it isn't disconnected when you move away.
- This is because there is a becomeNavigatorObject event, but no event for the reverse.
- When object navigation causes NVDA to connect to a console, new text is reported for that console. New text should only be reported for focused consoles.
- Because only one console can be connected at a time, if a console is focused and the user moves to another console with object navigation, the user can no longer access the focused console. That is, new text is not read nor is caret navigation, backspace, etc.
While issues 1 and 2 can be fixed, it is probably not possible to solve issue 3, as this is due to a limitation of the implementation in Windows. Therefore, the only option may be to not connect to consoles for review.
Work around: To restore functionality to a focused console, move the navigator object back to the focused console.
This functionality was introduced in 4808ab6.
Reported by jteh on 2010-05-26 22:41
When you move to a command console with object navigation, NVDA connects to this console, which allows this console to be reviewed. While this is useful, it presents three problems:
While issues 1 and 2 can be fixed, it is probably not possible to solve issue 3, as this is due to a limitation of the implementation in Windows. Therefore, the only option may be to not connect to consoles for review.
Work around: To restore functionality to a focused console, move the navigator object back to the focused console.
This functionality was introduced in 4808ab6.