Feature #90: Adding touch compatibility (new event listeners). #91
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.
Currently a work in progress; still needs a proper initialization on load. Possibly as a configuration parameter, since naturally you cannot hover over anything with a touch device, but you can swipe. Only works currently if you tap first on the viewport and then swipe around. The touch emulates a
mouseenter
event. The idea then would probably be to trigger amouseenter
event on any of the touch events in case it hasn't already been triggered.Currently how I'm doing this outside of this library is with Modernizr, simply looking for a
touch
class and then initializing it on page load:Again a better solution here would be to wait first for some interaction, since as a plugin, it needs to be concerned only about it self and not initialize due to changes in global state (i.e. page load).