Blank place with external keyboard on ipados with safari/chrome

[Paultje52]

• Web Browser: Safari
• Local OS: IpadOS 14
• Remote OS: Ubuntu 16.04
• code-server --version: 3.4.1

I connected an external bluetooth keyboard to my ipad.
When I click on a place where I can type, in the code itself, terminal, creating new files, etc, a blank place where the keyboard should be appears, that takes half of the screen up. It's so annoying that coding isn't possible.

Chrome

I also downloaded chrome, and when I try coding on chrome, a bar appears in the middle of the screen.

[Paultje52]

I made this issue a week ago. No answer. Is this a bug, or am I doing something wrong? Or is this unfixable bug by ios/ipados?

[code-asher]

I don't have an iPad so I can't make any concrete statements but I think it's unlikely these are caused by code-server. @nhooyr are you able to replicate this?

[Paultje52]

I tried using https://repl.it on my ipad, and it works just fine, on safari and on chrome. No bar etc, so that means that the issue is with code-server and not with ipados.

[nhooyr]

@Paultje52 repl.it isn't browser VS Code, it uses Monaco but is entirely different otherwise. I'll give this a test soon.

[Paultje52]

I know that repl.it isn't the same as code-server. I'm just saying that it is possible to remove bars like that.

Anyways, is there any progress?

[nhooyr]

Unfortunately not. Also see #979

Safari's support for running VS Code is very poor!

We currently have 14 open issues for safari! https://github.com/cdr/code-server/issues?q=is%3Aopen+is%3Aissue+label%3Abrowser-safari

[jsjoeio]

Hey @Paultje52 - are you still seeing this issue?

I’m currently using code-server on iPad and not seeing this issue.

Here’s a screenshot:

I’m using:

• iPad Pro (11 inch, 2nd gen) v14.1
• Apple Magic Keyboard
• Chrome v87.0

If this is no longer an issue, feel free to close.

[Paultje52]

Hello. Sorry for the late response, but I installed code-server version 3.8.0 an I don't have any problems in safari or chrome. This issue can be closed, thanks for your help!

[jsjoeio]

Hooray! Thanks for following up @Paultje52 - glad to hear it!