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
The mat-paginator is usually used above or under a collection, table, etc.
Therefore display: block; should be used to render correctly its width and borders if modified externally by the .mat-paginator selector.
What is the current behavior?
There is no display style property defined on the host.
What is the use-case or motivation for changing an existing behavior?
The mat-paginator is usually used above or under a collection, table, etc.
Therefore display: block; should be used to render correctly its width and borders if modified externally by a .mat-paginator selector.
Which versions of Angular, Material, OS, TypeScript, browsers are affected?
Bug, feature request, or proposal:
Proposal
What is the expected behavior?
The mat-paginator is usually used above or under a collection, table, etc.
Therefore
display: block;
should be used to render correctly its width and borders if modified externally by the.mat-paginator
selector.What is the current behavior?
There is no
display
style property defined on the host.What are the steps to reproduce?
You can actually see that the style property is missing in the source code:
https://github.com/angular/material2/blob/master/src/lib/paginator/paginator.scss
https://github.com/angular/material2/blob/master/src/lib/paginator/paginator.ts
What is the use-case or motivation for changing an existing behavior?
The mat-paginator is usually used above or under a collection, table, etc.
Therefore
display: block;
should be used to render correctly its width and borders if modified externally by a.mat-paginator
selector.Which versions of Angular, Material, OS, TypeScript, browsers are affected?
Angular: 5.0.0
Material2: 5.0.0-rc0
OS: Debian 8
TypeScript: 2.4.2
Browser: Chrome, Firefox, etc.
Is there anything else we should know?
No
The text was updated successfully, but these errors were encountered: