New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Outlook 2016: NVDA reads "Associated draft, no associated drafts" for every message #6219

Closed
bramd opened this Issue Jul 28, 2016 · 4 comments

Comments

Projects
None yet
4 participants
@bramd
Contributor

bramd commented Jul 28, 2016

Tested on latest Outlook 2016 from Office 365. @dkager reported that he has the same problem since yesterday with Office 365 as well.

Steps to reproduce:

  1. Open a mail folder (e.g. inbox)
  2. Arrow through the message list

Technical details

For every item in the message list, NVDA does the following:

  1. Use Outlooks' native COM interface to query some message attributes (read/unread, attachment, meeting request etc)
  2. Do a direct UIA query to loop over the children of the table row, filtered by controlType text

The "Associated draft" column has either been added very recently, or changed it's type to text and so is included in the loop in step 2.

Solution

I'm not that familiar with Outlook, but I guess this column sometimes contains real information about an associated draft, so just dropping it might not be the solution. We might drop it if it contains the "no associated drafts" value, but this is something that should be translated exactly in all languages and is to error prone. May be Microsoft can revert this change or we can come up with a better way to determine which columns to read.

@bramd

This comment has been minimized.

Show comment
Hide comment
@bramd

bramd Aug 1, 2016

Contributor

I've reverted to version 16.0.6965.2063. The problem is nonexistent in that version. I had a brief look at the changelogs, but didn't see any clue what changed to make this strange behavior happen.

Contributor

bramd commented Aug 1, 2016

I've reverted to version 16.0.6965.2063. The problem is nonexistent in that version. I had a brief look at the changelogs, but didn't see any clue what changed to make this strange behavior happen.

@bramd

This comment has been minimized.

Show comment
Hide comment
@bramd

bramd Aug 1, 2016

Contributor

I've reverted to version 16.0.6965.2063. The problem is nonexistent in that version. I had a brief look at the changelogs, but didn't see any clue what changed to make this strange behavior happen.

Contributor

bramd commented Aug 1, 2016

I've reverted to version 16.0.6965.2063. The problem is nonexistent in that version. I had a brief look at the changelogs, but didn't see any clue what changed to make this strange behavior happen.

@dkager

This comment has been minimized.

Show comment
Hide comment
@dkager

dkager Aug 2, 2016

Collaborator

For completeness' sake, I had the same issue with Outlook 2016 from Office 365 and the solution posted above worked to resolve it.

Collaborator

dkager commented Aug 2, 2016

For completeness' sake, I had the same issue with Outlook 2016 from Office 365 and the solution posted above worked to resolve it.

@leonardder

This comment has been minimized.

Show comment
Hide comment
@leonardder

leonardder Feb 22, 2018

Collaborator

I'm now on 16.0.9001.2102, and "No associated draft" is no longer exposed. Instead, the text node is empty.

Collaborator

leonardder commented Feb 22, 2018

I'm now on 16.0.9001.2102, and "No associated draft" is no longer exposed. Instead, the text node is empty.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment