vscode: In some situations orca doesn't read the search settings label when we enter VSCode settings
Issue Type: Bug
CC: @isidorn CC: @joanmarie
Steps to reproduce:
- Launch orca.
- Launch VSCode.
- Go to preferences:open settings(UI) pressing ctrl+, .
Actual results: Orca stays mute. Expected results: Orca should read: “search settings editor”.
- type for example “status” in the search field.
- Move to the clear button pressing tab, and press enter or space bar to activate the button.
Actual results: Focus moves to search field but orca doesn’t read anything. Expected results: The focus should move to the search field and the orca should read the label of that field.
VS Code version: Code - Insiders 1.64.0-insider (5554b12acf27056905806867f251c859323ff7e9, 2022-02-02T17:16:05.517Z) OS version: Linux x64 5.16.4-arch1-1 Restricted Mode: No
System Info
| Item | Value |
|---|---|
| CPUs | Intel® Core™ i5-5200U CPU @ 2.20GHz (4 x 2344) |
| GPU Status | 2d_canvas: enabled gpu_compositing: enabled multiple_raster_threads: enabled_on oop_rasterization: disabled_off opengl: enabled_on rasterization: disabled_software skia_renderer: enabled_on video_decode: disabled_software vulkan: disabled_off webgl: enabled webgl2: enabled |
| Load (avg) | 1, 1, 1 |
| Memory (System) | 15.54GB (1.06GB free) |
| Process Argv | -n --crash-reporter-id bcecf5e0-97d1-4830-b28c-0943c4adab1c --crash-reporter-id bcecf5e0-97d1-4830-b28c-0943c4adab1c |
| Screen Reader | yes |
| VM | 0% |
| DESKTOP_SESSION | gnome-xorg |
| XDG_CURRENT_DESKTOP | GNOME |
| XDG_SESSION_DESKTOP | gnome-xorg |
| XDG_SESSION_TYPE | x11 |
Extensions (37)
| Extension | Author (truncated) | Version |
|---|---|---|
| vscode-eslint | dba | 2.2.2 |
| EditorConfig | Edi | 0.16.4 |
| prettier-vscode | esb | 9.2.0 |
| shell-format | fox | 7.2.2 |
| rest-client | hum | 0.24.6 |
| vscode-docker | ms- | 1.19.0 |
| csharp | ms- | 1.24.0 |
| vscode-aks-tools | ms- | 0.0.11 |
| vscode-kubernetes-tools | ms- | 1.3.6 |
| python | ms- | 2022.0.1762517795-dev |
| vscode-pylance | ms- | 2022.1.6-pre.1 |
| remote-containers | ms- | 0.218.0 |
| remote-ssh | ms- | 0.70.0 |
| remote-ssh-edit | ms- | 0.70.0 |
| azure-account | ms- | 0.9.11 |
| powershell | ms- | 2021.12.0 |
| vsliveshare | ms- | 1.0.5330 |
| vsliveshare-audio | ms- | 0.1.91 |
| oracledevtools | Ora | 21.3.0 |
| vscode-boot-dev-pack | Piv | 0.1.0 |
| vscode-concourse | Piv | 1.30.0 |
| vscode-manifest-yaml | Piv | 1.30.0 |
| vscode-spring-boot | Piv | 1.30.0 |
| fabric8-analytics | red | 0.3.5 |
| java | red | 1.3.0 |
| vscode-commons | red | 0.0.6 |
| vscode-xml | red | 0.18.2 |
| vscode-yaml | red | 1.3.0 |
| sonarlint-vscode | Son | 3.2.0 |
| vscodeintellicode | Vis | 1.2.16 |
| vscode-java-debug | vsc | 0.38.0 |
| vscode-java-dependency | vsc | 0.19.0 |
| vscode-java-pack | vsc | 0.21.0 |
| vscode-java-test | vsc | 0.34.0 |
| vscode-maven | vsc | 0.35.0 |
| vscode-spring-boot-dashboard | vsc | 0.2.0 |
| vscode-spring-initializr | vsc | 0.8.0 |
A/B Experiments
vsliv695:30137379
vsins829:30139715
vsliv368:30146709
vsreu685:30147344
python383:30185418
vspor879:30202332
vspor708:30202333
vspor363:30204092
pythonvspyl392:30422396
pythontb:30258533
pythonvspyt551cf:30291413
pythonptprofiler:30281269
vshan820:30294714
pythondataviewer:30285072
vscod805cf:30301675
pythonvspyt200:30323110
bridge0708:30335490
bridge0723:30353136
vsaa593:30376534
pythonvs932:30404738
wslgetstartedc:30421358
vscop453:30404998
vsclayoutctrc:30405799
pythonvsnew555:30426298
vscscmwlcmc:30428972
About this issue
- Original URL
- State: closed
- Created 2 years ago
- Comments: 17 (9 by maintainers)
Commits related to this issue
- Update ARIA label when clearing search Ref #142064 — committed to microsoft/vscode by rzhao271 2 years ago
@jvesouza “Save All” gets greyed out when there are no pending changes. So this is expected behaviour.
As for the initial “Clear” action being read as greyed I can reproduce this with VS Code insiders. I can not reproduce it with Chrome 98. So it seems like Chrome has fixed this issue in later versions. @jvesouza can you try going to https://vscode.dev/github/microsoft/vscode that will load up the vscode workbench and try to reproduce there in Chrome browser. It works for me. So it seems we just need to pick a later Chrome version with the fix.
@jvesouza awesome! The new issue you found sound like a VS Code bug. @rzhao271 can you verify if the clear action updates the
aria-labelproperly. It seems like thearia-labelgets stale with old results.Looks like another case of Orca getting events and silently updating focus. Will see what I can do.