Skip to content
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.

Sign up for GitHub

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

Jump to bottom

word problems 2013 #13008

Closed
fernando-jose-silva opened this issue Oct 30, 2021 · 4 comments · Fixed by #13009
Closed

word problems 2013 #13008

fernando-jose-silva opened this issue Oct 30, 2021 · 4 comments · Fixed by #13009
Milestone
2022.1

Comments

@fernando-jose-silva
Copy link

fernando-jose-silva commented Oct 30, 2021 •
edited
Loading

Steps to reproduce:

I have a friend's computer with problems.
This machine is with office 2013 and windows 10, I didn't install these 2 software.
I updated on this machine only nvda and the add-ons.
In several parts of the word, nvda doesn't say anything:
When we press alt inside word nvda doesn't announce the focus in the menu, and when we walk with tabe it doesn't read anything either.
This also occurred within outlook.
When we close the document without saving in the word question if we want to save the changes when walking with tabe again, nvda does not announce anything.
When opening the word on the first screen where you can choose the type of document to create nvda again is muted when walking with tabe or arrows.
I've already tested it with disabled add-ons and the problem continued.
I already ran the registry fix tool with and the error continues.
Nvda seems to work well in any other area of windows 10 and other programs.

Actual behavior:

nvda mute on some word screens

Expected behavior:

nvda read screens normally

System configuration

NVDA installed/portable/running from source:

instaled

NVDA version:

alfa 24160

Windows version:

10 10.0.19043.

Name and version of other software in use when reproducing the issue:

office 2013

Other information about your system:

Other questions

Does the issue still occur after restarting your computer?

yes

Have you tried any other versions of NVDA? If so, please report their behaviors.

no

If NVDA add-ons are disabled, is your problem still occurring?

yes

Does the issue still occur after you run the COM Registration Fixing Tool in NVDA's tools menu?

yes
log of the various screens where I noticed the error.
Sorry, there are so many errors that I couldn't selessionar only the point where it matters in the log, but I tried to turn on nvda at the time the error occurs to be relatively smaller.
exit word.txt
select word.txt
start word.txt
@fernando-jose-silva fernando-jose-silva changed the title estou com um computador de um amigo que está com um problema. word problems 2013 Oct 30, 2021
@lukaszgo1
Copy link
Contributor

I'm afraid I've caused this regression. Would you be able to:

  • Test with NVDA 2021.2 the problem should no longer exists
  • Assuming Word would work with 2021.2 could you please open Python console when focused in Word paste focus.appModule.appPath move with F6 to the output panel and paste its output here.

Many thanks and sorry for the inconvenience!

@fernando-jose-silva
Copy link
Author

Everything happened as you said, don't worry, we're here to try to help.
follows two files, 1 with the log of nvda 2021.2 with everything working.
Another file with piton console output.
wordok.txt
wordpiton.txt

@lukaszgo1 lukaszgo1 mentioned this issue Oct 30, 2021
Merged
5 tasks
@lukaszgo1
Copy link
Contributor

Please test with this build

@fernando-jose-silva
Copy link
Author

perfect, this build works correctly.
Thank you very much

seanbudd pushed a commit that referenced this issue Oct 31, 2021
@lukaszgo1
Use casefold when comparing file paths as os.path.commonPath fail…
205df17 
…s to handle paths from different disks (#13009)

PR #12943 improved code which retrieves version information for a given executable files placed in system32 under 64-bit versions of Windows. To do so it is necessary to check if path of the given binary starts with path of system32 directory for the current system. The recommended way to compare path's in a case insensitive way was os.pathcommonPath`, however it turns out it does not work when path's are from different drives.
In case of reporter of #13008 they had Office installed in a custom location probably on non system disk.

Description of how this pull request fixes the issue:
This PR simplifies the code to use standard str.casefold for comparisons.
@nvaccessAuto nvaccessAuto added this to the 2022.1 milestone Oct 31, 2021
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
None yet
Projects
None yet
Milestone
2022.1
3 participants
@lukaszgo1 @nvaccessAuto @fernando-jose-silva