Issue with creating or editing text in issues in mobile view #5690

GiteaMirror commented

@djonmayer commented on GitHub (Jul 7, 2020):

I have the same problem with mobile view. Testet in Firefox and Chrome on Android 8 / 9.

@djonmayer commented on GitHub (Jul 7, 2020): I have the same problem with mobile view. Testet in Firefox and Chrome on Android 8 / 9.

GiteaMirror commented

@sploders101 commented on GitHub (Aug 27, 2020):

Not sure how many testimonials are necessary, but I can confirm the same issue on Chrome for Android. It seems like it is potentially an issue with the rich text editing function of the box, that automatically applies markdown syntax & formatting as you type (this would modify your cursor location and could mess with soft-keyboards' auto-complete/word substitution). If this is too big of an issue, even a simple textarea would resolve the issue in the short-term, since it isn't usable as-is.

Thanks!

@sploders101 commented on GitHub (Aug 27, 2020): Not sure how many testimonials are necessary, but I can confirm the same issue on Chrome for Android. It seems like it is potentially an issue with the rich text editing function of the box, that automatically applies markdown syntax & formatting as you type (this would modify your cursor location and could mess with soft-keyboards' auto-complete/word substitution). If this is too big of an issue, even a simple textarea would resolve the issue in the short-term, since it isn't usable as-is. Thanks!

GiteaMirror commented

@ColinShorts commented on GitHub (Sep 9, 2020):

Switching to desktop view (android10/11 + chrome) seems to work around the issue, but that's not ideal on tiny screens.

@ColinShorts commented on GitHub (Sep 9, 2020): Switching to desktop view (android10/11 + chrome) seems to work around the issue, but that's not ideal on tiny screens.

GiteaMirror commented

@zeripath commented on GitHub (Sep 9, 2020):

There's a workaround: Press the last icon on the toolbar the black 🗅 folded over note. That will switch off the editor.

@zeripath commented on GitHub (Sep 9, 2020): There's a workaround: Press the last icon on the toolbar the black 🗅 folded over note. That will switch off the editor.

GiteaMirror commented

@stale[bot] commented on GitHub (Nov 9, 2020):

This issue has been automatically marked as stale because it has not had recent activity. I am here to help clear issues left open even if solved or waiting for more insight. This issue will be closed if no further activity occurs during the next 2 weeks. If the issue is still valid just add a comment to keep it alive. Thank you for your contributions.

@stale[bot] commented on GitHub (Nov 9, 2020): This issue has been automatically marked as stale because it has not had recent activity. I am here to help clear issues left open even if solved or waiting for more insight. This issue will be closed if no further activity occurs during the next 2 weeks. If the issue is still valid just add a comment to keep it alive. Thank you for your contributions.

GiteaMirror commented

@luwol03 commented on GitHub (Nov 14, 2020):

but the error is not fixed yet?

@luwol03 commented on GitHub (Nov 14, 2020): but the error is not fixed yet?

GiteaMirror commented

@corneliusroemer commented on GitHub (Dec 15, 2020):

This problem has now been known for at least 5mo - could you please switch off the editor by default on mobile browsers until this is fixed. It's provides a terrible first impression for anyone encountering Gitea on mobile for the first time. See #13132

@corneliusroemer commented on GitHub (Dec 15, 2020): This problem has now been known for at least 5mo - could you please switch off the editor by default on mobile browsers until this is fixed. It's provides a terrible first impression for anyone encountering Gitea on mobile for the first time. See #13132

GiteaMirror commented

@6543 commented on GitHub (Dec 16, 2020):

@MelBourbon can you confirm, #13333 solved this?

try.gitea.io ~~com~~ run with latest version to test agains :)

@6543 commented on GitHub (Dec 16, 2020): @MelBourbon can you confirm, #13333 solved this? try.gitea.io ~~com~~ run with latest version to test agains :)

GiteaMirror commented

@corneliusroemer commented on GitHub (Dec 16, 2020):

@6543 try.gitea.com doesn't work for me, do I need to have some sort of permission or anything else to access it?

@corneliusroemer commented on GitHub (Dec 16, 2020): @6543 try.gitea.com doesn't work for me, do I need to have some sort of permission or anything else to access it?

GiteaMirror commented

@jolheiser commented on GitHub (Dec 16, 2020):

It should be try.gitea.io

@jolheiser commented on GitHub (Dec 16, 2020): It should be [try.gitea.io](https://try.gitea.io/)

GiteaMirror commented

@sploders101 commented on GitHub (Dec 16, 2020):

try.gitea.io works for me now. Thank you!

@sploders101 commented on GitHub (Dec 16, 2020): try.gitea.io works for me now. Thank you!

GiteaMirror commented

@corneliusroemer commented on GitHub (Dec 16, 2020):

Yes, it works on mobile now - though autocorrect does not work on the body.

Body text is never automatically corrected by auto correct, in contrast to normal text fields. Presumably a remaining issue with EasyMDE on mobile.

@corneliusroemer commented on GitHub (Dec 16, 2020): Yes, it works on mobile now - though autocorrect does not work on the body. Body text is never automatically corrected by auto correct, in contrast to normal text fields. Presumably a remaining issue with EasyMDE on mobile.

GiteaMirror commented