bug(cdkDropList): Wrong index for cdkPlaceHolder/cdkDrag after drag/hover other list and going back to original droplist
- Vorherrschende Sprache
- TypeScript
- Sterne
- 25k
- Forks
- 6.8k
- Ø Merge
- 1 T. 8 Std.
- Gemergte PRs (30 T.)
- 91
Beschreibung
### 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):
Beitragsleitfaden
Rechercherichtung
Starte zunächst die verlinkte StackBlitz-Reproduktion und verfolge das Verhalten von cdkDropList, cdkPlaceHolder und cdkDrag, während du ein Element von der rechten Liste in eine linke Liste und zurück verschiebst. Vergleiche den zurückgegebenen Platzhalterindex und den finalen Elementindex mit der ursprünglichen Position; abgeschlossen ist die Aufgabe, wenn das Element und der Platzhalter an ihren ursprünglichen Index zurückkehren, ohne die Drag-Richtung zu ändern.
Vom Indexierungsmodell aus dem Issue-Text verfasst.
Bewertung
- Tech-Stack
- angular, typescript
- Bereich
- frontend
- Issue-Typ
- Bug
- Schwierigkeit
- 4/5
- Geschätzter Aufwand
- 3-5 Tage
- Aktivitätsstatus
- Veraltet
- Klarheit
- Größtenteils klar
- Anfängerfreundlichkeit
- 35/100