bug(mat-text-column): Column-name based CSS ignored unless view encapsulation is disabled
- Lenguaje dominante
- TypeScript
- Estrellas
- 25k
- Forks
- 6.8k
- Merge medio
- 1 d 8 h
- PR fusionados (30 d)
- 91
Descripción
### 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
Guía de contribución
Línea de trabajo
Comienza con la reproducción vinculada de StackBlitz e inspecciona src/app/example-component.ts, comparando la matColumnDef definida explícitamente con la mat-text-column bajo view encapsulation. Confirma la discrepancia de estilos y determina si el resultado previsto es una corrección del componente o la documentación del comportamiento; se considera terminado cuando ambos tipos de columna reciben estilos equivalentes o se documenta la limitación.
Escrito por el modelo de indexación a partir del texto del issue.
Evaluación
- Stack tecnológico
- angular, typescript
- Área
- frontend
- Tipo de issue
- Error
- Dificultad
- 4/5
- Tiempo estimado
- 3-5 días
- Estado de actividad
- Estancado
- Claridad
- Bastante claro
- Aptitud para principiantes
- 38/100