You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
This issue is a side affect/related of a long discussed issue with scrolling behaviour of the autocomplete panel (e.g. #10079).
The autocomplete panel is bound to the html/body - perhaps to fix this issue in the context with chips, a click (focus) on chip/remove could just close the autocomplete panel.
And the scrolling schould be disabled for the underlying div (#26048)
@RobinKamps
I have read these issues, and they have a solution with cdkScrollable.
I hope that for the issue is a similar solution with an internal mechanism.
I thought about using methods like openPanel() or *ngIf with a custom flag, but I think it's a not well solution.
Thanks for your reply!
@Satlykov
yes - cdkScrollable could be used as a performance breaking workaround for the scrolling issue, but it does not work on this chip remove issue, since there is no scrolling involved, if a chip remove button is clicked.
Perhaps its an option for you to add viewchild and close the autocomplete panel on chip remove.
Like:
Is this a regression?
The previous version in which this bug was not present was
No response
Description
When remove chips, we don't have trigger for change position mat-autocomplete.
Reproduction
Steps to reproduce:
Expected Behavior
Update the position mat-autocomplete when resizing the area of chips.
Actual Behavior
After deleting chips, mat-autocomplete does not change position.
Environment
The text was updated successfully, but these errors were encountered: