Conversation
amanmahajan7
approved these changes
Apr 6, 2026
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
I was checking out an example in the mdn docs that slowed down my entire OS for a few seconds for some reason, regardless of the browser I tried. With Claude's help, I found out that the browser sends accessibility notifications on DOM changes via synchronous cross-process COM calls, and the desktop renderer depends on that same synchronous interface, which is why the entire OS became sluggish. In my specific case though, the Claude desktop app registers itself as a "listener/consumer", as if it's a screen reader, so Chrome automatically turned on accessibility modes and sent notifications on DOM changes.
Thankfully these accessibility features can be disabled in Chromium/Firefox.
It improves test perf a little bit, at least on Windows, especially when an app enables such accessibility modes and tests are DOM-heavy, and may reduce memory usage.
You can also check Chrome's accessibility internals in
chrome://accessibility/, where you can enable/disable these modes.Before/after for
npm t editcell keyboard, notice how Firefox does not seem affected, while on ChromekeyboardNavigation.test.tsxis ~1000ms slower andrenderEditCell.test.tsxis ~600ms slower.Running
channel: 'chromium'is most likely related too.Slowdown comparison:
Before, with the Claude desktop app closed
Before, with the Claude desktop app open
After, with the Claude desktop app open
After, with the Claude desktop app closed