Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

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 #17253

Open
cary-rowen opened this issue Oct 5, 2024 · 6 comments
Labels
blocked/needs-external-fix p3 https://github.com/nvaccess/nvda/blob/master/projectDocs/issues/triage.md#priority triaged Has been triaged, issue is waiting for implementation.

Comments

@cary-rowen
Copy link
Contributor

cc @josephsl
May I kindly ask if other CJK users are experiencing the same issue?

Steps to reproduce:

  1. Install the Chinese language pack and enable Microsoft Pinyin IME on Windows 11.
  2. 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

@josephsl
Copy link
Collaborator

josephsl commented Oct 5, 2024 via email

@cary-rowen
Copy link
Contributor Author

Hi @j
Yes, Narrator's behavior is consistent with NVDA

@josephsl
Copy link
Collaborator

josephsl commented Oct 7, 2024 via email

@SaschaCowley SaschaCowley added blocked/needs-external-fix p3 https://github.com/nvaccess/nvda/blob/master/projectDocs/issues/triage.md#priority triaged Has been triaged, issue is waiting for implementation. labels Oct 7, 2024
@Adriani90
Copy link
Collaborator

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.

@msftedad
Copy link

msftedad commented Oct 15, 2024

@Adriani90 We have shared the issue with the engineering team and will keep you posted once we have more information to share.

@cary-rowen
Copy link
Contributor Author

Hi @msftedad

Can you please take a look at this issue as well?

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
blocked/needs-external-fix p3 https://github.com/nvaccess/nvda/blob/master/projectDocs/issues/triage.md#priority triaged Has been triaged, issue is waiting for implementation.
Projects
None yet
Development

No branches or pull requests

5 participants