The issue editor has a reproducibility issue, reported via https://twitter.com/CorneliusRoemer/status/1338154365950038016 -- confirmed on one mobile device with both Fennec and Chrome, not reproducible on another.
Thanks for opening this - faster than I could make it to a desktop, didn't want to provide another messy issue.
Do you need anything from me to aid reproducibility? Maybe you could also provide the workaround recommendation here in this thread so that people who find it know about it.
It would be good if we could figure out why it works on some phones but not others. (reports of OS/browser versions etc)
To paraphrase the problem report tweet here: Gitea's WYSIWYG issue editor is in some mobile browsers pasting repeated trailing letters/syllables/words as soon the backspace key is pressed, making it hard or impossible to use.
Switching to plain text mode issue editor (last button in toolbar) allows to work around the issue temporarily.
Not clear yet what OS/browser combinations work and what not.
Gitea's mobile web experience is ... bad.
@cornelius.roemer do you know about GitNex
yes this does not solve the problem - but it works
Mozilla/5.0 (Linux; Android 11; IN2013) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/87.0.4280.101 Mobile Safari/537.36
Also reproduced on Brave on mobile
Mozilla/5.0 (Linux; Android 11; IN2013) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/87.0.4280.88 Mobile Safari/537.36
And Edge 45, Chrome 87.0.3865
And Opera
Mozilla/5.0 (Linux; Android 11; IN2013) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/86.0.4240.198 Mobile Safari/537.36 OPR/61.1.3076.56625
So anything with Chrome so far, including 86 and 87.
@hw Ok I'll get started.
I quite like Codeberg now on Desktop. It was just my first experience, on mobile, trying to open an issue for CCTG that I got a very bad welcome. That's actually one of the most common ways new people will first encounter Codeberg so it should really be sorted out rather soon.
Would it be possible to switch the default editor on unstable OS/browser combinations to the non-buggy one to prevent this from being a big red flag for anyone interacting with Codeberg for the first time?
@6543 Workarounds are ok for the initiated, but for opening an issue on CCTG you should not need to install an app or click through fora to find a way around.
Does this issue exist on Gitea? Shall we crosspost it there?
Do you need anything else from me?
Can we make the plain editor the default on mobile for the time being? What do you all think? cc: @ashimokawa
@6543 : do you know off-hand, if there is already a gitea upstream issue on this, or shall we create a new one?
@hw Thanks for considering a quick&dirty fix until Gitea solves this. I crossposted this issue there, turns out, the problem has been known since at least July - with no visible (PR) attempt made to resolve as far as I can tell. Which increases the attraction of an intermediary fix for Codeberg.
Here are the upstream issues:
https://github.com/go-gitea/gitea/issues/13132
https://github.com/go-gitea/gitea/issues/12146
If this is easily possible, I would like to have a workaround, even if that implies a simple and plain text input. The way is is now is probably really bad for most people.
GitNex is great but it should not be required to do stuff from mobile.
Here's an up-upstream issue for vanilla Simple MDE: https://github.com/sparksuite/simplemde-markdown-editor/issues/802
We created a temporary workaround in Codeberg/build-deploy-gitea@a72d228868, deployed to https://codeberg-test.org.
@cornelius.roemer : Can you please test, if this is kind-of reliably circumventing the issue, we'd push this to production too.
Great! Unfortunately I don't seem to be able to test it - or do you have a test account I can log in with? Github doesn't work, I don't get an activation email after registration either.
Great! Unfortunately I don't seem to be able to test it - or do you have a test account I can log in with? Github doesn't work, I don't get an activation email after registration either.
Mail log says "The email account that you tried to reach does not exist. Please try 550-5.1.1 double-checking the recipient's email address for typos or 550-5.1.1 unnecessary spaces." .. manually activated, login should work now.
Strange. The email is definitely valid. Anyhow...
The intermediary fix works! No more SimpleMDE it seems, off by default on mobile.
Strange. The email is definitely valid. Anyhow...
Just got told that the one is partially down again; could be on their side.
Deployed on codeberg.org also now
FWIW Google's mail system was bouncing a significant portion of emails today.
Tada, it works. Amazing how quickly you guys fixed this from report to fix. Impressed!
@ashimokawa time to rebase codeberg branch on top of v1.13 -> github.com/go-gitea/gitea@4f296f7436 got merged witch should close this issue :)
PS: Codeberg/build-deploy-gitea@840fd48cad can be reverted
All done, including the revert. Thanks!
I still have problems with the issue editor on Firefox mobile. Cursor jumping around mixing up my typed words.
Has this issue come back or was it not solved completely?
Do you have the "revert to simple textarea" on mobile? A document / paper icon at the right? This is a workaround I use on my PC when necessary ... otherwise, the upstream PR for the complete switch is still a WIP as far as I kknow.
@fnetX thanks, this is working for me. I also read in the gitea issues, that they want to replace this buggy editor.
I have this issue as ewlö. It's usper annoying to utpe here as otu can see. :/
No due date set.
No dependencies set.
Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?