-
Notifications
You must be signed in to change notification settings - Fork 4.3k
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
Fix invisible drop target indicator caused by is-drop-target class being applied to dragged block #23638
Merged
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
…ing applied to dragged block
Size Change: +37 B (0%) Total Size: 1.13 MB
ℹ️ View Unchanged
|
6 tasks
Thank you! This just needs a code review, looks like! |
Yes, this we should do this differently :) |
ellatrix
approved these changes
Jul 3, 2020
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Labels
[Feature] Drag and Drop
Drag and drop functionality when working with blocks
[Type] Bug
An existing feature does not function as intended
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.
Description
Since #23024 the block being dragged is set to
display: none
.I noticed a small issue where if that block is the one considered a drop target, it would have the
is-drop-target
class name applied, but because it's set todisplay: none
, the drop target would not be visible.To users, it'd seem like they were dragging a block into a valid position, but the blue drop target indicator wouldn't appear.
This PR fixes things by making sure the block being dragged is never considered a drop target.
In the future, I think it'd be great to not use the block border itself as the thing that indicates a drop zone, but in the short term this seems like the best way to fix the issue.
How has this been tested?
master
it's not visible.Screenshots
Types of changes
Bug fix (non-breaking change which fixes an issue)
Checklist: