You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
[x] bug report => Search github for a similar issue or PR before submitting
[ ] feature request
[ ] support request => Sorry, we will not be able to answer every support request. Please consider other venues for support requests
While dropped, custom component will not emit any value. I can't just wrap my two components with div and attach ngxDraggable to that div because my custom components are created dynamically. After some digging in your code I found that the problem is in this line:
this.drake.on('drag'....) {
...
if (_this.draggableMap.has(el))
...
}
Because el is custom-component1 and draggableMap expects it to be the div inside it.
Expected behavior
Be able to attach ngxDaggable inside custom component and still take advantage of [model] functionality. It's quite important in my use case so it would be great If some could look into that :).
Reproduction of the problem
What is the motivation / use case for changing the behavior?
Please tell us about your environment:
ngx-dnd version: 5.0.6
Angular version: 6.0.7
Browser: [all | Chrome XX | Firefox XX | IE XX | Safari XX | Mobile Chrome XX | Android X.X Web Browser | iOS XX Safari | iOS XX UIWebView | iOS XX WKWebView ]
Language: [all | TypeScript X.X | ES6/7 | ES5]
The text was updated successfully, but these errors were encountered:
I'm submitting a ... (check one with "x")
Current behavior
For most simple use case.
While dropped, custom component will not emit any value. I can't just wrap my two components with div and attach ngxDraggable to that div because my custom components are created dynamically. After some digging in your code I found that the problem is in this line:
this.drake.on('drag'....) {
...
if (_this.draggableMap.has(el))
...
}
Because el is custom-component1 and draggableMap expects it to be the div inside it.
Expected behavior
Be able to attach ngxDaggable inside custom component and still take advantage of [model] functionality. It's quite important in my use case so it would be great If some could look into that :).
Reproduction of the problem
What is the motivation / use case for changing the behavior?
Please tell us about your environment:
The text was updated successfully, but these errors were encountered: