-
Notifications
You must be signed in to change notification settings - Fork 6.7k
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
feat(autocomplete): support variable option height #20324
feat(autocomplete): support variable option height #20324
Conversation
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Can you add a DEPRECATED
block to your commit message?
Historically `mat-select` and `mat-autocomplete` have behaved very similarly, because they were written around the same time and they share some logic by depending on `mat-option`. `mat-select` has to know all the option heights ahead of time so that it can position its panel correctly over the trigger. The limitation made its way into `mat-autocomplete`, even though there's no reason for it to be there. While implementing the MDC-based autocomplete, I refactored some code that makes it easier to support variable-height options so there changes enable the functionality for the non-MDC autocomplete too. DEPRECATED: * `AUTOCOMPLETE_OPTION_HEIGHT` is deprecated, because it isn't being used anymore. * `AUTOCOMPLETE_PANEL_HEIGHT` is deprecated, because it isn't being used anymore. Fixes angular#18030.
8c57673
to
f59a78a
Compare
Done. |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
LgTM
This issue has been automatically locked due to inactivity. Read more about our automatic conversation locking policy. This action has been performed automatically by a bot. |
Historically
mat-select
andmat-autocomplete
have behaved very similarly, because they were written around the same time and they share some logic by depending onmat-option
.mat-select
has to know all the option heights ahead of time so that it can position its panel correctly over the trigger. The limitation made its way intomat-autocomplete
, even though there's no reason for it to be there.While implementing the MDC-based autocomplete, I refactored some code that makes it easier to support variable-height options so these changes enable the functionality for the non-MDC autocomplete too.
DEPRECATED:
AUTOCOMPLETE_OPTION_HEIGHT
is deprecated, because it isn't being used anymore.AUTOCOMPLETE_PANEL_HEIGHT
is deprecated, because it isn't being used anymore.Fixes #18030.