Ensure browse mode is used when reading Outlook messages with UI automation enabled #9188
Conversation
This file contains 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
…e is turned on by default when reading messages. Also handle the case where Outlook causes UIA to return mixedAttributes when searching for headings.
LeonarddeR
approved these changes
Jan 23, 2019
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:
Fall out from #8919
Summary of the issue:
With UI automation used for accessing Microsoft Word Documents when reading messages in Outlook, browse mode is not on by default.
This means that arrowing up and down the message can miss content a lot of the time if the content contains tables with more than one column.
Description of how this pull request fixes the issue:
Create an overlay class for Outlook word documents using UIA, that uses the treeInterceptor by default if the current message being viewed has been 'sent', I.e. it is being read, not composed.
This PR also catches a UIAMixedAttribute error sometimes seen when trying to quick navigate to headings in Outlook messages.
Testing performed:
Using Outlook 16.0.1231, Opened some messages from the inpox. Browse mdoe was correctly enabled for all of them. Also Created a new email and focused in the document. Browse mode was not enabled by default.
Known issues with pull request:
None.
Change log entry:
Bug fixes: