Reactive forms inside virtual scroll list yield buggy behaviour
- Langage dominant
- TypeScript
- Étoiles
- 25k
- Forks
- 6.8k
- Merge moyen
- 1 j 8 h
- PR mergées (30 j)
- 91
Description
## I'm submitting a...
[ ] Regression (a behavior that used to work and stopped working in a new release)
[x] Bug report
[ ] Performance issue
[ ] Feature request
[ ] Documentation issue or request
[ ] Support request => Please do not submit support request here, instead see https://github.com/angular/angular/blob/master/CONTRIBUTING.md#question
[ ] Other... Please describe:
## Current behavior
Reactive forms inside a virtual scroll list, should behave as expected. It looks like virtual scroll takes over and manipulates index which yields in erratic behaviour. If we check the last item in form array as checked and then go back to top and come back again to bottom, it is marked checked again. Tried external index as well but that didn't help either.
## Expected behavior
Reactive forms especially checkboxes should behave normally, and their values should belong to
appropriate ones only. Marking one checked should not affect others.
## Minimal reproduction of the problem with instructions
## What is the motivation / use case for changing the behavior?
For heavy or huge reactive forms, virtual lists should render form controls normally.
## Environment
Angular 7 and CDK 7
Angular version: 7.0.0
Browser:
- [x] Chrome (desktop) version 67.0.3396.87
- [x] Firefox version latest
- [x] Safari (desktop) version 12
- [x] IE version 11
Others:
Code sample can be seen on [stackblitz](https://stackblitz.com/edit/angular-mnd3k1) or [here](https://stackblitz.com/edit/angular-mnd3k1)
Guide de contribution
Ouvrir le guide de contribution
Piste de recherche
Commencez par exécuter la reproduction StackBlitz liée et examinez l’interaction entre la liste de défilement virtuel Angular CDK et les valeurs des cases à cocher du formulaire réactif pendant le défilement. Reproduisez la séquence signalée : cocher le dernier élément, revenir en haut, puis faire défiler à nouveau jusqu’en bas ; c’est terminé lorsque chaque case à cocher conserve uniquement sa propre valeur tout au long de cette séquence dans les navigateurs indiqués.
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é
- À clarifier
- Accessibilité débutants
- 25/100