Terminal should dodge the onscreen keyboard slightly better #12337

Open
opened 2026-01-31 03:12:51 +00:00 by claunia · 6 comments
Owner

Originally created by @guai on GitHub (Feb 1, 2021).

Expected behavior

when onscreen keyboard is shown and terminal's window maximized then text in the terminal should not be printed under the kb, instead its working area should be shrinked to the visible area

Actual behavior

the terminal does print text in the area I don't see that is covered with onscreen keyboard

Originally created by @guai on GitHub (Feb 1, 2021). # Expected behavior when onscreen keyboard is shown and terminal's window maximized then text in the terminal should not be printed under the kb, instead its working area should be shrinked to the visible area # Actual behavior the terminal does print text in the area I don't see that is covered with onscreen keyboard
claunia added the Issue-FeatureProduct-TerminalArea-UserInterface labels 2026-01-31 03:12:51 +00:00
Author
Owner

@zadjii-msft commented on GitHub (Feb 1, 2021):

Interesting. That's a good find.

How this would play with split panes, I'm not sure. Say you've got a horizontal split in the terminal [-]. You bring up the onscreen keyboard - it entirely covers the bottom pane. What would we do then?

maybe related: #8623 - if we did have a scroll-forward (even just one page), then you could at least scroll forward to have the text be visible.

@zadjii-msft commented on GitHub (Feb 1, 2021): Interesting. That's a good find. How this would play with split panes, I'm not sure. Say you've got a horizontal split in the terminal `[-]`. You bring up the onscreen keyboard - it entirely covers the bottom pane. What would we do then? maybe related: #8623 - if we did have a scroll-forward (even just one page), then you could at least scroll forward to have the text be visible.
Author
Owner

@ghost commented on GitHub (Feb 5, 2021):

This issue has been automatically marked as stale because it has been marked as requiring author feedback but has not had any activity for 4 days. It will be closed if no further activity occurs within 3 days of this comment.

@ghost commented on GitHub (Feb 5, 2021): This issue has been automatically marked as stale because it has been marked as requiring author feedback but has not had any activity for **4 days**. It will be closed if no further activity occurs **within 3 days of this comment**.
Author
Owner

@Don-Vito commented on GitHub (Feb 7, 2021):

No, bot.. don't close it.. it is important feature.. @zadjii-msft -help 😊

@Don-Vito commented on GitHub (Feb 7, 2021): No, bot.. don't close it.. it is important feature.. @zadjii-msft -help :blush:
Author
Owner

@zadjii-msft commented on GitHub (Feb 8, 2021):

Derp wait yea, this doesn't need author feedback - but it does need some feedback I suppose. I'm not really sure how best to handle this scenario. That being said, it's something we should to eventually.

@zadjii-msft commented on GitHub (Feb 8, 2021): Derp wait yea, this doesn't need author feedback - but it does need _some_ feedback I suppose. I'm not really sure how best to handle this scenario. That being said, it's something we should to eventually.
Author
Owner

@DHowett commented on GitHub (Jul 2, 2021):

I'm going to put this on the backlog, but it needs design.

@DHowett commented on GitHub (Jul 2, 2021): I'm going to put this on the backlog, but it needs design.
Author
Owner

@PankajBhojwani commented on GitHub (Sep 12, 2022):

Does anyone know of an app that does this well? Trying to look for inspiration but it seems like Outlook, Word, Notepad all print text under the on-screen keyboard

@PankajBhojwani commented on GitHub (Sep 12, 2022): Does anyone know of an app that does this well? Trying to look for inspiration but it seems like Outlook, Word, Notepad all print text under the on-screen keyboard
Sign in to join this conversation.
1 Participants
Notifications
Due Date
No due date set.
Dependencies

No dependencies set.

Reference: starred/terminal#12337