-
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
bug(MatTable): *matNoDataRow not properly styling in flex mode #22349
bug(MatTable): *matNoDataRow not properly styling in flex mode #22349
Comments
In an earlier PR we switched the flex-based table styles to target the tag names, rather than classes in order to support flex tables in MDC. The problem with targeting tag names is that it doesn't allow our styles to be applied to other elements within the table. E.g. in angular#22349 the user isn't able to target the "no data" row. These changes switch back to targeting classes and add some styles to prevent the flex-specific styles from bleeding into the table-based ones. Fixes angular#22349.
In an earlier PR we switched the flex-based table styles to target the tag names, rather than classes in order to support flex tables in MDC. The problem with targeting tag names is that it doesn't allow our styles to be applied to other elements within the table. E.g. in angular#22349 the user isn't able to target the "no data" row. These changes switch back to targeting classes and add some styles to prevent the flex-specific styles from bleeding into the table-based ones. Fixes angular#22349.
…es (#22350) In an earlier PR we switched the flex-based table styles to target the tag names, rather than classes in order to support flex tables in MDC. The problem with targeting tag names is that it doesn't allow our styles to be applied to other elements within the table. E.g. in #22349 the user isn't able to target the "no data" row. These changes switch back to targeting classes and add some styles to prevent the flex-specific styles from bleeding into the table-based ones. Fixes #22349.
…es (#22350) In an earlier PR we switched the flex-based table styles to target the tag names, rather than classes in order to support flex tables in MDC. The problem with targeting tag names is that it doesn't allow our styles to be applied to other elements within the table. E.g. in #22349 the user isn't able to target the "no data" row. These changes switch back to targeting classes and add some styles to prevent the flex-specific styles from bleeding into the table-based ones. Fixes #22349. (cherry picked from commit c76a09e)
In an earlier PR we switched the flex-based table styles to target the tag names, rather than classes in order to support flex tables in MDC. The problem with targeting tag names is that it doesn't allow our styles to be applied to other elements within the table. E.g. in angular#22349 the user isn't able to target the "no data" row. These changes switch back to targeting classes and add some styles to prevent the flex-specific styles from bleeding into the table-based ones. Fixes angular#22349.
Does the commit include a fix for this error when using matNoDataRow on a flex table or do I need to submit a new issue?
Broken
Works
|
Hello, this bug still exists in Angular 14.2.6. Will it be fixed someday? |
It seems it exists in 15 |
Reproduction
Steps to reproduce:
*matNoDataRow
in a flexMatTable
Expected Behavior
No Data Row is properly styled with a padding, like in the non-flex table:
Actual Behavior
No Data Row is missing proper styling:
Additional information
The code for the *matNoDataRow in non-flex tables is part of the documentation:
But how to do it with the flex table? I've tried several things, no luck so far:
Sure I could add the styles manually, but I was hoping that there was an official solution.
Environment
The text was updated successfully, but these errors were encountered: