Esteban Gehring
Esteban Gehring
@guilhermecostalopes do you want to explore a solution and implementation?
The implementation essentially is a search field, leaving it up to the consumers to appropriately filter the options.
thanks for reporting this issue. do you want to try to find a fix?
I havent tested that, but do you want to create a PR and test that this works properly?
@paulflo150 would you like to prepare a PR?
@radanax thanks for reporting this. Can you investigate and provide a fix?
@radanax would you want to test version 7.0.0 using the new MatSelectModule and check whether this is still an issue?
can you try to ensure the selected option is always present among the `mat-option` elements? otherwise it is de-selected by `mat-select`. so maybe it would be enough to conditionally enable...
~~Here is an implementation using mat-select: https://mat-select-search.stackblitz.io Code: https://stackblitz.com/edit/mat-select-search?file=app%2Fmat-select-search%2Fmat-select-search.component.ts~~ See https://github.com/bithost-gmbh/ngx-mat-select-search  @jelbourn @crisbeto might this be worth filing as a PR once https://github.com/angular/material2/issues/2812 / https://github.com/angular/material2/pull/7835 is ready?
@eyalhakim Thanks for your feedback. I added an example with `[multiple]=true` and adapted the implementation of the `mat-select-search` to fix the behavior you described in https://github.com/angular/material2/issues/5697#issuecomment-365005477 > when using the...