While typing answers and posts, on Android Chrome with the 'full site' option on, multiple bugs seem to arise; letters get randomly capitalised, duplicated, and start to come out of nowhere. Backspacing sometimes messes stuff up even further; words tend to duplicate when I do so. See the last typed paragraph in the below screenshot, which I've left unedited to show how this happens;


This has shown up multiple times when I use the site; it doesn't seem recent. I don't think it's due to me typing like a maniac, either; I checked while I was typing up the stuff in the screenshot, and I wasn't unintentionally hitting the 'capitalise' key.

Is it a site-wide bug, or am I doing something wrong? How can I fix it?

Update: here's a gif of the problem. I tried typing letters one be one, without touching any key other than the intended ones, and the errors persist. Things get even worse when I type at normal speeds, but even slow typing is difficult like this.

  • 4
    $\begingroup$ I don't have that, and I use the "full site" on my phone a lot. It looks like mistypes. These happen on a small keyboard. The "a" clicks the shift key, when you try to undo it, you accidentally press it again, etc. You don't need to type like a maniac. Just a tad less careful than perfect will lead to the same conclusion in some cases. $\endgroup$
    – Asaf Karagila Mod
    Aug 23 '21 at 18:53
  • 1
    $\begingroup$ @AsafKaragila: I suppose most of it could be explained by how I type, but there's the case of words and letters randomly multiplying when I do something. If by the shift key you mean the one that capitalizes letters, I took special care not to touch it when typing the stuff in the screenshot, and it still persists. It seemed to stop when I switched from GBoard to Samsung's keyboard, though. $\endgroup$
    – harry
    Aug 23 '21 at 19:18
  • 3
    $\begingroup$ The Android keyboard is prone to mistaking letter "a" for a single shift-key press, resulting in both the omission of letter "a" and the unintended capitalization of the next letter. $\endgroup$
    – hardmath
    Aug 23 '21 at 20:24
  • $\begingroup$ @hardmath: hmm. I'm still pretty sure it wasn't anything like that from when I typed and checked, but if it doesn't happen for anyone else I suppose it is my unholy typing. Thanks, I'll see to it. $\endgroup$
    – harry
    Aug 23 '21 at 21:21
  • 5
    $\begingroup$ I do see something similar on my Android device, but it is not frequent and is related to my keyboard app. You may try to change the keyboard app and see if that helps. $\endgroup$
    – Paramanand Singh Mod
    Aug 24 '21 at 2:24
  • 3
    $\begingroup$ I also experience this, but not only on Math.SE. $\endgroup$
    – soupless
    Aug 24 '21 at 15:14
  • $\begingroup$ @AsafKaragila: I've uploaded a gif of it. $\endgroup$
    – harry
    Aug 26 '21 at 1:06
  • 1
    $\begingroup$ Again, I am sorry that you have this problem, but I don't think it's an SE problem. $\endgroup$
    – Asaf Karagila Mod
    Aug 26 '21 at 7:01
  • $\begingroup$ We can wait a while to see if anyone not using Android has this problem. $\endgroup$
    – GEdgar
    Aug 26 '21 at 15:48
  • 1
    $\begingroup$ You may try to disable autocorrect feature in your keyboard app. Over time, a lot of wrong autocorrect words get saved in the app database (due to accidental/wrong touch). $\endgroup$
    – Paramanand Singh Mod
    Aug 27 '21 at 9:29

You must log in to answer this question.

Browse other questions tagged .