Skip to content
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

Conflict with drag-n-drop extensions (such as dragdis.com for drag-n-drop bookmarking) #704

Closed
TrevorHinesley opened this issue Mar 22, 2017 · 5 comments
Labels

Comments

@TrevorHinesley
Copy link

I had been using Dragdis for quite some time, but noticed beginDrag (and any other drag-n-drop) events weren't executing while I had the extension enabled. I'm sure this isn't the only extension affected, and jQuery drag-n-drop is unaffected. I'm not sure what's conflicting.

@TrevorHinesley TrevorHinesley changed the title Conflict with drag-n-drop extensions (such as dragdis.com) Conflict with drag-n-drop extensions (such as dragdis.com for drag-n-drop bookmarking) Mar 22, 2017
@mikhuang
Copy link

mikhuang commented Sep 8, 2017

React DnD also seems to conflict with the Filestack widget's drag and drop functionality

@jennybean
Copy link

I have experienced this issue as well. Filestack does not work in where React DnD is being used.

@Liz303
Copy link

Liz303 commented Jun 14, 2018

Anyone found a solution to this? Working with filestack and react-beautiful-dnd works, but react-beautiful-dnd only supports x or y sorting, not sorting in a grid. I found a workaround to get filestack to work with react-dnd but it doesn’t meet my UI needs. By removing DragSource from the page I am able to get filestack to work. Here’s my example (this isn't working code but hopefully will give you an idea)

class DragArea extends React.Component {
    state = {
      draggableItems: [
        {id: 1, name: "first item"},
        {id: 2, name: "second item"},
        {id: 3, name: "third item"}
      ],
      dragAndDrop: false
    }
    addFile(filestackResponse) {
    // do some stuff in here
    }
    
    onError(file, error) {
    // handle error
    }
    
    render() {
      return (
        <div>
          <div onClick={() => {this.setState({dragAndDrop: !this.state.dragAndDrop})}}> {this.state.dragAndDrop ? "Draggable" : "Not Draggable"}</div>
          <ul className="draggable-items">
            <div className="filestack-upload-area" id="filestack-section-upload-primary">
                <FilestackUploader
                    dropzoneContainerId="filestack-section-upload-primary"}
                    type="area"
                    onSuccess={this.addFiles}
                    onError={this.onError}
                  />
              
             {this.state.draggableItems.map((item, index) => {
                if(this.state.dragAndDrop) {
                  /* Returns a react component wrapped in DragSource()
                  return (
                    <DraggableReactComponent/>
                  )
                } else {
                  return (
                    <ReactComponent/>
                  )
                }
             })}
           </ul>
         </article>
      );
    }
}

@NicoleRauch
Copy link

Any news on this? I am using a widget which uses react-dnd under the hood, and that killed my other D&D on the page (which was done with HTML5 droppable). Very unpleasant surprise...

@stale
Copy link

stale bot commented Jul 6, 2019

This issue has been automatically marked as stale because it has not had recent activity. It will be closed if no further activity occurs. Thank you for your contributions.

@stale stale bot added the wontfix label Jul 6, 2019
@stale stale bot closed this as completed Jul 13, 2019
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Projects
None yet
Development

No branches or pull requests

5 participants