bug(drag-drop): Slot content not visible when we start dragging an element
- 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
Hi,
Background:
I am creating a reusable dynamic list component which also has the ability to drag and drop items in a list.
This component uses **slots** to dynamically project content from the consumer component.
Problem:
The component renders correctly.
But when I start dragging an item, the content in the slot is not visible.
Does anyone know how to solve this issue or any workaround for this?
@angular/cdk
@angular/cdk/drag-drop
Thanks!
### Reproduction
StackBlitz link: https://stackblitz.com/edit/stackblitz-starters-jbsaba?file=src%2Fmain.ts
Steps to reproduce:
1. Click on "Item 1 in slot" and start dragging it.
2. Notice that the text "Item 1 in slot" is not visible while you are dragging the item.
### Expected Behavior
Any content in a slot element should be visible while dragging the element.
### Actual Behavior
Content in the slot is not visible while you are dragging the item.
### Environment
- Angular: 16.2.7
- CDK/Material: 16.2.6
- Browser(s): Chrome
- Operating System: macOS
### REASON -
I am still debugging but found the reason behind this problem.
As per documentation,
"When a cdkDrag element is picked up, it will create a preview element visible while dragging."
This causes another slot element to be created with the same name which is why we don't see its content.
Still trying to find a solution.
Beitragsleitfaden
Rechercherichtung
Öffne die verlinkte StackBlitz-Reproduktion und beginne mit src/main.ts. Ziehe „Item 1 in slot“, um zu bestätigen, dass projizierter Slot-Inhalt in der Drag-Vorschau fehlt. Fertig ist die Aufgabe, wenn der Slot-Text während des Ziehens sichtbar bleibt und die Reproduktionsschritte weiterhin erfolgreich sind.
Vom Indexierungsmodell aus dem Issue-Text verfasst.
Bewertung
- Tech-Stack
- angular, typescript
- Bereich
- frontend
- Issue-Typ
- Bug
- Schwierigkeit
- 3/5
- Geschätzter Aufwand
- 1-2 Tage
- Aktivitätsstatus
- Veraltet
- Klarheit
- Größtenteils klar
- Anfängerfreundlichkeit
- 42/100