-
Notifications
You must be signed in to change notification settings - Fork 6.8k
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
fix(a11y): avoid overlapping or left over timers in live announcer #13602
fix(a11y): avoid overlapping or left over timers in live announcer #13602
Conversation
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Good catch. LGTM
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
LGTM
3f7bc9e
to
69b7ea4
Compare
* Avoids timers overlapping in the `LiveAnnouncer`, which can happen if a new message is announced within 100ms of the previous one. This can be an issue if the screen reader started reading out the previous message and then gets interrupted by the new one. * Avoids leftover timers if the service is destroyed. * Fixes the reference to the `_liveElement` not being cleared after it's removed from the DOM, potentially leaving it in memory.
…13602) * Avoids timers overlapping in the `LiveAnnouncer`, which can happen if a new message is announced within 100ms of the previous one. This can be an issue if the screen reader started reading out the previous message and then gets interrupted by the new one. * Avoids leftover timers if the service is destroyed. * Fixes the reference to the `_liveElement` not being cleared after it's removed from the DOM, potentially leaving it in memory.
This issue has been automatically locked due to inactivity. Read more about our automatic conversation locking policy. This action has been performed automatically by a bot. |
LiveAnnouncer
, which can happen if a new message is announced within 100ms of the previous one. This can be an issue if the screen reader started reading out the previous message and then gets interrupted by the new one._liveElement
not being cleared after it's removed from the DOM, potentially leaving it in memory.