We read every piece of feedback, and take your input very seriously.
To see all available qualifiers, see our documentation.
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
Testing #55389
Issue Type: Bug
Bug Notice entry for Accessibility Options. My understanding is that this is a command for internal use and should generally not be used by users
Accessibility Options
@alexandrudima Says we can remove the entire Accessibility Options command so that it no longer shows up in the command palette either
VS Code version: Code - Insiders 1.26.0-insider (0707dd4, 2018-07-31T05:18:06.861Z) OS version: Windows_NT x64 10.0.17686
The text was updated successfully, but these errors were encountered:
👍 We can just remove it if it bothers people. We only had it in insiders and used it as a critical Electron workaround for electron/electron#7208.
Sorry, something went wrong.
560724f
Remove accessability options logic entirely
0325e25
Follow up on #55451
@sbatten Added bug label.
bug
sbatten
No branches or pull requests
Testing #55389
Issue Type: Bug
Bug
Notice entry for
Accessibility Options
. My understanding is that this is a command for internal use and should generally not be used by users@alexandrudima Says we can remove the entire
Accessibility Options
command so that it no longer shows up in the command palette eitherVS Code version: Code - Insiders 1.26.0-insider (0707dd4, 2018-07-31T05:18:06.861Z)
OS version: Windows_NT x64 10.0.17686
System Info
checker_imaging: disabled_off
flash_3d: enabled
flash_stage3d: enabled
flash_stage3d_baseline: enabled
gpu_compositing: enabled
multiple_raster_threads: enabled_on
native_gpu_memory_buffers: disabled_software
rasterization: unavailable_software
video_decode: enabled
video_encode: enabled
webgl: enabled
webgl2: enabled
The text was updated successfully, but these errors were encountered: