NVDA and detection of message state - is selected/is not selected in Microsoft Outlook
Hi,
Is it possible to detect message state in NS Outlook so I would know, which messages are selected and not?
Steps to reproduce:
- Open MS Outlook
- Go to Inbox or anyother folder where are messages you wish to move them.
- Try to select messages with simular commands which have been used in windows explorer. so hold ctrl/shift key and press arrow keys and than spacebar to select appropriate message.
Expected behavior:
NVDA should report if message was selected or not. I expect same behaviour as in Windows Explorer.
Actual behavior:
NVDA does not detect message state.
System configuration:
NVDA version: updated next snapshots
NVDA Installed or portable: Installed
Other information:
Windows version:
Windows 10 Version 1607 Build 14393.1358 and ver 1703
MS Office 2016
Other questions:
Does the issue still occur after restarting your PC? Yes.
Have you tried any other versions of NVDA? Yes
Please list them and the result
- 2017.1
- 2017.2
same result
There was some related discussion of selection in Outlook message list in #6819.
Every day I use Microsoft Outlook and false information about the status of the message (new, read, attached) is very uncomfortable. I think there should be no additional messages with the shift key pressed.
This is still reproducible in NVDA 2019.1.1. cc: @leonardder, @michaelDCurran
To be clear, the user talks here about the command ctrl+up and down arrow key to focus the message, followed by ctrl+space bar to select it. This allows non contiguous selection of messages in Outlook. This works as expected in Outlook 365 build 2409 when pressing ctrl+space bar for the first time to select a message. NVDA reports "selected". However, when pressing ctrl+space bar again, to unselect it, NVDA does not report anything. NVDA is also silent for all subsequent ctrl+space presses unless you're moving the focus back and forth via ctrl+up and down arrow and trying again.
UIA doesn't seem to make any difference.
@ABuffEr do you know whether this would need a fix by Microsoft, or whether this could be fixed in NVDA?
Hi @Adriani90, I don't use Outlook anymore, and I'm unable to setup it for testing at the moment. To answer your question, anyway, inspection of states from developer info of variously selected message could be sufficient, I think.