-
Notifications
You must be signed in to change notification settings - Fork 6.8k
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
Feature for mat-paginator; [disableOptionCentering] #13646
Comments
This should be easy enough to add, but I'm not sure how practical it would be to continue doing it. Eventually we'd end up proxying every single input on |
Hello, @crisbeto, @mibrezovec , Best regards Matthew |
Afaik, not assigned atm, you can take it @krivkoo |
Will you assign it to me or will I do it? @mibrezovec |
Please feel free to do it yourself, I am new here and uncertain if I can assign you if I'm not an admin. @krivkoo |
Since we hide the underlying `MatSelect` inside the `MatPaginator`, the user doesn't have the ability to configure some of the inputs. These changes introduce an input that proxy some of the supported properties to the select. Fixes angular#13646.
Since we hide the underlying `MatSelect` inside the `MatPaginator`, the user doesn't have the ability to configure some of the inputs. These changes introduce an input that proxy some of the supported properties to the select. Fixes angular#13646.
Since we hide the underlying `MatSelect` inside the `MatPaginator`, the user doesn't have the ability to configure some of the inputs. These changes introduce an input that proxy some of the supported properties to the select. Fixes #13646.
Since we hide the underlying `MatSelect` inside the `MatPaginator`, the user doesn't have the ability to configure some of the inputs. These changes introduce an input that proxy some of the supported properties to the select. Fixes angular#13646.
Since we hide the underlying `MatSelect` inside the `MatPaginator`, the user doesn't have the ability to configure some of the inputs. These changes introduce an input that proxy some of the supported properties to the select. Fixes angular#13646.
Since we hide the underlying `MatSelect` inside the `MatPaginator`, the user doesn't have the ability to configure some of the inputs. These changes introduce an input that proxy some of the supported properties to the select. Fixes angular#13646.
Since we hide the underlying `MatSelect` inside the `MatPaginator`, the user doesn't have the ability to configure some of the inputs. These changes introduce an input that proxy some of the supported properties to the select. Fixes angular#13646.
Since we hide the underlying `MatSelect` inside the `MatPaginator`, the user doesn't have the ability to configure some of the inputs. These changes introduce an input that proxy some of the supported properties to the select. Fixes angular#13646.
Since we hide the underlying `MatSelect` inside the `MatPaginator`, the user doesn't have the ability to configure some of the inputs. These changes introduce an input that proxy some of the supported properties to the select. Fixes angular#13646.
Just a heads up that we kicked off a community voting process for your feature request. There are 20 days until the voting process ends. Find more details about Angular's feature request process in our documentation. |
Thank you for submitting your feature request! Looks like during the polling process it didn't collect a sufficient number of votes to move to the next stage. We want to keep Angular rich and ergonomic and at the same time be mindful about its scope and learning journey. If you think your request could live outside Angular's scope, we'd encourage you to collaborate with the community on publishing it as an open source package. You can find more details about the feature request process in our documentation. |
…lect Since we hide the underlying `MatSelect` inside the `MatPaginator`, the user doesn't have the ability to configure some of the inputs. These changes introduce an input that proxy some of the supported properties to the select. Fixes angular#13646.
…lect Since we hide the underlying `MatSelect` inside the `MatPaginator`, the user doesn't have the ability to configure some of the inputs. These changes introduce an input that proxy some of the supported properties to the select. Fixes angular#13646.
…lect Since we hide the underlying `MatSelect` inside the `MatPaginator`, the user doesn't have the ability to configure some of the inputs. These changes introduce an input that proxy some of the supported properties to the select. Fixes angular#13646.
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. |
…lect (angular#13705) Since we hide the underlying `MatSelect` inside the `MatPaginator`, the user doesn't have the ability to configure some of the inputs. These changes introduce an input that proxy some of the supported properties to the select. Fixes angular#13646.
Bug, feature request, or proposal:
As any mat-select, mat-select inside the mat-paginator should be able to use [disableOptionCentering].
What is the expected behavior?
Something on the lines of
<mat-paginator [disableOptionCentering]="true" [length]="pageLength" </mat-paginator>
Adding the [disableOptionCentering] should be possible and working as intended (like with any other mat-select). See mat-select API for detailed explanation.
What is the current behavior?
It's not possible. mat-paginator API
What are the steps to reproduce?
https://material.angular.io/components/paginator/overview
Select options from the "Items per page", the chosen option will be in the "dropdown" center.
What is the use-case or motivation for changing an existing behavior?
It should be posibble to use [disableOptionCentering] with any mat-selects, even if in a paginator.
Which versions of Angular, Material, OS, TypeScript, browsers are affected?
All that support mat-paginators I guess.
Is there anything else we should know?
Nope.
The text was updated successfully, but these errors were encountered: