Ensure office app check is bound to window class#12854
Merged
Merged
Conversation
See test results for failed build of commit e8d9245774 |
Collaborator
Author
|
System tests failure seems unrelated.
|
lukaszgo1
reviewed
Sep 16, 2021
| @@ -756,7 +756,9 @@ def _isUIAWindowHelper(self,hwnd): | |||
| canUseOlderInProcessApproach = bool(appModule.helperLocalBindingHandle) | |||
| isOfficeApp = appModule.productName.startswith(("Microsoft Office", "Microsoft Outlook")) | |||
Contributor
There was a problem hiding this comment.
Based on the log snipped I posted in #12852 I believe this fix would not be effective since fileUtils raises an error during execution of this line when trying to access productName of the LogonUI
Member
|
For now At very least a try accept RuntimeError is required around the call to appModule.productName I think. |
Collaborator
Author
|
Here's another incarnation of the regression: |
Collaborator
Author
|
I did a rewrite of my approach. In short, I really want to do the appModule.productName call only when the window class is wwg. IN the current situation of master, every call of _isUIAWindowHelper tried to get the appName |
michaelDCurran
approved these changes
Sep 17, 2021
Contributor
|
Is this planned for merge? |
Member
|
with try build:
|
5 tasks
michaelDCurran
pushed a commit
that referenced
this pull request
Sep 18, 2021
In #12854 the CanUseOlderInProcessApproach check was moved to run only when checking Office windows. However, it is also used to check whether to use UIA in Chromium. Description of how this pull request fixes the issue: Move this check before all usages, restoring the ability to use UIA in Chromium.
michaelDCurran
added a commit
that referenced
this pull request
Oct 26, 2021
This reverts commit e36efe4.
5 tasks
michaelDCurran
added a commit
that referenced
this pull request
Oct 27, 2021
We have tried to switch to using UI automation to access MS Word documents by default in NVDA 2021.3. However, there are still several issues remaining with our UIA support. Switching to UIA by default should be held back until these are addressed. Some of these include: • Support for math: Support mathML UIA custom property in MS Word #12946 • Reporting of line numbers: Requires UIA custom patterns support\ Over the last couple of months our UIA support has had a lot of fixes and improvements, mainly spured on by the apparent need to switch due to NVDA and MS Word not playing well together with the introduction of Modern Comments in MS Word build 13901. However, a work around has been found for #12982 now, making the swich less of a high priority. Description of how this pull request fixes the issue: Reverts #12859 Reverts #12854 Reverts #12770
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 #12852
Summary of the issue:
Secure desktops were severly broken in Alpha.
Description of how this pull request fixes the issue:
First check for the proper window class before applying logic to detect office apps and versions.
Testing strategy:
T.B.D. I think we need a signed build for this.
Known issues with pull request:
None known
Change log entries:
None needed
Code Review Checklist: