-
Notifications
You must be signed in to change notification settings - Fork 6.8k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
bug:(@angular/cdk/drag-drop): Cannot read property 'clientRect' of undefined #13077
Comments
FYI: the error occurs when adding the 2nd "List" item. |
It's hard to tell what's going on based on the video. Based on the stack trace, it looks like a |
here it is : https://stackblitz.com/edit/angular-uhe5x7 Try to drop a same item twice in the red zone. |
Thanks for the reproduction @kanidjar. It looks like the issue was fixed in master already. |
Nice, thank you @crisbeto |
@crisbeto what was the fix exactly? I'm still seeing this issue and I am on the newest version of the cdk |
@dakotamaker it's been a while so I don't remember. I think I tried out the Stackblitz against master and the issue just wasn't there. |
I'm facing same issue. Did you find any way to resolve this one @kanidjar? |
I'm getting this error when applying [cdkDropList] directive it the parent component and [cdkDragData] in it's childrens. When everything in the one component, then no errors. |
Yes, I am facing the same, is there a solution for this? |
@crisbeto I am trying to sort or dragdrop dynamically generated components. The container has the cdkDropList directive while the dynamically components has the cdkDrag directive and I would expect it works, It is simply not working. [Parent Component that holds a container for the dynamic child component to insert.]
[HTML of the child component that would be inserted in the container.]
|
The drag & drop is a great feature, In my opinion it should be not only with simple list that we can drag and drop but also components and more specific to dynamic components. I am sure the usage of dynamic components may be limited scope but this is where Angular is helping new developers like us achive a lot of things quickly and easily. I do not understand the priority of the bugs but to me this bug should be raised to a higher priority. @crisbeto please comment. |
same problems here with mat-table as cdkDropList and mat-row inside as cdkDrag this means that the new drag&drop api in angular7.1 is not usable with mat-tables which is sad, because i need this features... |
btw. only dragging of mat-tables works fine.... |
I'm having the same problem using I'm getting this while having the edit: the issues seems to resolve when I put the cdkDrag directives on the child-component selectors in the same html as the component instead of inside the html of the child component. |
Hello. Same problem with "@angular/cdk": "^7.1.1". I have a component with two connected cdkDropList. One list is filled with dynamically generated components that contain the cdkDrag directive in the template. When I try to drag one of these elements the error appears. edit: solved following @JesseZomer hint:
|
for me the problem is not solved. |
I reproduce it adding D&D to move reactive form controls (siblings dynamically added to a single form within a single angular component). |
Hey, Using the exact same code inside a |
I am experiencing the same issued. I need to be able to call the (cdkDragDropped) event within the child component, but this error makes it so the cdkDropList does not recognize the cdkDrop when in separate components. |
I am struggling with the same issue, has this issue been fixed? |
FYI, it seems that I added |
I added a cdkDragHandle to an element inside my draggable component and I no longer got this error. |
Any fix? |
I'm reproducing this error on the stackblitz example from angular.io : |
…s finishing Fixes an error being thrown if the user manages to start a different drag sequence while the previous one is finishing. The error comes from the fact that some elements are still being moved around while we're waiting for the previous animation to finish. Fixes angular#13077.
…s finishing Fixes an error being thrown if the user manages to start a different drag sequence while the previous one is finishing. The error comes from the fact that some elements are still being moved around while we're waiting for the previous animation to finish. Fixes angular#13077.
bump ... |
This issue has been automatically locked due to inactivity. Read more about our automatic conversation locking policy. This action has been performed automatically by a bot. |
Bug, feature request, or proposal:
BUG: when drag-dropping an item between two connected dropzone, an error occurs randomly
See video and image below
https://streamable.com/nuudt
What is the expected behavior?
No error should occur.
What is the current behavior?
An error occurs randomly as soon as an item enters in the dropzone. The (dropped) event happens anyway.
What are the steps to reproduce?
Classic connected dropzones.
My dropzones are not in the same component.
Which versions of Angular, Material, OS, TypeScript, browsers are affected?
"@angular/cdk": "^7.0.0-beta.0"
"@angular/material": "^6.4.7"
"@angular/core": "^6.1.6",
Is there anything else we should know?
The error is located in drag-drop.es5.js.CdkDrop._sortItem (drag-drop.es5.js:1436)
The text was updated successfully, but these errors were encountered: