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
There should be a way to style the panel created by the autocomplete component.
What is the current behavior?
The mat-autocomplete-panel div is added dynamically, outside the current component. The only way to specify styles would be to use a /deep/ selector. But this only works globally, so there would be no way to style the panels of individual autocompletes.
What are the steps to reproduce?
Any use of mat-autocomplete.
What is the use-case or motivation for changing an existing behavior?
Sizing is one possible use case for specifying styles on the autocomplete panel. Current behavior will truncate the options if their widths exceed the width of the panel. Adding a style to the panel such as min-width: fit-content would be a desirable solution.
Which versions of Angular, Material, OS, TypeScript, browsers are affected?
All versions.
Is there anything else we should know?
The solution should be essentially the same as #4485
The text was updated successfully, but these errors were encountered:
Bug, feature request, or proposal:
Feature request
What is the expected behavior?
There should be a way to style the panel created by the autocomplete component.
What is the current behavior?
The mat-autocomplete-panel div is added dynamically, outside the current component. The only way to specify styles would be to use a
/deep/
selector. But this only works globally, so there would be no way to style the panels of individual autocompletes.What are the steps to reproduce?
Any use of mat-autocomplete.
What is the use-case or motivation for changing an existing behavior?
Sizing is one possible use case for specifying styles on the autocomplete panel. Current behavior will truncate the options if their widths exceed the width of the panel. Adding a style to the panel such as
min-width: fit-content
would be a desirable solution.Which versions of Angular, Material, OS, TypeScript, browsers are affected?
All versions.
Is there anything else we should know?
The solution should be essentially the same as #4485
The text was updated successfully, but these errors were encountered: