-
Notifications
You must be signed in to change notification settings - Fork 729
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
Dragging with NONE accept-criterion blocks / freezes application indefinitely (on client side) #4060
Comments
Originally by @Wnt Unfortunatelly I don't have time to work on this in the next few weeks. |
Originally by @Artur- A lot of tickets have been left hanging in the issue tracker through the years. Some of them are still relevant, some of them have been fixed a long time ago and some are no longer valid. To get a better look on what is important and still relevant, we are closing old tickets which have not been touched in a long time. No further work will be done on this ticket unless someone indicates that it's still relevant. If this ticket is still relevant to you, please reopen it. |
NB this issue is still around in the currently latest Vaadin-release |
No auto test because of SeleniumHQ/selenium#1365 Fixes vaadin#4060
No auto test because of SeleniumHQ/selenium#1365 Fixes vaadin#4060
* Properly end HTML5 drag operations when no drop is performed No auto test because of SeleniumHQ/selenium#1365 Fixes #4060
Originally by @jtreml
With a drop handler that returns NONE as an accept criterion (
Not((ClientSideCriterion) AcceptAll.get())
), dragging anything in the UI will stop the application from responding to any more events indefinitely until you refresh the browser.[[BR]][[BR]]
Online demo:[[BR]]
[http://env-2724817.jelastic.servint.net/drag-freeze/]
To reproduce:
Demo code:
Imported from https://dev.vaadin.com/ issue #12013
The text was updated successfully, but these errors were encountered: