Inconsistent information displayed in Input Gestures after editing keystrokes

[Qchristensen]

Steps to reproduce:

(In brief, allocate a browse mode only gesture, then try to edit it somewhere Browse mode is not available).

1. Open any web page, in Browse mode
2. Open Input Getures (NVDA+n, p, n)
3. Press shift+tab then type "Math" to filter to the text "Math" (assuming you haven't added keystrokes for moving to next and previous math equations. If you have pick another Browse mode function like "Next same style Paragraph" or something else with an unassigned gesture).
4. Select one of the Browse mode functions without a keystroke.
5. Press alt+a and assign a gesture (any gesture, as long as you won't accidentally press it)
6. Press ENTER to allocate the gesture for the current layout and enter again to close the dialog.
7. Press alt+d to go to the web page's address bar (not somewhere browse mode works)
8. Open Input Gestures (NVDA+n, p, n)
9. Filter to "Math" (or whatever you used last time)
10. Read through the results.

Actual behavior:

At step 10, note that the command you assigned to jump to next Math function exists, but not the corresponding jump to previous math function you didn't allocate a gesture to.

Expected behavior:

The input gestures dialog should be consistent with the gestures displayed. In the existing (as at 2024.2) setup, the contents of the dialog are context dependent - IE: Browse mode only gestures are only displayed when NVDA was in Browse mode prior to opening the dialog. Personally I favour implementing #10775 (Input Gestures: Allow Configuration of all Gestures via the Input Gestures Dialog irrespective of Context), and if implementing that would automatically fix this, then I'm in favour of prioritising that over this issue.

I'm not sure what other situations might trigger this issue, but if the result is sometimes displaying gestures when they otherwise shouldn't be, I don't think the impact is high.

NVDA logs, crash dumps and other attachments:

System configuration

NVDA installed/portable/running from source:

NVDA version:

NVDA 2024.2 Installed

Windows version:

Windows 11 (64-bit) Version: 23H2, Build: 22631.3737

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?

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

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

No add-ons installed

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