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.

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

Rendering issue for settings with type "object" #213717

Closed
Yoyokrazy opened this issue May 28, 2024 · 2 comments · Fixed by #213826
Closed

Rendering issue for settings with type "object" #213717

Yoyokrazy opened this issue May 28, 2024 · 2 comments · Fixed by #213826
Assignees
Labels
insiders-released Patch has been released in VS Code Insiders
Milestone

Comments

@Yoyokrazy
Copy link
Contributor

Yoyokrazy commented May 28, 2024

Testing #213344

When hovering over any setting with the "object" structure there is a rendering issue on the right side of the row. See screenshot attached.

image

@Yoyokrazy Yoyokrazy assigned meganrogge and rzhao271 and unassigned meganrogge May 28, 2024
@Yoyokrazy Yoyokrazy changed the title Rendering issue while screen reader optimized and running NVDA Rendering issue for settings with type "object" May 28, 2024
@Yoyokrazy
Copy link
Contributor Author

Edit: this effects all settings with type "object", not related to screen readers. Repros with all screen reader related apps turned off.

@AP1400

This comment has been minimized.

@rzhao271 rzhao271 added this to the May 2024 milestone May 29, 2024
@vscodenpa vscodenpa added unreleased Patch has not yet been released in VS Code Insiders insiders-released Patch has been released in VS Code Insiders and removed unreleased Patch has not yet been released in VS Code Insiders labels May 29, 2024
@microsoft microsoft locked and limited conversation to collaborators Jul 13, 2024
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
insiders-released Patch has been released in VS Code Insiders
Projects
None yet
Development

Successfully merging a pull request may close this issue.

5 participants