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

iOS compatibility issue on iPad pro, and CKJ input method issues #3157

Closed
geyang opened this issue Dec 4, 2016 · 2 comments
Closed

iOS compatibility issue on iPad pro, and CKJ input method issues #3157

geyang opened this issue Dec 4, 2016 · 2 comments
Labels

Comments

@geyang
Copy link

geyang commented Dec 4, 2016

Accidentally submitted this issue on my iPad Pro when switching between input methods : P

This issue references #37 which dates all the way back to 2011.

Now with iPad getting bigger and more productivity oriented, there are more users trying to use it instead of a PC for productivity work. Currently, ACE editor's cursor movement does not on an iPad with an external keyboard. IME support is also poor.

IME issue:
Start typing in CKJ, now with a few alphabets typed, press backspace. Expected behavior is for the alphabets in the active IME session to get deleted one by one. However, text before the IME input box gets deleted instead. This only happens on mobile.

Cursor issue:
On mobile, when you use the arrow key of an attacked keyboard to move the cursor, the cursor does not move. This has been mentioned in #37

Cursor under vim:
Cursor under vim mode on mobile works well. Except that keyrepeat does not cause the cursor to move multiple characters, but instead gets stuck if you keep the key pressed down.

If these issues require a concerted effort, maybe we can make some plans on addressing them together.

@geyang geyang changed the title iOS com iOS compatibility issue on iPad pro, and CKJ input method issues Dec 4, 2016
@nightwing nightwing added the ime label Jan 30, 2017
@xiaohulu
Copy link

xiaohulu commented Aug 2, 2017

+1

@nightwing
Copy link
Member

The keyboard issue is fixed by #3172.
The other issues are still open.

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

No branches or pull requests

3 participants