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.
I was having an issue in my project when the mouse moves directly from one object to another. I have a div on the page that is supposed to be updated with metadata on a
mouseover
event and cleared on amouseout
event. However, when the mouse moves directly from one object to another themouseover
event for the new object would fire before themouseout
event for the old object. As a result the div would be updated with the new metadata but then immediately cleared.I felt like the
mouseout
event for the old object should fire before themouseover
event for the new object so that the div can be cleared of the old metadata and then updated with the new. I made these changes to the code and now it works as expected.You may have alternative reasons for wanting to keep it as it was but for my usecase I felt like this should be the default behaviour. I just thought I would share this incase others think so also, if you like it merge it, if not then delete it. Etherway thanks so much for the awesome code!
Cheers! 🍺🍺