Add Touch Support for Mobile Editing #2336

New Issue

GiteaMirror · 2025-11-02T04:33:13-06:00

GiteaMirror commented

2025-11-02 04:33:13 -06:00

Originally created by @ghost on GitHub (Sep 15, 2018).

Sorry no template in FastHub-Libre so please enjoy freeform issue goodness. 😊

On Brave browser for Android, both in Standard and Desktop view, markdown file editing is not easy as:

In Mobile View touching inside a text area or editable region to edit files causes erroneous characters to output to the screen, rendering copy/paste inaccessible.
In Brave Mobile Desktop View long-pressing to select words and highlight text is not possible as the gesture seems to be swallowed by some other handler. Pasting, however, does work in this view.

Verdict? Needs some UX love, and cross-browser testing on mobile browsers using different platforms so basic file editing is possible using a soft or virtual keyboard.

Many thanks to the team for continuing to provide a stellar self-hosted alterative to Gogs.

Originally created by @ghost on GitHub (Sep 15, 2018). Sorry no template in FastHub-Libre so please enjoy freeform issue goodness. :blush: On Brave browser for Android, both in Standard and Desktop view, markdown file editing is not easy as: 1. In Mobile View touching inside a text area or editable region to edit files causes erroneous characters to output to the screen, rendering copy/paste inaccessible. 2. In Brave Mobile Desktop View long-pressing to select words and highlight text is not possible as the gesture seems to be swallowed by some other handler. Pasting, however, _does_ work in this view. Verdict? Needs some UX love, and cross-browser testing on mobile browsers using different platforms so basic file editing is possible using a soft or virtual keyboard. Many thanks to the team for continuing to provide a stellar self-hosted alterative to Gogs.

GiteaMirror added the type/enhancement issue/stale labels 2025-11-02 04:33:13 -06:00

GiteaMirror closed this issue

2025-11-02 04:33:13 -06:00

GiteaMirror commented

2025-11-02 04:33:14 -06:00

@insertjokehere commented on GitHub (Oct 22, 2018):

I'm seeing a similar (related?) issue on Chrome for Android; when editing a markdown file:

it<space> -> it
was -> ititwas
<space> -> ititwasititwas

@insertjokehere commented on GitHub (Oct 22, 2018): I'm seeing a similar (related?) issue on Chrome for Android; when editing a markdown file: * `it<space>` -> `it` * `was` -> `ititwas` * `<space>` -> `ititwasititwas`

GiteaMirror commented

2025-11-02 04:33:14 -06:00

@lafriks commented on GitHub (Oct 22, 2018):

I have same also on github so this could be browser bug

@lafriks commented on GitHub (Oct 22, 2018): I have same also on github so this could be browser bug

GiteaMirror commented

2025-11-02 04:33:14 -06:00

@ghost commented on GitHub (Oct 24, 2018):

Tested GitHub and was not able to reproduce. By default GitHub doesn't offer a file editor unless in Desktop View so perhaps that's some kind of UX workaround in their UI.

Also reproduced issue in Via mobile browser on Android. Each screen touch causes the last untrimmed full word to duplicate itself in the editor even when focus is lost.

Obviously this isn't a top priority but it is indeed a bug of some sort.

@ghost commented on GitHub (Oct 24, 2018): Tested GitHub and was not able to reproduce. By default GitHub doesn't offer a file editor unless in Desktop View so perhaps that's some kind of UX workaround in their UI. Also reproduced issue in [Via](https://github.com/LakorTi/Via) mobile browser on Android. Each screen touch causes the last untrimmed full word to duplicate itself in the editor even when focus is lost. Obviously this isn't a top priority but it is indeed a bug of some sort.

GiteaMirror commented

2025-11-02 04:33:14 -06:00

@stale[bot] commented on GitHub (Jan 5, 2019):

This issue has been automatically marked as stale because it has not had recent activity. It will be closed if no further activity occurs during the next 2 weeks. Thank you for your contributions.

@stale[bot] commented on GitHub (Jan 5, 2019): This issue has been automatically marked as stale because it has not had recent activity. It will be closed if no further activity occurs during the next 2 weeks. Thank you for your contributions.

GiteaMirror commented

2025-11-02 04:33:15 -06:00

@stale[bot] commented on GitHub (Feb 23, 2019):

This issue has been automatically closed because of inactivity. You can re-open it if needed.

@stale[bot] commented on GitHub (Feb 23, 2019): This issue has been automatically closed because of inactivity. You can re-open it if needed.

GiteaMirror commented

2025-11-02 04:33:15 -06:00

@ghost commented on GitHub (Feb 24, 2019):

Letting this one go.

P.s. Bot says "You can re-open it if needed." but that's not necessarily true.

@ghost commented on GitHub (Feb 24, 2019): Letting this one go. P.s. Bot says "You can re-open it if needed." but that's not necessarily true.

GiteaMirror referenced this issue