-
Notifications
You must be signed in to change notification settings - Fork 29.9k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Context switching prevents external keyboard input in Terminal (iPadOS Safari) #144232
Comments
@rebornix this seems like an ipadOS problem. Thoughts? |
@meganrogge I think this is a focus issue. As long as we use a textarea under the hood, we might get into trouble that the textarea thinks we have focus (no |
@rebornix Is there anything I can do to help debug this? |
Recommend #151626 should be closed as it doesn’t clearly articulate this issue, and both this issue’s and that issue’s last comments reference each other. Also recommend this issue remains open and be addressed. |
Merging #151626 here. Some extra info from there:
fyi @joaomoreno |
/duplicate #163448 |
Help wanted here, to make it clear the team will likely not fix this as those that contribute to the terminal don't have ipads. |
This makes vs code tunnels almost unusable! It seems to affect arrow keys and escape as well as enter. Normal characters as well as control, option, command, and the emoji meta keys all work. Sometimes I have to fiddle with focus until those buttons work: I can't, however, restore the other meta keys without physically unplugging the keyboard. |
On-screen keyboard works fine, but not for physical attached one (at least on the offcial Apple one) |
There is a workaround I found here: |
Steps to Reproduce:
.
key on any repo)Command
+J
to focus it) and it should print as expectedVideo reproduction:
FullSizeRender.MOV
Expected behavior:
If the keyboard focus is on the terminal the active input device should regain focus when OS context switches back to VSCode. This very well could be an iPadOS Safari bug, but if so it seemed important to document it here since I couldn’t find a specific issue covering this unexpected and disruptive behavior.
The text was updated successfully, but these errors were encountered: