Hi all

@Paul,
Why don't you open the ticket yourself? You have all the skills to do it. The technical description that you made of this issue is more than correct with a detailed way to reproduce the issue. And your English, as written in your messages, is also correct.
If something else is blocking you, just let us know and we can help, here or in GitHub once the ticket is opened.

@Gene:
A common consequence of an error occurring in the GUI is that the GUI may not work as expected in the future. For example if you add the following steps to Paul's steps:
- close the input gesture window
- open a new input gesture window
- open a new input gesture window
- open a new input gesture window
- open a new input gesture window
- open a new input gesture window
- open a new input gesture window

You will end up with many input gesture window opened, whereas the standard behaviour of NVDA is to re-focus the input gesture window if it is already opened in the background.

Cheers,

Cyrille




On Wed, Jun 29, 2022 at 04:08 AM, bering.p wrote:

Hi,
I think I discovered an NVDA bug using the "input gestures" dialog.
I would like you to confirm this and if so, that one of you accustomed to the ticket, make one.
I consistently reproduce it with NVDA 2022.1 and 2022.2 beta and all add-ons disabled.
To do this:
- launch nvda with add-ons disabled,
- display the "Input gestures" dialog,
- press "end" to select the last category,
- go up two categories to select the "mouse" category,
- then "shift+tab" to position the cursor in the "filter" field,
- type "z".

A series of errors appear in the log.
Then, each time the "Input gestures" dialog is restarted, a new error is entered in the log.
Thank you.
Best regards.
Paul.

-- 

Paul.