-
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
bug(MatAutocompleteTrigger): callback applied to closed EventEmitter runs outside of the Angular Zone on outside click #24811
Comments
looks like the root cause comes from |
Fixes a bug in Angular Material `autocomplete` when outside click doesn't trigger `changeDetection`. Fixes angular#24811
Fixes a bug in Angular Material `autocomplete` when outside click doesn't trigger `changeDetection`. Fixes angular#24811
Fixes a bug in Angular Material `autocomplete` when outside click doesn't trigger `changeDetection`. Fixes angular#24811
Fixes a bug in Angular Material `autocomplete` when outside click doesn't trigger `changeDetection`. Fixes angular#24811
Fixes a bug in Angular Material `autocomplete` when outside click doesn't trigger `changeDetection`. Fixes angular#24811
Fixes a bug in Angular Material `autocomplete` when outside click doesn't trigger `changeDetection`. Fixes #24811
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. |
Is this a regression?
The previous version in which this bug was not present was
No response
Description
The callback applied to the
closed
EventEmitter seems to run outside of the Angular Zone whenclosed
is emitted via "outside click"Reproduction
https://stackblitz.com/edit/components-issue-83t6vu?file=src/app/autocomplete.component.ts
Steps to reproduce:
Expected Behavior
clicking outside the panel to close the panel should have disabled the button without using
ngZone.run()
Actual Behavior
the button remains disabled
Environment
The text was updated successfully, but these errors were encountered: