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
Is your feature request related to a problem? Please describe.
I have a parent component that uses the native onDragStart method, and my child component is wrapped with react-dnd. When dragging in the child component, the event bubbles up to the parent component. How do I prevent the event from bubbling in the useDrag of the child component?
Describe the solution you'd like
Subcomponents have interfaces to prevent events from bubbling up
Describe alternatives you've considered
no plan
Additional context
Only the child components need to be wrapped with react-dnd, the parent component does not need to be wrapped
The text was updated successfully, but these errors were encountered:
I met an issue looks like yours. In the parent component, I have a child component wrapped with react-dnd, but another child component uses the navtive "draggable=true & onDragStart", but this component is not working, try to drag it, no response.
I met an issue looks like yours. In the parent component, I have a child component wrapped with react-dnd, but another child component uses the navtive "draggable=true & onDragStart", but this component is not working, try to drag it, no response.
Is your feature request related to a problem? Please describe.
I have a parent component that uses the native onDragStart method, and my child component is wrapped with react-dnd. When dragging in the child component, the event bubbles up to the parent component. How do I prevent the event from bubbling in the useDrag of the child component?
Describe the solution you'd like
Subcomponents have interfaces to prevent events from bubbling up
Describe alternatives you've considered
no plan
Additional context
Only the child components need to be wrapped with react-dnd, the parent component does not need to be wrapped
The text was updated successfully, but these errors were encountered: