vscode: I can't edit a breakpoint expression using orca.
Issue Type: Bug
CC: @isidorn @joanmarie
-
Launch orca.
-
Launch vscode.
-
Create a .js file.
-
Insert the following code:
<a = 1> -
Activate the run menu.
-
Expand the new breakpoint menu.
-
Choose the log point option.
-
Type for example “this is a test”.
-
Try to review the typed text using left and right arrow.
In my environment nothing is read by orca.
VS Code version: Code - Insiders 1.50.0-insider (bc38b0accb3c62180317c63dbe7323200977db0f, 2020-09-11T12:27:36.137Z) OS version: Linux x64 5.8.7-arch1-1
System Info
| Item | Value |
|---|---|
| CPUs | Intel® Core™ i5-5200U CPU @ 2.20GHz (4 x 2494) |
| GPU Status | 2d_canvas: enabled flash_3d: enabled flash_stage3d: enabled flash_stage3d_baseline: enabled gpu_compositing: enabled multiple_raster_threads: enabled_on oop_rasterization: disabled_off opengl: enabled_on protected_video_decode: unavailable_off rasterization: disabled_software skia_renderer: enabled_on video_decode: unavailable_off vulkan: disabled_off webgl: enabled webgl2: enabled |
| Load (avg) | 2, 1, 1 |
| Memory (System) | 7.68GB (0.46GB free) |
| Process Argv | . --no-sandbox --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 |
About this issue
- Original URL
- State: closed
- Created 4 years ago
- Comments: 18 (7 by maintainers)
Commits related to this issue
- fixes #106505 — committed to jmannanc/vscode by isidorn 4 years ago
It looks great. @joanmarie @isidorn Thanks, great job.
Thanks @joanmarie for looking more into this and for the write-up.
Motivation for allowing hidden elements to emit text events: there might be use cases like vscode that use a rich editor on top, but have hidden textArea fields just for accessibility. Not sure if anyone else is currently doing this pattern, but I can imagine others doing the same.
What I do not understand is why this works for our regular editor but does not work for the breakpoint edit box? What is different between those two? Since on our side we use the same editor widget in both cases that use a hidden
textAreaelement.If there is a change to be backported from Chrome let me know and we can try to do it no problem.
Thanks!
@isidorn I’ll see if I can dig into it from the Chromium side of things. Working on a different Chromium bug atm which I need to finish first, however. If you don’t make progress and I space it out, please ping me.