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

lines jumping around since 5.21 mobile #4493

Open
renlok opened this issue Jan 15, 2017 · 5 comments
Open

lines jumping around since 5.21 mobile #4493

renlok opened this issue Jan 15, 2017 · 5 comments

Comments

@renlok
Copy link

renlok commented Jan 15, 2017

Since upgrading from 5.17 I have been having issues with mobile where lines will be moved to the line above.

For example if you try to type out

hello
world

you will just get
helloworld
I tried different versions and this seems to only effect 5.22 and 5.21, 5.20 and older seem to be fine

@edemaine
Copy link
Contributor

edemaine commented Jan 17, 2017

Unfortunately, I can confirm that this issue remains on 5.22.0. Pressing enter goes to the next line, but then typing seems to have the effect of hitting backspace first, erasing that newline character. This behavior didn't occur on 5.14.2 (testing on the same Android device, same setup, one day apart). Pressing enter twice and then typing has the desired effect of entering a single newline.

For what it's worth, with Enter bound to newlineAndIndentContinueMarkdownList, the same error occurs, except when actually continuing a Markdown list; then enter and typing behaves as expected.

@edemaine
Copy link
Contributor

edemaine commented Mar 8, 2017

I'm pretty sure that the latest patch (bad02ce) fixed this issue. At least, I don't seem to be able to reproduce it on Android, on master in say demo/marker.html.

@marijnh
Copy link
Member

marijnh commented Mar 8, 2017

That's interesting. I can't explain how that patch could fix this, though. @Renlock, can you confirm?

@renlok
Copy link
Author

renlok commented Feb 17, 2018

Still broken in 5.34

@adrianheine
Copy link
Contributor

This is one of many issues which are difficult to solve with the fundamental approach currently taken by CodeMirror.

We are working on a rewrite (CodeMirror 6) that will overhaul input handling and should 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.

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

No branches or pull requests

4 participants