Outlook: When selecting multiple messages in 2016, NVDA uses the read/unread characteristics of the first message in the selection

[PratikP1]

This is possibly related to #6009.

STR:

1. Open any inbox and find an unread message.
2. Start selection with either shift+up/down or control+up/down.
3. Repeat the first two steps after finding a read message.

I believe this message selection behavior carries over from Outlook 2013. I cannot confirm as I don't have Office 2013 installed on any of my units.

[feerrenrut]

In terms of desired behaviour here, what would be expected?
Would it be better not to report the read / unread status when multiple messages are selected? I think this would be less confusing, and the simplest way to address this.

[PratikP1]

In fact, I would argue the opposite. I’m often using the selection commands to clean up or organize old messages. It’s quicker and more efficient to keep track of messages as I’m selecting them without having to listen to the entire row.

[feerrenrut]

Ok in that case its a little more complicated. Lets try to define what the expected output should be in the following cases, the first two are easy. But what do you think about the others?

• Selecting 1 message, outputs the read status of just that message.
• Extending the current selection by 1 message, outputs the read status of the message added to the selection
• Removing 1 message from the current selection.
• Extending the current selection by several messages
• Removing several messages from the current selection.

[PratikP1]

Here is what I would propose for the three scenarios that seem complicated: · Removing 1 message from the current selection. o In this case, only the selection status of the message need be read when spacebar is pressed. Presumably when the user presses up or down arrow key in conjunction with shift or control, the read status has already been spoken. o The related issue I referenced in my original report comes into play. · Extending the current selection by several messages o Traversing through the list of messages while selecting those messages should identify the read/unread status along with the selected status—E.G., “Selected. Unread. From service@paypal.com<mailto:service@paypal.com> subject you’ve got money …” · Removing several messages from the current selection. o This should work no differently than my first suggestion.

[PratikP1]

Part of this issue has been resolved by #7949. Now, when selection occurs, the read/unread status of each message is reported correctly. We should further look at the discussion here though. For the sake of efficiency, the selection status should be reported first. (Related to #7296.)

[LeonarddeR]

I'm afraid this is quite complex due to how we interact with Outlook's object model. It seems we're always using the first item of the selection. This means that focussing one message and than selecting the message below does not work correctly, as the object model information will still reflect the first message in the selection. Selection from bottom to top should work, I believe.

[PratikP1]

With the latest changes incubating, read/unread status is read no matter whether the selection is started and we use down arrow for additional selection or the reverse. Now the only issue remains is determining which item is selected. This announcement comes after the info in the row is spoken. Interrupt ability is essential during this process.

[Adriani90]

I can reproduce this issue in NVDA 2019.1 and Outlook 2016 as follows:

1. Open Outlook
2. Focus an unread message in the message list (make sure NVDA reports unread)
3. Hold down shift key and start selecting messages with down arrow
   Actual: NVDA will report "unread" for all messages you select regardless of their real tag. Messages which are read are also reported as "unread"
   Expected: NVDA should report "unread" only for messages which are unread.

cc: @CyrilleB79, @Novalis7747, @josephsl

[Novalis7747]

I can reproduce this with Office 365 and NVDA 2019.1. From: Adriani90 <notifications@github.com> Sent: Montag, 1. April 2019 18:26 To: nvaccess/nvda <nvda@noreply.github.com> Cc: Ralf Kefferpuetz <novalis7747@live.com>; Mention <mention@noreply.github.com> Subject: Re: [nvaccess/nvda] Outlook: When selecting multiple messages in 2016, NVDA uses the read/unread characteristics of the first message in the selection (#6819) I can reproduce this issue in NVDA 2019.1 and Outlook 2016 as follows: 1. Open Outlook 2. Focus an unread message in the message list (make sure NVDA reports unread) 3. Hold down shift key and start selecting messages with down arrow Actual: NVDA will report "unread" for all messages you select regardless of their real tag. Messages which are read are also reported as "unread" Expected: NVDA should report "unread" only for messages which are unread. cc: @CyrilleB79<https://apc01.safelinks.protection.outlook.com/?url=https%3A%2F%2Fgithub.com%2FCyrilleB79&data=02%7C01%7C%7C7a2f72095f99472bff8f08d6b6beccfc%7C84df9e7fe9f640afb435aaaaaaaaaaaa%7C1%7C0%7C636897327926369285&sdata=4T23CNSl7Spye%2FIcNrCyn6nJOcGf4HTzfBLTsPHmuOU%3D&reserved=0>, @Novalis7747<https://apc01.safelinks.protection.outlook.com/?url=https%3A%2F%2Fgithub.com%2FNovalis7747&data=02%7C01%7C%7C7a2f72095f99472bff8f08d6b6beccfc%7C84df9e7fe9f640afb435aaaaaaaaaaaa%7C1%7C0%7C636897327926379290&sdata=XBqez1Sz4OAzB96DwoIn4%2B1BWe0n7nEFtUn9J0MdxPc%3D&reserved=0>, @josephsl<https://apc01.safelinks.protection.outlook.com/?url=https%3A%2F%2Fgithub.com%2Fjosephsl&data=02%7C01%7C%7C7a2f72095f99472bff8f08d6b6beccfc%7C84df9e7fe9f640afb435aaaaaaaaaaaa%7C1%7C0%7C636897327926389300&sdata=F%2FuZlShOhyB5NF6oy7ARXFfdgffCCM4C6W%2Fu%2F2eoqAo%3D&reserved=0> — You are receiving this because you were mentioned. Reply to this email directly, view it on GitHub<https://apc01.safelinks.protection.outlook.com/?url=https%3A%2F%2Fgithub.com%2Fnvaccess%2Fnvda%2Fissues%2F6819%23issuecomment-478649146&data=02%7C01%7C%7C7a2f72095f99472bff8f08d6b6beccfc%7C84df9e7fe9f640afb435aaaaaaaaaaaa%7C1%7C0%7C636897327926399305&sdata=VY7dNG%2FgDyKLvznQk9RmrnT6%2F4NrDVdsHPP4Ht9Rsto%3D&reserved=0>, or mute the thread<https://apc01.safelinks.protection.outlook.com/?url=https%3A%2F%2Fgithub.com%2Fnotifications%2Funsubscribe-auth%2FAffwnOeDpW6_wmAcThNc_pfsFjBrViqyks5vcjM0gaJpZM4LwyJi&data=02%7C01%7C%7C7a2f72095f99472bff8f08d6b6beccfc%7C84df9e7fe9f640afb435aaaaaaaaaaaa%7C1%7C0%7C636897327926409322&sdata=N54l1mRAEPctFOQhfQpcP%2BVfS35WL80Jl%2FSZuRM86Xo%3D&reserved=0>.