Fix/388 hover on another element after dragstart #402
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
[WIP] Bug/381 sortupdate event index wrong (lukasoppermann#391)
…- Hover on another element after dragstart'
|
Geniously simple fix, thanks a lot. 👍 |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
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.
Solves #388, to the extent that
options.hoverClasswill not be added to any new item for as long as dragging takes place.Chrome still maintains pseudo-class :hover at the original location of the item that is being drag.
Recent Firefox and Safari, however, do not maintain CSS :hover pseudo-class at the original item location.
The
README.mdwarning not to use CSS :hover selectors for styling still holds true.