angular / angular/components

bug: mat-chip color is not working properly within mat-chip-list & mat-form-field

Ouverte
#9,851 19 commentaires 18 réactions 0 personnes assignées Voir sur GitHub
area: material/chips needs investigation P3
Langage dominant
TypeScript
Étoiles
25k
Forks
6.8k
Merge moyen
1 j 8 h
PR mergées (30 j)
91

Description

#### Scenario

I have a simple input field that have an async autocomplete feature in order to add an email of a set of users. The added email will be illustrated in form of mat-chip within a mat-chip-list.

#### Bug
I have in my template an mat-form-field element that conatins a mat-chip-list element.
Within the mat-chip-list element i have also nested elements including the mat-chip element and an input as well as an mat-autocomplete element.

The color input of mat-chip is eql "accent", however the color is correct if i add an element to the list using the matChipInputTokenEnd event. Else, all chip's color are reset to the default one, e.g: if I add an item to the mat-chip-list using the auto complete feature...
This is very strange and therefore i provide the code and a gif below.
PS: selected input is eql `true`.

To confirm that the mat-chip works normally without the combination explained above,
i added a stand alone mat-chip (primary color - indigo) above the mat-chip-list and this works as expected. Furthermore, i added a static mat-chip ("testing") within the mat-chip-list with an accent color. This is not working too!

#### What is the expected behavior?

all chips should be with the color entered --> "accent" !!!

#### What is the current behavior?

#### What are the steps to reproduce?

```html

testing



testing


{{email}}
cancel




{{ user.email }}
({{user.displayName}})



Bitte geben Sie eine gültige E-Mail-Adresse ein




```

```ts
....
@ViewChild('emailsInput') emailsInputElement: ElementRef;

public add(event: MatChipInputEvent): void {
const input = event.input;
const value = event.value;

// Add an email
if ((value || '').trim() && this.validateEmail(value)) {
this.userEmails.push(value.trim());
this.emailsInputElement.nativeElement.value = '';
}
}

public test($event: MatAutocompleteSelectedEvent) {
console.log('on optionSelected: ', $event.option.value);
this.userEmails.push($event.option.value.trim());
this.searchValue = '';
this.emailsInputElement.nativeElement.value = '';
console.log('emails array: ', this.userEmails);
}

public remove(email: any): void {
const index = this.userEmails.indexOf(email);

if (index >= 0) {
this.userEmails.splice(index, 1);
}
}

}

```

#### Which versions of Angular, Material, OS, TypeScript, browsers are affected?
- Angular v5.2.3
- Material v5.1.0
- OS: MacOS high Sierra
- TS v2.4.2
- Browsers: tested on chrome and firefox (not working!)

#### Is there anything else we should know?

![feb-08-2018 22-43-04](https://user-images.githubusercontent.com/20149774/35999983-d2f2ac0c-0d21-11e8-953b-6100d8dd11c4.gif)

Guide de contribution

Ouvrir le guide de contribution

Piste de recherche

Commencez par reproduire la réinitialisation de couleur signalée avec le template fourni contenant mat-chip-list, mat-form-field, input et mat-autocomplete sur Angular 5.2.3 et Material 5.1.0. Suivez la gestion de la couleur de mat-chip pour les chips ajoutés via autocomplete et pour le chip statique, puis vérifiez que chaque chip reste accent-colored tandis que le chip autonome reste primary.

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é
3/5
Temps estimé
1-2 jours
Activité
À l'abandon
Clarté
Plutôt claire
Accessibilité débutants
35/100

Recevez les nouvelles issues par e-mail

Un résumé court des issues GitHub adaptées aux débutants.