-
Notifications
You must be signed in to change notification settings - Fork 6.8k
refactor(live-announcer): run outside NgZone #10631
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
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.
LGTM, I would actually categorize this as a fix
@crisbeto Please rebase. Thanks |
Rebased. |
8d3d271
to
5b75144
Compare
5b75144
to
51400b1
Compare
Hi @crisbeto! This PR has merge conflicts due to recent upstream merges. |
51400b1
to
a02075f
Compare
Hi @crisbeto! This PR has merge conflicts due to recent upstream merges. |
Switches to running the timeout from the `LiveAnnouncer` outside the `NgZone`, because it does all of its DOM manipulation directly on the element and it doesn't have to trigger Angular's change detection.
a02075f
to
bba3f07
Compare
Switches to running the timeout from the `LiveAnnouncer` outside the `NgZone`, because it does all of its DOM manipulation directly on the element and it doesn't have to trigger Angular's change detection.
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. |
Switches to running the timeout from the
LiveAnnouncer
outside theNgZone
, because it does all of its DOM manipulation directly on the element and it doesn't have to trigger Angular's change detection.