Backspace works if you start backspacing "in the middle" of the word you wanna delete, but it crashes code-server(? Proof here: https://youtu.be/WOGQubsOjoo

Argh, well at least we know there is a workaround.

@leKamikaze1 do you know if the issue occurs with a separate bluetooth keyboard? I can try testing too. Wondering if this is specific to the on-screen keyboard.

Argh, well at least we know there is a workaround.

@leKamikaze1 do you know if the issue occurs with a separate bluetooth keyboard? I can try testing too. Wondering if this is specific to the on-screen keyboard.

Sadly, I never had a Bluetooth keyboard In my life, so its pretty impossible for me to test that

No worries at all. I have one lying around somewhere so I can test!

@jsjoeio Found something?

I finally got around to testing - it works with a bluetooth keyboard! No backspace issues 😄

Demo

Well, that's great. So, the issue is on Android's on-screen keyboard? Not sure what would cause it 🤔

It has to do with the way xterm.js is handling the input for on-screen keyboards I'm guessing:

Pulled from comment

• upstream: Issues with Backspace in Codespaces on Android (Surface Duo)
• underlying issue: Support mobile platforms

Any news? Working solution?
Backspace working, but can't delete special characters

Unfortunately, no :/ this is upstream and out of our control to fix. Only working solution I know of is to use an external keyboard.

microsoft/vscode@20f3ece#diff-720a2dcc75d4242d03024e70d87943ebc58dcdbb8baf1d1ab8b78792248b621a

Thanks for linking that @nikey02 ! Looks like that was part of vscode 1.55.2, which we upgraded to in #3085 which means...hopefully this isn't an issue in our next release 🤞

@jsjoeio
glad to hear that but
i want to point out some issues i facing

• in code-server settings UI dropdown menu is not working
• also regarding gboard backspace issue which was in monaco-editor but after patch another problem is shown in monaco-editor@0.23.0 that is backspace not
  working at beginning of the line

may be this is specific to me, if anyone has this issue please comment or test it ( all tested/having this in termux/android )

To keep things separate and ensure this doesn't get lost, do you mind opening a separate bug report issue? I'd be happy to take a closer look!

sure I'll make issue with proper testing and confirmation

thanks @jsjoeio