How to produce the bug:

  1. Connect a Bluetooth or OTG-USB keyboard to an Android device.
  2. In SE app, start typing a comment which is 2 lines or longer.
  3. While on any line other than the first, try using to go back to correct a typo, etc.
  4. Instead of taking you just one character back, the button will take you dozens of characters back.

I've reproduced this bug using the latest version (1.0.85) of the app on Samsung I9305 running Android 4.4.4.

I've also reproduced on Asus ZE551ML (Android 5.0).

@IlmariKaronen has reproduced on Samsung XCover 3 (Android 5.1.1)

@meatball has reproduced on the Nexus 4 (Android 4.4.2).

Android devices with hard keyboards are becoming more and more common. Remix OS is gaining ground. Android apps are coming to Chrome OS. Therefore, this bug should be given priority to fix. Also, it should be relatively easy to fix. I have never seen any other Android app with this type of bug.

  • 1
    Reproduced with Samsung XCover 3 / Android 5.1.1 and a Microsoft Wedge bluetooth keyboard. Curiously, changing the screen orientation (regardless of what it originally was) seems to make the bug disappear, and it doesn't reappear when I rotate the device back again. Canceling the comment by pressing the back button and then trying to post a new comment (even with just the same content copy-pasted in) does re-trigger it. – Ilmari Karonen Jun 22 '16 at 21:06
  • 1
    ... On the other hand, while rotating the screen while typing a comment seems to fix this bug, it also seems to trigger another bug that breaks the "post" button, making the comment impossible to submit. :( I had to use copy+paste to post the previous comment. – Ilmari Karonen Jun 22 '16 at 21:10
  • @IlmariKaronen Yes, I got the exact same behavior as you when I tried the rotation thing, including the broken "post" button. And that seems to be unrelated to the keyboard thing, as rotating the screen breaks the post button even without any external keyboard. Oo – Revetahw Jun 22 '16 at 21:22
  • @IlmariKaronen Since the rotation thing is a separate issue I've posted it as a separate question. – Revetahw Jun 22 '16 at 21:38
  • Same bug does not occur on iOS devices. – ArtOfCode Jun 22 '16 at 22:04
  • @ArtOfCode Thanks for checking, could you do this one too? – Revetahw Jun 22 '16 at 22:06
  • Seems related/dupe of this bug report. SE app had a weird bug with arrow keys for navigation in the first place (whether it's soft/physical keyboard). – Meta Andrew T. Jun 25 '16 at 8:39
  • @meatball Yeah, looks like a dupe! – Revetahw Jun 25 '16 at 8:47
  • Any reason you ruined your post? – Shadow The Dragon Wizard Jun 25 '16 at 12:44
  • @ShadowWizard What do you mean? – Revetahw Jun 25 '16 at 13:31
  • @Fiksdal you did not edit? – Shadow The Dragon Wizard Jun 25 '16 at 13:33
  • @ShadowWizard Yes, but what do you mean by "ruin"? – Revetahw Jun 25 '16 at 13:34
  • You really didn't notice the numerous typos, gibberish words and bad formatting? – Shadow The Dragon Wizard Jun 25 '16 at 13:40
  • @ShadowWizard No. I'm not that familiar with formatting standards, and English is only my second language. Feel free to do a cleanup of this post. Or tell me in comments what I can improve. – Revetahw Jun 25 '16 at 13:44
  • 1
    I think Shadow Wizard referred to this revision, and if I should guess the reason, you're probably (pocket-typing accidentally?) editing this post from the app. No worries, it has been fixed. – Meta Andrew T. Jun 25 '16 at 15:30

You must log in to answer this question.

Browse other questions tagged .