Suppress reporting of tables when reading emails in Outlook using UIA#12820
Merged
Conversation
…uppressing reporting when reading emails.
Contributor
|
It seems that for Word documents (legacy), it is checked that the table has borders. |
Member
Author
|
No, UIA does not expose border information sadly.
|
seanbudd
reviewed
Sep 9, 2021
seanbudd
approved these changes
Sep 9, 2021
Member
Author
|
Oh, that was an out of date comment. Further discussion on #11430 chose
against checking number of rows and columns.
|
See test results for failed build of commit eecfa50b7b |
michaelDCurran
added a commit
that referenced
this pull request
Sep 16, 2021
9 tasks
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Link to issue number:
Fixes #11430
Summary of the issue:
Microsoft Outlook uses a Microsoft word document control to present emails when both reading and composing. NVDA is in the process of switching to using UI Automation to access Microsoft Word document controls due to major performance advantages, and also due to Microsoft no longer maintaining the Office object model.
However, in the UI automation implementation exposed by MS Word document controls, it is impossible to identify the difference between a data table and a layout table. Thus, NVDa reports all layout tables when reading, which is extremely annoying, as the majority of HTML emails use many nested layout tables.
Description of how this pull request fixes the issue:
Tables are now classed as layout tables in MS Word document controls if the app is Outlook, and the table is read-only (Outlook is in message reading view).
Being marked as a layout table means that by default the table will not be reported, however the user can still turn on the Include Layout Tables option in NVDA's browse mode settings temporarily if there is a genuine data table they need to have reported.
Testing strategy:
With use UIA in MS Word controls enabled in NVDA's advanced settings:
Known issues with pull request:
All table reporting will be suppressed when reading emails in Outlook, even data tables. However, waying up the extreme annoyance of having layout tables read verses not reporting some very rare data tables (where the user can manually still enforce reporting by turning on includeLayoutTables) I think this is okay.
Though it would be much better if Outlook exposed layout tables in an identifiable way, such as not supporting the UI Automation Table Pattern for layout tables.
Change log entries:
Bug fixes:
Code Review Checklist: