Skip to content
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

touch keyboard doesn't auto-trigger #2055

Closed
LordObsidian01 opened this issue Jul 22, 2019 · 3 comments
Closed

touch keyboard doesn't auto-trigger #2055

LordObsidian01 opened this issue Jul 22, 2019 · 3 comments
Labels
Area-Input Related to input processing (key presses, mouse, etc.) Area-TerminalControl Issues pertaining to the terminal control (input, selection, keybindings, mouse interaction, etc.) Area-User Interface Issues pertaining to the user interface of the Console or Terminal Help Wanted We encourage anyone to jump in on these. Issue-Task It's a feature request, but it doesn't really need a major design. Product-Terminal The new Windows Terminal. Resolution-Duplicate There's another issue on the tracker that's pretty much the same thing.
Milestone

Comments

@LordObsidian01
Copy link

When using a touch device (such as a Surface Pro 4) in tablet mode, I expect the touch keyboard to be presented when you tap on the input area of the terminal, however it does not. it is the same behavior with PS, cmd, wsl. the cursor appears and waits for input but no keyboard.

@ghost ghost added Needs-Triage It's a new issue that the core contributor team needs to triage at the next triage meeting Needs-Tag-Fix Doesn't match tag requirements labels Jul 22, 2019
@DHowett-MSFT DHowett-MSFT added Area-Input Related to input processing (key presses, mouse, etc.) Area-TerminalControl Issues pertaining to the terminal control (input, selection, keybindings, mouse interaction, etc.) Area-User Interface Issues pertaining to the user interface of the Console or Terminal Help Wanted We encourage anyone to jump in on these. Issue-Task It's a feature request, but it doesn't really need a major design. Product-Terminal The new Windows Terminal. labels Jul 22, 2019
@ghost ghost removed the Needs-Tag-Fix Doesn't match tag requirements label Jul 22, 2019
@DHowett-MSFT DHowett-MSFT added Needs-Tag-Fix Doesn't match tag requirements and removed Needs-Triage It's a new issue that the core contributor team needs to triage at the next triage meeting labels Jul 22, 2019
@ghost ghost removed the Needs-Tag-Fix Doesn't match tag requirements label Jul 22, 2019
@miniksa miniksa changed the title touch keyboard doesn't auto-tigger touch keyboard doesn't auto-trigger Jul 23, 2019
@miniksa
Copy link
Member

miniksa commented Jul 23, 2019

I am relatively sure that #1919 will resolve this. I think touch and pen input is activated via a TSF context. If we have a TSF context, I think it will show the keyboard.

@zadjii-msft zadjii-msft added this to the Terminal v1.0 milestone Dec 19, 2019
@DHowett-MSFT
Copy link
Contributor

Moving discussion to /dup #3639

@ghost
Copy link

ghost commented Jan 23, 2020

Hi! We've identified this issue as a duplicate of another one that already exists on this Issue Tracker. This specific instance is being closed in favor of tracking the concern over on the referenced thread. Thanks for your report!

@ghost ghost closed this as completed Jan 23, 2020
@ghost ghost added the Resolution-Duplicate There's another issue on the tracker that's pretty much the same thing. label Jan 23, 2020
This issue was closed.
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Area-Input Related to input processing (key presses, mouse, etc.) Area-TerminalControl Issues pertaining to the terminal control (input, selection, keybindings, mouse interaction, etc.) Area-User Interface Issues pertaining to the user interface of the Console or Terminal Help Wanted We encourage anyone to jump in on these. Issue-Task It's a feature request, but it doesn't really need a major design. Product-Terminal The new Windows Terminal. Resolution-Duplicate There's another issue on the tracker that's pretty much the same thing.
Projects
None yet
Development

No branches or pull requests

4 participants