Open LittleStar-VIP opened 2 years ago
If you use nvda/B anywhere, you can get a loop. Sometimes its just several times, sometimes its endless. I seem to recall this has to do with the very basic way the command tries to read the would page. At one time there was proposal to remove this command, but I find it very useful as you can clearly hear when its repeating but its often the only way to have any idea how the screen of a very inaccessible bit of software is laid out.
Confirmed with this STR.
This seems to be caused by a bug in the explorer accessibility provider. When navigating through the tree it goes from the yes button back to the main instruction icon.
We could work around this by tracking the visited accessibility IDs.
This is also very related or even duplicate of #9413 and #6972. cc: @michaelDCurran
Hello! I can reproduce this strange behavior even in NVDA 2023.1 and even with latest alpha versions of NVDA on Windows 10 and on Windows 11. I didn't know about this issue and created a new one: #15219 . It was closed as a duplicate of this issue where i write this comment. And even in this issue I see a comment about possibly duplication or similarity. So, my question is straight and obvious: what is going on? Why some really serious issues are not fixed since previous major release? There were another issue related to losing focus when a new notification arrives (#14958), but it also was closed as a duplicate of another very old issue from 2021 release. I understand the fact that development team does not get money for their work and so they do their job motivated only by their enthusiasm. But why we see just support for new braille display models and few API changes in every new release? Where are major bug fixes? Where is migration to a newer Python version? In 2023 we still use 3.7 32-bit.
Steps to reproduce:
Actual behavior:
nvda repeating the message of the window again and again, I at least hear nvda repeating the message three times
Expected behavior:
nvda will only report everything once
System configuration
NVDA installed/portable/running from source:
portable
NVDA version:
nvda2022.1 beta3
Windows version:
win 10 home ed 21h1
Name and version of other software in use when reproducing the issue:
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.
the issue also existed in nvda 2021.3.5
If NVDA add-ons are disabled, is your problem still occurring?
my beta is a clean version without any addon
Does the issue still occur after you run the COM Registration Fixing Tool in NVDA's tools menu?