-
-
Notifications
You must be signed in to change notification settings - Fork 784
Electron: Unable to report status bar #17339
Copy link
Copy link
Open
Labels
blocked/needs-external-fixp3https://github.com/nvaccess/nvda/blob/master/projectDocs/issues/triage.md#priorityhttps://github.com/nvaccess/nvda/blob/master/projectDocs/issues/triage.md#prioritytriagedHas been triaged, issue is waiting for implementation.Has been triaged, issue is waiting for implementation.
Metadata
Metadata
Assignees
Labels
blocked/needs-external-fixp3https://github.com/nvaccess/nvda/blob/master/projectDocs/issues/triage.md#priorityhttps://github.com/nvaccess/nvda/blob/master/projectDocs/issues/triage.md#prioritytriagedHas been triaged, issue is waiting for implementation.Has been triaged, issue is waiting for implementation.
Type
Fields
Give feedbackNo fields configured for issues without a type.
Follow-up of #17190
Because
objectFromPointcan't get the correct NVDAObject, all related functionality is broken.Steps to reproduce:
Actual behavior:
Report ‘No status bar’
Expected behavior:
Contents of the report status bar
NVDA logs, crash dumps and other attachments:
System configuration
NVDA installed/portable/running from source:
installed/portable/source
NVDA version:
alpha-34442,39c687c7 x86
Windows version:
Windows 11 22H2 (10.0.22621) workstation AMD64
Name and version of other software in use when reproducing the issue:
VS Code 1.94.2
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.
Yes
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