-
Notifications
You must be signed in to change notification settings - Fork 6.8k
fix(autocomplete): not emitting opened event if options come in after open #15582
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(autocomplete): not emitting opened event if options come in after open #15582
Conversation
if (this.panelOpen) { | ||
this._overlayRef!.updatePosition(); | ||
|
||
if (wasOpen !== this.panelOpen) { |
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.
Add a comment here that captures the context for this PR?
1f4a42c
to
e5f62b7
Compare
Addressed the feedback @jelbourn. |
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
@crisbeto this passes presubmit, just needs a rebase |
… open Fixes `mat-autocomplete` not emitting its `opened` event if it is opened without any options and then the options come in at a later point. Fixes angular#15573.
Rebased. |
e5f62b7
to
face478
Compare
… open (angular#15582) Fixes `mat-autocomplete` not emitting its `opened` event if it is opened without any options and then the options come in at a later point. Fixes angular#15573.
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. |
Fixes
mat-autocomplete
not emitting itsopened
event if it is opened without any options and then the options come in at a later point.Fixes #15573.