fix: disable AutoDisableAccessibility feature #169201
Merged
Conversation
This file contains 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
jrieken
approved these changes
Dec 15, 2022
deepak1556
added a commit
that referenced
this pull request
Dec 20, 2022
aeschli
pushed a commit
that referenced
this pull request
Dec 20, 2022
Sign up for free
to subscribe to this conversation on GitHub.
Already have an account?
Sign in.
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.
Fixes #169000
The feature disables a11y support in the runtime if there is no a11y api usage for 30s since receiving a user input, most scenarios described in the above issue indicate that the runtime is not sending a11y events to us when it detects usage after gaining focus from a different application indicating a bug in the runtime. Created #169200 to track re-enabling this feature.
/cc @isidorn @meganrogge