added support for on hover notifications #14
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
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.
Hi,
For a use case we needed notifications to be closed on user hovering the mouse over the notification. So I have introduced new callback functions on settings
over: function (e. instance) {...}
out: function (e. instance) {...}
that will be called when mouse is over the notification and and juts lived notification.
By default if hoverIntent.js is present (and loaded before notify.js) then hover intent will be used. If not present then default jquery hover will be used. If present but you still want to use jquery hover you can pass parameter {useHoverIntent: false}.
I have modified the sample app to show these options.