-
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] mat-autocomplete doesn't close using displayWith under IE11 #9479
Labels
P3
An issue that is relevant to core functions, but does not impede progress. Important, but not urgent
Comments
crisbeto
added a commit
to crisbeto/material2
that referenced
this issue
Jan 21, 2018
…ith an empty string display value Fixes the autocomplete panel reopening on IE11 when the user selects an option whose display value is an empty string. Fixes angular#9479.
crisbeto
added a commit
to crisbeto/material2
that referenced
this issue
Jan 24, 2018
…ith an empty string display value Fixes the autocomplete panel reopening on IE11 when the user selects an option whose display value is an empty string. Fixes angular#9479.
crisbeto
added a commit
to crisbeto/material2
that referenced
this issue
Feb 2, 2018
…ith an empty string display value Fixes the autocomplete panel reopening on IE11 when the user selects an option whose display value is an empty string. Fixes angular#9479.
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. |
Sign up for free
to subscribe to this conversation on GitHub.
Already have an account?
Sign in.
Labels
P3
An issue that is relevant to core functions, but does not impede progress. Important, but not urgent
Bug, feature request, or proposal:
Bug
Similar to: #5165 (not duplicate)
What is the expected behavior?
mat-autocomplete-panel should be close after selected an option
What is the current behavior?
mat-autocomplete-panel continues to be opened even after to have selected an option
What are the steps to reproduce?
Run the stackblitz: https://stackblitz.com/edit/angular-gieptd
Which versions of Angular, Material, OS, TypeScript, browsers are affected?
Angular 5.2.0
Node: 8.6.0
MAterial: 5.1.0
Windows 7 Pro 64 bits
TypeScript: 2.6.2
NB: For the moment, the workaround consists to use the reset function available on the formControl. IE11 worls properly in this context
The text was updated successfully, but these errors were encountered: