Keyboard navigation commands and braille routing don't work as expected in the terminal input editor

[daniel-montalvo]

Type: Bug

To replicate.

1. Go to terminal pressing CTRL+`
2. Type something in the terminal input edit box, for example "git diff"
3. Use your arro keys to navigate the contents in the edit box

Expected result As you use left and right arrow keys, you get info as to where the cursor is as you move. The braille display shows the whole input and the cursor is updated as you move left and right.

Obtained result

Braille displays don't show the contents of the edit box. Screen readers do not read the cursor position as you move left and arrow keys

This is similar to #146994 which was resolved in #191828

VS Code version: Code 1.84.2 (1a5daa3a0231a0fbba4f14db7ec463cf99d7768e, 2023-11-09T10:51:52.184Z) OS version: Windows_NT x64 10.0.22631 Modes: Remote OS version: Linux x64 5.15.133.1-microsoft-standard-WSL2

System Info

|Item|Value| |---|---| |CPUs|Intel(R) Core(TM) i7-8665U CPU @ 1.90GHz (8 x 2112)| |GPU Status|2d_canvas: enabled
canvas_oop_rasterization: enabled_on
direct_rendering_display_compositor: disabled_off_ok
gpu_compositing: enabled
multiple_raster_threads: enabled_on
opengl: enabled_on
rasterization: enabled
raw_draw: disabled_off_ok
video_decode: enabled
video_encode: enabled
vulkan: disabled_off
webgl: enabled
webgl2: enabled
webgpu: enabled| |Load (avg)|undefined| |Memory (System)|15.81GB (4.68GB free)| |Process Argv|--crash-reporter-id 1f62659b-b510-4103-8662-f773a43c0887| |Screen Reader|yes| |VM|0%| |Item|Value| |---|---| |Remote|WSL: Ubuntu| |OS|Linux x64 5.15.133.1-microsoft-standard-WSL2| |CPUs|Intel(R) Core(TM) i7-8665U CPU @ 1.90GHz (8 x 2112)| |Memory (System)|7.67GB (6.66GB free)| |VM|0%|

Extensions (29)

Extension|Author (truncated)|Version ---|---|--- spellright|ban|3.0.118 remotehub|Git|0.62.0 remote-wsl|ms-|0.81.8 azure-repos|ms-|0.38.0 remote-repositories|ms-|0.40.0 st235-wordscounter|ale|0.0.3 gh-cli-actions|arc|1.2.0 composer-php-vscode|DEV|1.41.14263 intelli-php-vscode|DEV|0.10.14222 phptools-vscode|DEV|1.41.14263 profiler-php-vscode|DEV|1.41.14263 gitlens|eam|14.5.1 copilot-chat|Git|0.10.2 remotehub|Git|0.62.0 vscode-github-actions|git|0.26.2 vscode-pull-request-github|Git|0.77.2023110909 html-links-checker|j-c|1.1.13 vscode-language-pack-es|MS-|1.84.2023111509 python|ms-|2023.20.0 jupyter|ms-|2023.10.1100000000 jupyter-renderers|ms-|1.0.17 vscode-jupyter-cell-tags|ms-|0.1.8 vscode-jupyter-slideshow|ms-|0.1.5 azure-repos|ms-|0.38.0 remote-repositories|ms-|0.40.0 html-validator|Nar|1.3.1 code-spell-checker|str|3.0.1 five-server|yan|0.2.3 json|Zai|2.0.2

A/B Experiments

``` vsliv368:30146709 vsreu685:30147344 python383cf:30185419 vspor879:30202332 vspor708:30202333 vspor363:30204092 vslsvsres303:30308271 vserr242:30382549 pythontb:30283811 vsjup518:30340749 pythonptprofiler:30281270 vshan820:30294714 vstes263:30335439 vscoreces:30445986 vscod805cf:30301675 binariesv615:30325510 bridge0708:30335490 bridge0723:30353136 vsaa593cf:30376535 pythonvs932:30410667 py29gd2263:30899288 vsclangdf:30486550 c4g48928:30535728 dsvsc012:30540252 azure-dev_surveyone:30548225 3biah626:30602489 f6dab269:30613381 showlangstatbar:30737416 fixshowwlkth:30771522 showindicator:30805244 pythongtdpath:30769146 i26e3531:30792625 pythonnosmt12:30797651 pythonidxpt:30866567 pythonnoceb:30805159 asynctok:30898717 dsvsc013:30795093 dsvsc014:30804076 dsvsc015:30845448 pythontestfixt:30902429 pyreplss1:30897532 pythonmypyd1:30879173 pythoncet0:30885854 pythontbext0:30879054 accentitlementsc:30887149 dsvsc016:30899300 dsvsc017:30899301 dsvsc018:30899302 aa_t_chat:30882232 ```

[meganrogge]

Thanks for the issue. Have you tried using the accessible view, via alt+F2?

[daniel-montalvo]

Thanks for your reply.

Yes, and that works very nicely. The issue, though, is not when reviewing the output of the terminal. It is when reviewing your input. For example, Let’s say you’ve made a typo when typing ‘git commit -M “message”’ and you want to correct it. I would expect to be able to use the wrrow keys just like in any other editor within VS Code.

---

Daniel Montalvo

Accessibility Specialist

W3C/WAI

From: Megan Rogge @.> Sent: Friday, December 15, 2023 11:32 PM To: microsoft/vscode @.> Cc: Daniel Montalvo @.>; Author @.> Subject: Re: [microsoft/vscode] Keyboard navigation commands and braille routing don't work as expected in the terminal input editor (Issue #199651)

Thanks for the issue. Have you tried using the accessible view, via alt+F2?

— Reply to this email directly, view it on GitHub https://github.com/microsoft/vscode/issues/199651#issuecomment-1858567854 , or unsubscribe https://github.com/notifications/unsubscribe-auth/ALYFOWSFWI33G6FBQJPAW7LYJTFULAVCNFSM6AAAAABABA2O22VHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMYTQNJYGU3DOOBVGQ . You are receiving this because you authored the thread.Message ID: @.***>

[meganrogge]

The underlying text area should be synced with the terminal input, so I'd expect this to work. Could you pls add the setting: "terminal.integrated.developer.devMode": true to your settings.json file and record your screen?

[vscodenpa]

This issue has been closed automatically because it needs more information and has not had recent activity. See also our issue reporting guidelines.

Happy Coding!