mlisowsk

I ran into this bug today when working with MS WebBrowser Control (which is based on IE11, if IE11 is installed on that machine). #### Workaround My workaround is to...

@ronaldohoch you _can_ have specific event handlers for the onNext (or any other event) for each step. For example you can bind an `onNext` handler just for the first step...

@kamranahmedse did you get stuck on the rewrite? How about just commit+release your rewrite or merge those pull requests and move on to the next release. Looks like a dead-lock...

> [jquery.fn.sortable.js.tar.gz](https://github.com/RubaXa/Sortable/files/309293/jquery.fn.sortable.js.tar.gz) You can find here a version of the library (with jQuery compatibility) which works on IE 10 & 11 and Edge on Tablet devices ! Maybe a commit...

I am using the code below to refresh the overlay position with a small delay (here 500ms). This allows the clicked element to handle any of its own logic and...

I managed to get drag and drop to work in a MS WebBrowser control (IE11 mode) by passing the option `supportPointer: false` , i.e. instructing Sortable to explicitly not use...

Better documentation of event handler environment. Specifically what is the value of `this` in event handlers?

Try this, it works for me: https://github.com/SortableJS/Sortable/issues/266#issuecomment-1619729909

I suggest you handle state in Redux and ignore the SortableJS store. Just render the new items to DOM in new order when needed - make sure to not remove...

Somewhat sidestepping here but in a browser you can actually use the browser's devtools. For example in Chrome: * press F12 to bring up devtools * Go to Network tab...