bug(cdkDropList): Wrong index for cdkPlaceHolder/cdkDrag after drag/hover other list and going back to original droplist
- 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
My apologies if this is a stupid use case, I am trying to use multiple droplists as a base for a patience/solitaire card game as a learning project. There are multiple connected droplists where you can only drag the last item, and drop it in the last position of another container. This works amazing.
However, dragging from a cdkDroplist from the right to another cdkDroplist to the left of it and returning to the original list does not put the cdkPlaceHolder in the original index. Dragging from left to right (and returning to the original list) does?!
Not sure is this is an issue or working as intended.
I think i understand partially why it happens, but don't understand why it does work from left to right.
### Reproduction
StackBlitz link: https://stackblitz.com/~/github.com/PsychoSpike/cdkDropListsSortedToBottom
Steps to reproduce:
1. Pick up an item from the most right list
2. Drag(not drop) it over a list to the left
3. Return to the original list
### Expected Behavior
The CdkDragPlaceholder and CdkDrag element returns to its original index
### Actual Behavior
The CdkDragPlaceholder shows up at the wrong index and the CdkDrag element gets put into index-1 from starting the drag
### Environment
- Angular:
- CDK/Material:
- Browser(s):
- Operating System (e.g. Windows, macOS, Ubuntu):
Guía de contribución
Línea de trabajo
Comienza ejecutando la reproducción enlazada de StackBlitz y sigue el comportamiento de cdkDropList, cdkPlaceHolder y cdkDrag mientras mueves un elemento de la lista derecha a una lista izquierda y de vuelta. Compara el índice del marcador de posición devuelto y el índice final del elemento con la posición original; se considera terminado cuando el elemento y el marcador de posición vuelven a su índice original sin cambiar la dirección del arrastre.
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
- 35/100