microsoft / vscode

Visual Studio Code
https://code.visualstudio.com
MIT License
163.06k stars 28.8k forks source link

Strange behavior in settings screen #180007

Open jvesouza opened 1 year ago

jvesouza commented 1 year ago

Type: Bug CC: @isidorn @meganrogge

I don't know if the problem has something to do with the use of a screen reader. In this case I am using the Orca screen reader. The problem may not happen with other screen readers.

To reproduce try the following steps:

  1. Press ctrl+, to activate the settings screen.
  2. In the search box type zen.
  3. Press tab key 3 times.
  4. Press the down arrow until you find the Zen Mode: Hide Line Numbers option.
  5. Press the tab key.
  6. Press the shift+tab key.

Expected: The focus should be moved to the same place it was before pressing the tab key.

Actual: The focus is moved to a different place.

Eventually I need to rerun steps 5 and 6 for the problem to happen.

VS Code version: Code - Insiders 1.78.0-insider (3ad5774eb8123d4224eb55629df9e5f82fe13b99, 2023-04-14T05:27:06.042Z) OS version: Linux x64 6.2.9-200.fc37.x86_64 Modes: Sandboxed: Yes

System Info |Item|Value| |---|---| |CPUs|Intel(R) Core(TM) i5-8250U CPU @ 1.60GHz (8 x 2681)| |GPU Status|2d_canvas: enabled
canvas_oop_rasterization: disabled_off
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: disabled_software
vulkan: disabled_off
webgl: enabled
webgl2: enabled
webgpu: disabled_off| |Load (avg)|1, 1, 1| |Memory (System)|15.26GB (6.68GB free)| |Process Argv|--crash-reporter-id bc02adbd-6c3a-44b8-af92-55103a608af7| |Screen Reader|yes| |VM|0%| |DESKTOP_SESSION|gnome-xorg| |XDG_CURRENT_DESKTOP|GNOME| |XDG_SESSION_DESKTOP|gnome-xorg| |XDG_SESSION_TYPE|x11|
Extensions (42) Extension|Author (truncated)|Version ---|---|--- doxdocgen|csc|1.4.0 vscode-markdownlint|Dav|0.49.0 vscode-eslint|dba|2.4.0 EditorConfig|Edi|0.16.4 copilot|Git|1.82.15 rest-client|hum|0.25.1 better-cpp-syntax|jef|1.17.2 docomment|k--|1.0.0 azure-pipelines|ms-|1.208.0 vscode-docker|ms-|1.24.0 csharp|ms-|1.25.4 vscode-dotnet-runtime|ms-|1.6.0 vscode-kubernetes-tools|ms-|1.3.11 remote-containers|ms-|0.290.0 remote-ssh|ms-|0.101.2023041015 remote-ssh-edit|ms-|0.84.0 azure-account|ms-|0.11.3 cmake-tools|ms-|1.13.45 cpptools|ms-|1.15.2 cpptools-extension-pack|ms-|1.3.0 makefile-tools|ms-|0.6.0 powershell|ms-|2023.4.0 remote-explorer|ms-|0.5.2023040509 vsliveshare|ms-|1.0.5857 oracledevtools|Ora|21.5.0 fabric8-analytics|red|0.3.6 java|red|1.18.2023041404 vscode-xml|red|0.25.2023041204 vscode-yaml|red|1.12.2 sonarlint-vscode|Son|3.16.0 cmake|twx|0.0.17 intellicode-api-usage-examples|Vis|0.2.7 vscodeintellicode|Vis|1.2.30 vscode-boot-dev-pack|vmw|0.2.1 vscode-spring-boot|vmw|1.45.0 vscode-java-debug|vsc|0.49.2023032407 vscode-java-dependency|vsc|0.21.2023041400 vscode-java-pack|vsc|0.25.2023032708 vscode-java-test|vsc|0.38.2023032402 vscode-maven|vsc|0.41.2023041103 vscode-spring-boot-dashboard|vsc|0.12.0 vscode-spring-initializr|vsc|0.11.2 (1 theme extensions excluded)
A/B Experiments ``` vsliv695:30137379 vsins829:30139715 vsliv368cf:30146710 vsreu685:30147344 python383cf:30185419 vspor879:30202332 vspor708:30202333 vspor363:30204092 vswsl492cf:30256198 vstes627cf:30244335 vslsvsres303:30308271 pythontb:30258533 pythonptprofiler:30281269 vshan820:30294714 pythondataviewer:30285072 vscod805cf:30301675 bridge0708:30335490 bridge0723:30353136 cmake_vspar411:30581797 vsaa593cf:30376535 pythonvs932:30404738 cppdebug:30492333 vsclangdf:30492506 c4g48928:30535728 dsvsc012cf:30540253 pynewext54:30618038 pylantcb52:30590116 nodejswelcome1:30587009 pyind779:30611226 pythonsymbol12:30651887 6233i204:30659907 defaultazurewalk:30687958 pythonms35:30671666 cai9j608:30680470 24365598:30687740 pythonfmttext:30710679 pythonclientmv:30700173 ```
meganrogge commented 1 year ago

Hm, at first try, this is working for me. @rzhao271 any changes here recently?

rzhao271 commented 1 year ago

I don't think it's a regression, but I was able to confirm the issue after repeating steps 5 and 6 a few times.