Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

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

Jump to bottom

by default, auto expand variables when debugging in screen reader mode #221512

Closed
meganrogge opened this issue Jul 11, 2024 · 0 comments · Fixed by #221513
Closed

by default, auto expand variables when debugging in screen reader mode #221512

meganrogge opened this issue Jul 11, 2024 · 0 comments · Fixed by #221513
Assignees
@meganrogge
Labels
accessibility Keyboard, mouse, ARIA, vision, screen readers (non-specific) issues debug Debug viewlet, configurations, breakpoints, adapter issues feature-request Request for new features or functionality insiders-released Patch has been released in VS Code Insiders
Milestone
July 2024

Comments

@meganrogge
Copy link
Contributor

We lazy load variables by default with a mouse click action to resolve and expand them. That behavior can be changed via debug.autoExpandLazyVariables. When in screen reader mode, we should do that by default, but allow users to set that to off if it impacts perf too much.

Thus, we'll have a new format for the setting, auto | on | off.
@meganrogge meganrogge self-assigned this Jul 11, 2024
@meganrogge meganrogge added feature-request Request for new features or functionality debug Debug viewlet, configurations, breakpoints, adapter issues accessibility Keyboard, mouse, ARIA, vision, screen readers (non-specific) issues labels Jul 11, 2024
@meganrogge meganrogge added this to the July 2024 milestone Jul 11, 2024
meganrogge added a commit that referenced this issue Jul 11, 2024
@meganrogge
fix #221512
94d0e3f
@meganrogge meganrogge mentioned this issue Jul 11, 2024
Merged
@Macyoutuber Macyoutuber mentioned this issue Jul 11, 2024
Closed
@VSCodeTriageBot VSCodeTriageBot added the unreleased Patch has not yet been released in VS Code Insiders label Jul 11, 2024
@VSCodeTriageBot VSCodeTriageBot added insiders-released Patch has been released in VS Code Insiders and removed unreleased Patch has not yet been released in VS Code Insiders labels Jul 12, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees

@meganrogge meganrogge

Labels
accessibility Keyboard, mouse, ARIA, vision, screen readers (non-specific) issues debug Debug viewlet, configurations, breakpoints, adapter issues feature-request Request for new features or functionality insiders-released Patch has been released in VS Code Insiders
Projects
None yet
Milestone
July 2024
2 participants
@meganrogge @VSCodeTriageBot