You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
NVDAObjects\__init__.py, around line 267 in the findBestAPIClass method: add a check to stop infinite recursion. Add a condition to break the recursion if no suitable API class can be found after a certain number of attempts. Or, before attempting a call to the next class's findBestAPIClass check if the class is the same as the one before
NVDAObjects\UIA\__init__.py, around line 1480 in the kwargsFromSuper method: Handle non-native elements correctly.
NVDAObjects\UIA\__init__.py, around line 1552 in the __init__ method: Add a check if the UIAElement is a native UIA element, and raise InvalidNVDAObject if it is not.
if not UIAHandler.handler.isNativeUIAElement(UIAElement):
raise InvalidNVDAObject("This UIA element is not native")
Steps to reproduce:
Open NVDA mouse settings, enable voicing everything, including the object under the mouse pointer.
Open a large channel in Unigram, where there is an HLS video. Turn on the video in Unigram;
Move the mouse cursor over this open video;
The bug is not always reproduced, but from time to time, today it is, tomorrow it is not.
Actual behavior:
Expected behavior:
NVDA crashes:
NVDA logs, crash dumps and other attachments:
System configuration
NVDA installed
NVDA version: 2024.4.1
Windows version: 10, 22H2 (OS build 19045.5247)
Name and version of other software in use when reproducing the issue: Unigram The last version in the store on December 19th
Other information about your system: Lenovo B590 20208, SSD, 8 GB RAM, Intel® Core™ i5-3230M CPU @ 2.60GHz
Other questions
Does the issue still occur after restarting your computer?
Sometimes yes, sometimes no. Floating problem.
Have you tried any other versions of NVDA? If so, please report their behaviors.
Yes, it is also reproduce: in other versions.
If NVDA add-ons are disabled, is your problem still occurring?
Yes, even without addons.
Does the issue still occur after you run the COM Registration Fixing Tool in NVDA's tools menu?
No, it didn't help. There is a problem.
The text was updated successfully, but these errors were encountered: