AccessibilityManager's handleKey should be triggered by onData, not onKey #5221
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.
Issue:
In Android, screen reader feature sometimes generates the voice output including previous content
Reason:
_liveRegion.textContent
from previous command is supposed be cleaned up in key stroke event, but onKey doesn't work as intended with IME(except 'enter' in Android) as mentioned in #3025. So the voice output includes previous content.Fix:
As @Tyriars said in #3025, use
onData
instead ofonKey