Sortable freezes when acceptFrom list does not exist
See original GitHub issueOriginates from #519
Current behavior:
When acceptFrom
is used, but no sortable with the selector can be found the sortable freezes.
Needs validation: This should be validated with an example on codepen.
Desired behavior:
- Catch error from isConnected and log to console.
- Make sure the sortables work as if
acceptFrom
was not present
Issue Analytics
- State:
- Created 4 years ago
- Comments:5 (2 by maintainers)
Top Results From Across the Web
jQuery sortable onDrop event freezes the page - Stack Overflow
I wasn't getting a page freeze when testing your code, but the element that was dragged never got the .dragged class removed from...
Read more >JqueryUI - Sortable - Tutorialspoint
jQueryUI provides sortable() method to reorder elements in list or grid using the mouse. This method performs sortability action based upon an operation ......
Read more >Documentation - Apache Kafka
When disabled, broker does not perform any down-conversion and instead sends an UNSUPPORTED_VERSION error to the client. Dynamic broker configuration options ...
Read more >G - Veterans Affairs
BR_6.02 VBECS displays options that are not available to a user in gray text. ... BR_5.02 VBECS lists all or part of a...
Read more >Mail not working in macOS Catalina, How-to fix - AppleToolBox
Here are some tips to help you if your Mail is not working following upgrade to macOS Catalina. Mail crashing? Unable to send/receive?...
Read more >Top Related Medium Post
No results found
Top Related StackOverflow Question
No results found
Troubleshoot Live Code
Lightrun enables developers to add logs, metrics and snapshots to live code - no restarts or redeploys required.
Start FreeTop Related Reddit Thread
No results found
Top Related Hackernoon Post
No results found
Top Related Tweet
No results found
Top Related Dev.to Post
No results found
Top Related Hashnode Post
No results found
Top GitHub Comments
Hey @kaffarell please leave it open until the documentation is updated. In the PR to update the readme you can all “fixes #520” and this issue should auto-close once it is merged. Just FYI closing-issues-using-keywords (I also don’t know all keywords, but it is very handy, you can also close multiple issues this way)
👍 Going to change the documentation soon, can I close this issue?