mdChips: with autocomplete minLength=0, list should not open automatically when a chip is removed.

[antoinebrault]

It feels weird that the list opens after a delete. And the list opens at the wrong place too.

[devversion]

Little codepen to see the current behavior: http://codepen.io/DevVersion/pen/vLzgeX?editors=1010 @antoinebrault What do you suggest for the behavior? it's the default behavior of the autocomplete. If we won't open it directly it wouldn't make sense to use that in an autcomplete, wrapped in <md-chips> except the validation.

[antoinebrault]

At least these points should be fixed:

• Focus is on the list and I have to click twice to delete an item
• List is positioned after the chip I just deleted instead of after the last chip.

Look at how select2 and chosen do it: https://harvesthq.github.io/chosen/#multiple-select List doesn't open until input is refocused after a add/delete. I can remove multiple chips quickly.

https://select2.github.io/examples.html#multiple List does open after a delete but I can remove multiple chips and the list stays open between deletes and doesn't move around.

Either way, it feels more natural than the current impl of chips/autocomplete.

[antoinebrault]

Any plans on fixing this?

[afreeland]

I am experiencing this issue as well. I feel that if a user selects the 'x' to remove the chip that the autocomplete should not be triggered. Are they any workarounds for this?

Also it appears that when I hit Esc that it closes the autocomplete and leaves me with my placeholder and a loading bar.

[ThomasBurleson]

This issue is closed as part of our ‘Surge Focus on Material 2' efforts. For details, see our forum posting @ http://bit.ly/1UhZyWs.