nvda icon indicating copy to clipboard operation
nvda copied to clipboard

NVDA does not remove "Expanded" state when there are no shortcuts available to an option in the Input gesture settings!

Open gauravahir28 opened this issue 10 months ago • 2 comments

Steps to reproduce:

  • Open Input gesture
  • open any category such as "Brows mode.
  • expand any available subcategory such as "Activates the current object in the document"
  • Delete all the assigned keyboard shortcuts of expanded subcategory.
  • observe the announcement of subcategory

Actual behavior:

NVDA says "Activates the current object in the document expanded " even when there are no keyboard shortcuts available!

Expected behavior:

NVDA should not convey the expanded state since the keyboard shortcuts are not available anymore!

NVDA logs, crash dumps and other attachments:

System configuration

NVDA installed/portable/running from source:

Installed

NVDA version:

NVDA 2024.1

Windows version:

Windows 11 23H2

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.

Not tried

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

gauravahir28 avatar Apr 16 '24 10:04 gauravahir28

Using Narrator and Windows Explorer:

  • Create a new folder named "Folder1"
  • In Folder1, create a new subfolder named Folder2
  • Go to the folder tree on the left (e.g. with F6 or shift+F6 until you reach the tree view) and select Folder1
  • Press rightArrow to expand Folder1
  • Press F6 to go to the folder's content and delete Folder2
  • Press shift+f6 to move back the focus to the tree view

Result: Folder1 is still reported as expanded, whereas it is now empty.

I cannot say if the same bug impacts all tree views or if these are two bugs with a distinct cause but leading to a similar result.

CyrilleB79 avatar Apr 16 '24 12:04 CyrilleB79

This likely needs to be fixed in Windows

seanbudd avatar Apr 23 '24 00:04 seanbudd