-
-
Notifications
You must be signed in to change notification settings - Fork 133
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
Angular 16: Search field acting weird? #425
Comments
@GipHub123 are you using the legacy field or the mdc based ones? See #411 |
Sorry that original description was missing this important detail. I'm using newer MDC based components imported from |
Same issue, also using newer MDC based one |
Can you please provide more information about which package versions you use, a screenshot, an example template etc? Ideally could you create a stackblitz example? |
Updating all the dependencies and removing line 27 of polyfills.ts in the stackblitz provided in the readme replicates the issue: https://stackblitz.com/github/bithost-gmbh/ngx-mat-select-search-example |
ok, could confirm, it seems to have changed since I last tested with Material Version: 16.0.0-next.2 (where it worked fine) |
fixed with version 7.0.2, thanks for reporting! |
… release 7.0.2 (bithost-gmbh#426) (cherry picked from commit e83532d) accepting these changes not sure whether good for legacy
Describe the bug
ngx-mat-select-search acting weird after updating angular 16.0.0.
Field looked like disabled / clear button didn't do anything. I rolled back to version 15 and search field started to work as expected.
It looked like some changes has been made to the Material's select -component.
https://github.com/angular/components/tree/main/src/material/select
Can anyone else confirm this or it's just me doing something stupid?
The text was updated successfully, but these errors were encountered: