bug(mat-error,mat-hint): mat-error and mat-hint display leading spaces
- Lingua principale
- TypeScript
- Stelle
- 25k
- Fork
- 6.8k
- Merge medio
- 1g 8h
- PR unite (30g)
- 91
Descrizione
### Is this a regression?
- [X] Yes, this behavior used to work in the previous version
### The previous version in which this bug was not present was
14.2.7
### Description
In versions pre mdc migration mat-hint and mat-error do NOT display leading spaces.
In versions post mdc migration mat-hint and mat-error do display leading spaces.
This behavior causes multi-line hints and errors to not align properly.
Of course this just a small thing an can be fixed by formatting the html differently but it is technically an undocumented breaking change. So i need to know if this is intended behavior and i have to fix it in my code or if it will be fixed in angular material.
Apparently there was already an issue for that #26430 but it was closed for not being reproducable but my StackBlitz Links show that it is still the case.
### Reproduction
Working StackBlitz link (14.2.7): https://stackblitz.com/edit/xxdwty?file=src%2Fapp%2Fform-field-appearance-example.html
Error StackBlitz link (16.2.1): https://stackblitz.com/edit/qopght?file=src%2Fexample%2Fform-field-appearance-example.html,src%2Findex.html
### Expected Behavior
Leading spaces are not displayed.
### Actual Behavior
Leading spaces are displayed.
### Environment
- Angular: 16
- CDK/Material: 16.2.1
- Browser(s): Chrome
- Operating System (e.g. Windows, macOS, Ubuntu): Windows
Guida per i contributori
Apri la guida per i contributori
Direzione di ricerca
Inizia con gli esempi StackBlitz collegati, confrontando src/app/form-field-appearance-example.html di Angular Material 14.2.7 con src/example/form-field-appearance-example.html e src/index.html della versione 16.2.1. Conferma il comportamento dello spazio iniziale in mat-hint e mat-error, quindi verifica che il comportamento previsto venga ripristinato senza compromettere l’allineamento su più righe.
Scritto dal modello di indicizzazione a partire dal testo della issue.
Valutazione
- Stack tecnologico
- angular, typescript
- Ambito
- frontend
- Tipo di issue
- Bug
- Difficoltà
- 3/5
- Tempo stimato
- 1-2 giorni
- Stato di attività
- Ferma
- Chiarezza
- Abbastanza chiara
- Idoneità per principianti
- 35/100