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.

Sign up for GitHub

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

Jump to bottom

up/down keys not working in ui settings #74115

Closed
byehack opened this issue May 22, 2019 · 3 comments
Closed

up/down keys not working in ui settings #74115

byehack opened this issue May 22, 2019 · 3 comments
Assignees
@roblourens
Labels
*duplicate Issue identified as a duplicate of another issue(s) info-needed Issue requires more information from poster

Comments

@byehack
Copy link

byehack commented May 22, 2019 •
edited
Loading

Version: 1.34.0 (user setup)
Commit: a622c65
Date: 2019-05-15T21:59:53.881Z
Electron: 3.1.8
Chrome: 66.0.3359.181
Node.js: 10.2.0
V8: 6.6.346.32
OS: Windows_NT ia32 10.0.10586

Does this issue occur when all extensions are disabled?: No
@byehack byehack mentioned this issue May 24, 2019
Closed
@sandy081 sandy081 assigned roblourens and unassigned sandy081 May 28, 2019
@roblourens
Copy link
Member

I need you to explain exactly what the issue is, please be very specific.

@roblourens roblourens added the info-needed Issue requires more information from poster label May 29, 2019
@byehack
Copy link
Author

byehack commented May 31, 2019

I need you to explain exactly what the issue is, please be very specific.

thanks for your reply.
when we are in the ui settings we must use scroll to go to up/down settings. it is very hard when there are a lot of settings. currently is not possible to move the page slowly with up/down key in the ui settings page. currently the up/down key don't do anything in the settings ui. and i should use tab key for this and it isnt good choose for me

@roblourens
Copy link
Member

Ok, yes I am tracking that here: #66237

@roblourens roblourens added the *duplicate Issue identified as a duplicate of another issue(s) label May 31, 2019
@vscodebot vscodebot bot locked and limited conversation to collaborators Jul 15, 2019
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Assignees

@roblourens roblourens

Labels
*duplicate Issue identified as a duplicate of another issue(s) info-needed Issue requires more information from poster
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
3 participants
@roblourens @sandy081 @byehack