fix(useDropZone): update isOverDropZone handling when elements inside the drag area use v-if #4664
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Before submitting the PR, please make sure you do the following
fixes #123
).Description
Issue: #4652
Reason Found: When the elements inside the drag area use v-if, moving the mouse away from those internal elements fails to trigger the dragleave event on them. This causes an error in the counter calculation, preventing isOverDropZone from being set to false.
Solution Approach: Add an extra condition to the existing logic to check whether the mouse is still within the drag area.
Additional context