-
Notifications
You must be signed in to change notification settings - Fork 29.1k
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
scrolling causes issues (code renderer CPU spike) when using a screenreader (like vimac) #110764
Comments
If anyone looks further into this may be worth looking here as well in case it's somehow related to vimac implementation (though im not sure how vimac would cause high cpu on the code renderer process) |
Thanks for the feedback. Do you see the same when you use vimac and chrome, for example this page https://bocupp-microsoft.github.io/sample-code/textarea/setselectionrange-performance.html If you see slowness then could you please file an issue against Chrome? |
I went to the link you sent and did not experience any issues there. Slack and Bitwarden (though bitwarden is pretty minimal so maybe a bad comparison) both run fine as well (cannot tell a difference when vimac is enabled vs disabled) |
Yes, It uses AXManualAccessibility to be able to read the element tree. |
This is likely a chromium accessibility performance issue, not a VSCode or electron one. See the original discussion on adding AXManualAccessibility: |
@dexterleng yes sounds like Chromium. Best would be if we could get reproducable steps for Chrome, so we can file an issue in the Chromium repository. |
Steps to Reproduce:
Does this issue occur when all extensions are disabled?: Yes
Note: I'm not entirely sure that vimac is a screenreader though i believe it is because when i first enabled it vscode displayed a message (only time ive ever seen this) mentioning
Controls whether the editor should run in a mode where it is optimized for screen readers
(setting this to on does not help btw)The text was updated successfully, but these errors were encountered: