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

Rich text input fields are broken when using Google Gboard Keyboard on Android #11352

Closed
1 of 7 tasks
antonsmetanin opened this issue May 9, 2020 · 11 comments
Closed
1 of 7 tasks
Labels
issue/confirmed Issue has been reviewed and confirmed to be present or accepted to be implemented outdated/theme/markdown topic/mobile type/upstream This is an issue in one of Gitea's dependencies and should be reported there

Comments

@antonsmetanin
Copy link

  • Gitea version (or commit ref): 1.11.4

  • Git version: N/A

  • Operating system: N/A

  • Database (use [x]): N/A

    • PostgreSQL
    • MySQL
    • MSSQL
    • SQLite
  • Can you reproduce the bug at https://try.gitea.io:

    • Yes (any issue page)
    • No
    • Not relevant
  • Log gist:

  • Android version: 6.0.1

  • Chrome version: 77.0.3865.92

  • Gboard version: 8.6.10.266015648-release-armeabi-v7a

Description

Rich text input field used to write issue comments (and probably in other places, too) is broken when using Gboard. The entered text keeps getting copied over and over whenever you're typing new characters, deleting the old ones, or even just tapping somewhere else. This makes Gitea web interface pretty much unusable unless you switch to another keyboard.

Screenshots

20200509_142543

@silverwind
Copy link
Member

SimpleMDE has a lot of issues, #10729 will eventually fix it.

@zeripath
Copy link
Contributor

zeripath commented May 9, 2020

Press the last button in the toolbar - the plain black file button - it will turn off simple mde and revert to a simple textare

@antonsmetanin
Copy link
Author

@zeripath Thanks, this helped. Still, I've read the linked issue, and I agree that SimpleMDE probably needs to be replaced.

@stale
Copy link

stale bot commented Jul 11, 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 stale bot added the issue/stale label Jul 11, 2020
@lunny lunny added type/upstream This is an issue in one of Gitea's dependencies and should be reported there issue/confirmed Issue has been reviewed and confirmed to be present or accepted to be implemented labels Jul 12, 2020
@stale stale bot removed the issue/stale label Jul 12, 2020
@jswolf19
Copy link

jswolf19 commented Jul 15, 2020

I get a similar issue when using the file editor to create a new file. I'm using Windows 10's Japanese IME in Firefox, Gitea 1.12.2. The text becomes doubled for certain inputs. While Japanese doesn't seem to get duplicated, alphanumeric strings do.

Editing issues and pull requests does not have the same problem for me.

@TheEvilSkeleton
Copy link

I get the same issue on Bromite (browser) and OpenBoard (keyboard).

@zeripath
Copy link
Contributor

zeripath commented Aug 6, 2020

on the toolbar there is a page icon in the far right click that to make SimpleMDE disappear and return to a simple textarea.

Screenshot from 2020-08-06 18-07-31

@corneliusroemer
Copy link

Why is the simple textarea not the default on mobile if SimpleMDE is so buggy on mobile?

@jolheiser
Copy link
Member

Why is the simple textarea not the default on mobile if SimpleMDE is so buggy on mobile?

There has not been a PR to introduce such a thing. You are welcome to make one. 🙂

As you've noted in other issues, the long-term fix will ideally be #10729. Until that is accomplished, as noted by zeripath above there is a workaround.
Regardless of whether that workaround is subjectively sufficient or not, none of us are paid to work on this project and so we cannot force anyone to take on the work.

@wxiaoguang
Copy link
Contributor

wxiaoguang commented Jul 17, 2022

Can you try it on https://try.gitea.io ? The editor is using contenteditable mode now.


I did some tests on mobile (Android), it seems that in some cases the contenteditable mode is still buggy. In most cases, it seems usable (better than before?)

@wxiaoguang wxiaoguang added issue/needs-feedback For bugs, we need more details. For features, the feature must be described in more detail and removed issue/needs-feedback For bugs, we need more details. For features, the feature must be described in more detail labels Jul 17, 2022
@silverwind
Copy link
Member

Fixed with #23876

@github-actions github-actions bot locked as resolved and limited conversation to collaborators May 19, 2023
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
issue/confirmed Issue has been reviewed and confirmed to be present or accepted to be implemented outdated/theme/markdown topic/mobile type/upstream This is an issue in one of Gitea's dependencies and should be reported there
Projects
None yet
Development

No branches or pull requests

10 participants