bug(mat-text-column): Column-name based CSS ignored unless view encapsulation is disabled
- Langage dominant
- TypeScript
- Étoiles
- 25k
- Forks
- 6.8k
- Merge moyen
- 1 j 8 h
- PR mergées (30 j)
- 91
Description
### Is this a regression?
- [ ] Yes, this behavior used to work in the previous version
### The previous version in which this bug was not present was
_No response_
### Description
May not technically be a bug, and more of an undocumented quirk.
There are two aspects to mat-table column definitions that lead to an unexpected conclusion:
- For a column named `foo`, you can define a `.mat-column-foo` style which will get applied to it.
- A `mat-text-column` named `foo` is shorthand for an explicit matColumnDef with sensible defaults for a text-only field.
However, if you define said style, and try to apply it to a mat-text-column, it won't match.
I supppose that technically, the affected th/td elements are no longer generated by the parent view, but by mat-text-node itself - and thus, those are outside the scope of view-encapsulated styles defined there.
The fix may not be trivial, but it might still be worth documenting as a gotcha.
### Reproduction
See StackBlitz [here](https://stackblitz.com/edit/components-issue-e4h1lq?file=src/app/example-component.ts). By making the component non-encapsulated, the style applies to both columns. Otherwise, it only matches the explicitly defined one, not the text-column.
### Expected Behavior
Styles affect matColumnDefs and mat-text-columns the same way.
### Actual Behavior
...they don't!
### Environment
Angular CLI: 13.3.5
Node: 14.17.6
Package Manager: yarn 1.22.15
OS: win32 x64
Angular: 13.3.6
Guide de contribution
Ouvrir le guide de contribution
Piste de recherche
Commencez par la reproduction StackBlitz liée et inspectez src/app/example-component.ts, en comparant la matColumnDef définie explicitement avec la mat-text-column sous view encapsulation. Confirmez la différence de style et déterminez si le résultat attendu est une correction du composant ou la documentation du comportement ; c'est terminé lorsque les deux types de colonnes reçoivent des styles équivalents ou que la limitation est documentée.
Rédigé par le modèle d'indexation à partir du texte de l'issue.
Évaluation
- Stack technique
- angular, typescript
- Domaine
- frontend
- Type d'issue
- Bug
- Difficulté
- 4/5
- Temps estimé
- 3-5 jours
- Activité
- À l'abandon
- Clarté
- Plutôt claire
- Accessibilité débutants
- 38/100