-
Notifications
You must be signed in to change notification settings - Fork 83
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
v-drag-over-target is not removed when the drop is ending in a Vaadin Grid #8476
Comments
Could be that Grid is eating the event Flow needs. Need to check if bug is on components side or flow side. |
The issue was triaged and currently added to the backlog priority queue for further investigation. |
As a workaround, you can disable the Grid with |
The issue was assigned to a developer and is currently being investigated. |
Due to a regression with no apparent solution, we needed to revert this fix. I am currently looking into a new fix for this that will not break existing functionality. |
Transferring issue to web-components repository, since was unable to fix it on Flow side without causing unwanted effects on other features. Either we need to let Grid propagate the DnD related events, or we need a custom event(s) fired that we could listen to in Flow and remove/add class names based on those. Edit: removed this from Flow board as well, please get back to us if anything is needed on Flow side. |
Description of the bug
When I'm using drag and drop, the
v-drag-over-target
is added automatically when drag-over and it's not removed when the drop zone has a grid and the drag end is done on top of a grid.v-drag-over-target
Expected behavior
v-drag-over-target
should always be removed.See the video: (the green border on top of the grid = v-drag-over-target is here)
Screen.Recording.2024-10-11.at.14.46.34.mov
Minimal reproducible example
and the CSS:
Versions
The text was updated successfully, but these errors were encountered: