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

Context menu not shown on surface pro 4 #3056

Closed
TheLevenCreations opened this issue Feb 16, 2016 · 2 comments
Closed

Context menu not shown on surface pro 4 #3056

TheLevenCreations opened this issue Feb 16, 2016 · 2 comments
Assignees
Labels
bug Issue identified by VS Code Team member as probable bug important Issue identified as high-priority verified Verification succeeded
Milestone

Comments

@TheLevenCreations
Copy link

This is an usability issue. I am using Surface pro 4 tablet, windows 10 x64, vscode 0.10.8.

As a source code reviewer, I'd like to go to the definition from a source code line, without the need of keyboard or tablet pen.

Normally, if you want to right click on "my Computer" or "Desktop" or anywhere, you can just put your finger on the tablet screen and hold there for 3 seconds, the context menu will pop up.
However, in vscode, I put my finger right in javascript source code viewlet and hold it for several seconds and nothing happens. As a result, if user want to navigate to definition, or 'Go to symbol', he/she needs to click the system menu on right-left side of vscode, or, use a keyboard, which both are annoying if you are using a tablet which usually no keyboard no pen support - you can only use a finger to touch.

Please see: https://github.com/TheLevenCreations/electron_typescript_template/blob/master/captured2.gif

@TheLevenCreations
Copy link
Author

BTW, put the surface pen in there and hold there for 3 seconds, the context menu will pop up. Why finger cannot?

@TheLevenCreations
Copy link
Author

This issue also exists on 0.10.7, 0.10.6

@alexdima alexdima added bug Issue identified by VS Code Team member as probable bug important Issue identified as high-priority labels Feb 16, 2016
@alexdima alexdima self-assigned this Feb 16, 2016
@alexdima alexdima added this to the Feb 2016 milestone Feb 16, 2016
@alexdima alexdima assigned joaomoreno and unassigned alexdima Feb 26, 2016
@joaomoreno joaomoreno added the verified Verification succeeded label Feb 26, 2016
@vscodebot vscodebot bot locked and limited conversation to collaborators Nov 18, 2017
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
bug Issue identified by VS Code Team member as probable bug important Issue identified as high-priority verified Verification succeeded
Projects
None yet
Development

No branches or pull requests

3 participants