Skip to content
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

Changing the autocomplete on a trigger does not change the overlay (options) #13812

Closed
thomaspink opened this issue Oct 25, 2018 · 5 comments · Fixed by #13814
Closed

Changing the autocomplete on a trigger does not change the overlay (options) #13812

thomaspink opened this issue Oct 25, 2018 · 5 comments · Fixed by #13814
Assignees
Labels
P3 An issue that is relevant to core functions, but does not impede progress. Important, but not urgent

Comments

@thomaspink
Copy link
Contributor

Bug, feature request, or proposal:

Changing the autocomplete on a trigger does not change the options in the overlay.

What is the expected behavior?

When changing the autocomplete (dtAutocomplete input) on a trigger, the overlay should display the new options.

What is the current behavior?

When changing the autocomplete (dtAutocomplete input) on a trigger, the overlay options
are still the initial ones.

What are the steps to reproduce?

https://stackblitz.com/edit/angular-7djgzt?file=app%2Fautocomplete-simple-example.html

Which versions of Angular, Material, OS, TypeScript, browsers are affected?

Current

@manklu
Copy link

manklu commented Oct 25, 2018

You could simply switch between the lists.

https://stackblitz.com/edit/angular-7djgzt-bzagsq

@thomaspink
Copy link
Contributor Author

thomaspink commented Oct 25, 2018

Yes i know, but this does not show the issue.
This also only works if the options of the 2 array have the same form.

crisbeto added a commit to crisbeto/material2 that referenced this issue Oct 25, 2018
Fixes the menu trigger being locked into the first menu panel that is passed in, after it has been opened at least once.

Fixes angular#13812.
crisbeto added a commit to crisbeto/material2 that referenced this issue Oct 25, 2018
Fixes the menu trigger being locked into the first menu panel that is passed in, after it has been opened at least once.

Relates to angular#13812.
crisbeto added a commit to crisbeto/material2 that referenced this issue Oct 25, 2018
Fixes the menu trigger being locked into the first menu panel that is passed in, after it has been opened at least once.

Relates to angular#13812.
@manklu
Copy link

manklu commented Oct 25, 2018

@thomaspink
Copy link
Contributor Author

thomaspink commented Oct 25, 2018

This example is there to show the issue of not updating the template/portal when changing the autocomplete panel. Workarounds/other solutions of course work but do not solve this issue.

jelbourn pushed a commit that referenced this issue Nov 3, 2018
Fixes the menu trigger being locked into the first menu panel that is passed in, after it has been opened at least once.

Relates to #13812.
atscott pushed a commit to atscott/components that referenced this issue Nov 5, 2018
Fixes the menu trigger being locked into the first menu panel that is passed in, after it has been opened at least once.

Relates to angular#13812.
jelbourn pushed a commit that referenced this issue Nov 6, 2018
Fixes the menu trigger being locked into the first menu panel that is passed in, after it has been opened at least once.

Relates to #13812.
@andrewseguin andrewseguin added the P3 An issue that is relevant to core functions, but does not impede progress. Important, but not urgent label May 30, 2019
@angular-automatic-lock-bot
Copy link

This issue has been automatically locked due to inactivity.
Please file a new issue if you are encountering a similar or related problem.

Read more about our automatic conversation locking policy.

This action has been performed automatically by a bot.

@angular-automatic-lock-bot angular-automatic-lock-bot bot locked and limited conversation to collaborators Sep 10, 2019
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
Projects
None yet
4 participants