-
Notifications
You must be signed in to change notification settings - Fork 6.8k
perf(focus-monitor): avoid triggering unnecessary change detections #18668
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
src/components-examples/cdk/a11y/focus-monitor-directives/focus-monitor-directives-example.html
Outdated
Show resolved
Hide resolved
src/components-examples/cdk/a11y/focus-monitor-directives/focus-monitor-directives-example.html
Outdated
Show resolved
Hide resolved
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
Please rebase, thanks! |
734d08a
to
20a56c9
Compare
20a56c9
to
eaa12a0
Compare
Needs rebase (sorry, this is taking a while due to failures internally) |
This was addressed in #15077. Closing. |
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. |
This is similar to #15077, but IMHO does it in much simpler way.
I also fixed up the documentation, examples, and some call sites that incorrectly stated that
FocusMonitor
emits the observable outside ofNgZone
.Caretaker note: #15077 had to be reverted before (#15076) because there was an app that depended on the extra change detections. We may have to investigate further before we can merge this in again.