iOS keyboard cannot input chuck of words
See original GitHub issuefor example, when I want to use third-party keyboard such as clip
, to input a chuck of word (or with any auto complete function) on iOS, it will only input the first char.
Here, the keyboard should input ‘will xxxx’, but it only shows ‘w’
The English keyboard shipped with iOS dont have this kind of problem. Nearly all other third party kb have this problem.
Issue Analytics
- State:
- Created 8 years ago
- Comments:14 (4 by maintainers)
Top Results From Across the Web
iOS keyboard cannot input chuck of words · Issue #3690 ... - GitHub
for example, when I want to use third-party keyboard such as clip, to input a chuck of word (or with any auto complete...
Read more >The keyboard in mail will not allow the s… - Apple Community
With the last upgrade to iOS 13, I have not been able to type an email on my phone and the screen scroll...
Read more >8 essential keyboard tips every iPhone owner should know
Go to your Settings menu, then General, then scroll down and tap Keyboard. In the next screen you can ensure your preferences are...
Read more >How do I type using my keyboard on the iphone simulator?
Try trashing the iPhone Simulator preferences file. When my iPhone Simulator stopped responding to keystrokes, this fixed it. Quit the simulator.
Read more >Why doesn't the iPhone remember previously typed words?
iOS is supposed to learn your typing habits and it does a pretty good job most of the time. · 1) Reset your...
Read more >Top Related Medium Post
No results found
Top Related StackOverflow Question
No results found
Troubleshoot Live Code
Lightrun enables developers to add logs, metrics and snapshots to live code - no restarts or redeploys required.
Start FreeTop Related Reddit Thread
No results found
Top Related Hackernoon Post
No results found
Top Related Tweet
No results found
Top Related Dev.to Post
No results found
Top Related Hashnode Post
No results found
Top GitHub Comments
This is a issue that’s difficult if not impossible to solve with the fundamental approach currently taken by CodeMirror.
We are working on a rewrite (CodeMirror 6) that will probably address this issue, and we are currently raising money for this work: See the announcement for more information about the rewrite and a demo.
Note that CodeMirror 6 is by no means stable or usable in production, yet. It is highly unlikely that we pick up this issue for CodeMirror 5, though.
所以说什么时候可以解决这个问题?
so…when can fix this bug?