nvaccess
After input composition ends in Windows 11 with Microsoft Pinyin IME, NVDA reports the name and value of the edit control instead of the committed candidate
cc @josephsl May I kindly ask if other CJK users are experiencing the same issue?
Steps to reproduce:
- Install the Chinese language pack and enable Microsoft Pinyin IME on Windows 11.
- Open Notepad and use Microsoft Pinyin to type Chinese text. For example, type 'luo' and then press the space key to commit the first candidate.
Actual behavior:
NVDA reports: 'Text Editor edit focused, multi line, 罗'
I believe the cause of this issue is that the modern keyboard in Windows 11 opens a candidate window that forcibly gains the system focus. After the candidate is committed, the window loses focus, and the edit control that receives the input regains focus.
Expected behavior:
NVDA should only report "罗", the committed candidate itself.
NVDA logs, crash dumps and other attachments:
System configuration
NVDA installed/portable/running from source:
installed, portable
NVDA version:
All versions
Windows version:
Windows11
Name and version of other software in use when reproducing the issue:
any editable control
Other information about your system:
None
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.
no version differences
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
Hi, try testing with Narrator and see if the problem is reproducible. If yes, then this is indeed caused by focus changes thanks to modern keyboard. Thanks.
From: Rowen @.> Sent: Saturday, October 5, 2024 5:28 AM To: nvaccess/nvda @.> Cc: Joseph Lee @.>; Mention @.> Subject: [nvaccess/nvda] After input composition ends in Windows 11 with Microsoft Pinyin IME, NVDA reports the name and value of the edit control instead of the committed candidate (Issue #17253)
cc @josephsl https://github.com/josephsl May I kindly ask if other CJK users are experiencing the same issue?
Steps to reproduce:
- Install the Chinese language pack and enable Microsoft Pinyin IME on Windows 11.
- Open Notepad and use Microsoft Pinyin to type Chinese text. For example, type 'luo' and then press the space key to commit the first candidate.
Actual behavior:
NVDA reports: 'Text Editor edit focused, multi line, 罗'
I believe the cause of this issue is that the modern keyboard in Windows 11 opens a candidate window that forcibly gains the system focus. After the candidate is committed, the window loses focus, and the edit control that receives the input regains focus.
Expected behavior:
NVDA should only report "罗", the committed candidate itself.
NVDA logs, crash dumps and other attachments:
System configuration
NVDA installed/portable/running from source:
installed, portable
NVDA version:
All versions
Windows version:
Windows11
Name and version of other software in use when reproducing the issue:
any editable control
Other information about your system:
None
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.
no version differences
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
— Reply to this email directly, view it on GitHub https://github.com/nvaccess/nvda/issues/17253 , or unsubscribe https://github.com/notifications/unsubscribe-auth/AB4AXEGUYANJCTF6CPIWBR3ZZ7EK5AVCNFSM6AAAAABPNIM7FOVHI2DSMVQWIX3LMV43ASLTON2WKOZSGU3DOOBZGI2TCNY . You are receiving this because you were mentioned.Message ID: @.***>
Hi, in this case, there’s nothing NVDA can really do as this is something to do with IME interface. Thanks.
cc: @msftedad can you please take this up with the development team? Since it seems it is related to modern keyboard and wrong focus changes. It impacts Narator as well.
@Adriani90 We have shared the issue with the engineering team and will keep you posted once we have more information to share.
NOTE: I do not work for Microsoft and the information I am about to provide should not be interpreted as a comment from Microsoft.
I reached out to Microsoft via enterprise support to troubleshoot this issue and https://github.com/nvaccess/nvda/discussions/17223, both of which are still present on Windows 11 in various forms. This issue is also present for Narrator. Microsoft has acknowledged the issues, but at this time they have determined that these bugs will need a workaround created for them on the NVDA side of things.
