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

Already on GitHub? Sign in to your account

Caret move not responding after input method candidate window closed #4145

Closed
nvaccessAuto opened this Issue May 17, 2014 · 5 comments

Comments

Projects
None yet
3 participants

Reported by nishimotz on 2014-05-17 04:21
setup:

  • Windows 8.1 Update (64bit, User Interface Language: English, enabled Japanese Microsoft IME and SAPI5 Japanese Haruka Desktop TTS)
  • NVDA 2014.2rc1 (speak typed characters: enabled, automatically report all available candidates: disabled)
  • notepad.exe

procedure:

  • start notepad application
  • type "abc" with English keyboard array. each characters are reported as typed.
  • windows+space: switch to Japanese IME
  • application key, then upper arrow key twice: if the item is "Close IME", press Escape to cancel. if it is "Open IME", press Enter.
  • type "kawa" (reported 'k', 'ka', 'w', 'wa')
  • space key (reported 'kawa')
  • space key (opened candidate window and reported second candidate)
  • enter key (second candidate is selected.): expected to announce the selected candidate 'kawa'. actually only 'candidate' is announced.
  • left arrow key or right arrow key: expected to report the character at the caret. actually nothing reported.
  • alt key twice: now left or right arrow keys work normally.

As far as we know, Braille display is also not properly updated after the open-close of candidate window (although Japanese Braille is only supported by Japanese forked version of NVDA).

Reverting api.py line 96 regarding #3873 (setFocusObject incorrectly caches container property as parent) seems to resolve the issues as far as we investigated.

Comment 2 by vgjh2005 on 2014-08-14 08:57
Hi:
This problem is caused in Chinese input method. I also hope that can be solve as soon as possible.
Thanks

Comment 3 by surfer0627 on 2014-08-26 01:32
Thanks nishimotz.

This ticket provides a more specific description than the previous one I have filed #2792.

I also hope that this case could be fixed in the near future.

Comment 4 by jteh (in reply to comment 3) on 2014-08-26 02:41
Replying to surfer0627:

This ticket provides a more specific description than the previous one I have filed #2792.

While #2792 results in the same problem, I think it's actually a different cause, as @nishimotz noted that the issue he is reporting was caused by a fairly recent change (01e2298), whereas #2792 was filed long before that.

Comment 5 by surfer0627 on 2014-08-26 06:19
Thanks Jamie's clarification.

@michaelDCurran michaelDCurran added a commit that referenced this issue Dec 10, 2015

@michaelDCurran michaelDCurran Support for the Modern IME candidate list UI (used in Windows 8 and a…
…bove for such input methods as Chinese Simplified Microsoft Pinyin).


Fixes #4145
Fixes #4011
2370692

@michaelDCurran michaelDCurran added a commit that referenced this issue Dec 10, 2015

@michaelDCurran michaelDCurran Support for the Modern IME candidate list UI (used in Windows 8 and a…
…bove for such input methods as Chinese Simplified Microsoft Pinyin).


Fixes #4145
Fixes #4011
dbbaace
Contributor

michaelDCurran commented Dec 10, 2015

Fix implemented as part of #4011

@michaelDCurran michaelDCurran added a commit that referenced this issue Jan 6, 2016

@michaelDCurran michaelDCurran Revert "Support for the Modern IME candidate list UI (used in Windows…
… 8 and above for such input methods as Chinese Simplified Microsoft Pinyin)."

Unincubates #4011

This reverts commit dbbaace.

Note that this still incubates #4145
4e93c3c

@jcsteh jcsteh added this to the 2016.1 milestone Jan 6, 2016

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment