bug(drag-drop): Slot content not visible when we start dragging an element
- Lingua principale
- TypeScript
- Stelle
- 25k
- Fork
- 6.8k
- Merge medio
- 1g 8h
- PR unite (30g)
- 91
Descrizione
### 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.
Guida per i contributori
Apri la guida per i contributori
Direzione di ricerca
Apri la riproduzione StackBlitz collegata e inizia da src/main.ts. Trascina “Item 1 in slot” per confermare che il contenuto dello slot proiettato manca dall’anteprima del trascinamento. Il lavoro è completato quando il testo dello slot rimane visibile durante il trascinamento e i passaggi per riprodurre il problema continuano ad avere esito positivo.
Scritto dal modello di indicizzazione a partire dal testo della issue.
Valutazione
- Stack tecnologico
- angular, typescript
- Ambito
- frontend
- Tipo di issue
- Bug
- Difficoltà
- 3/5
- Tempo stimato
- 1-2 giorni
- Stato di attività
- Ferma
- Chiarezza
- Abbastanza chiara
- Idoneità per principianti
- 42/100