You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
I am using ractive on a page to render some dynamic content; this page has a bunch of other plugins, including custom ones, jQuery, and Zurb Foundation Sites. The trouble is, many plugins, including Foundation, have a "live listener" - like this one:
Not sure what the best solution is if there are compatibility issues (would be interested in understanding what exactly those were). For my project, I'm simply commenting it out.
The text was updated successfully, but these errors were encountered:
I think the goal with that line is just to prevent firing a click event after a touch event, so not so much compatibility with a particular browser - just preventing a double fire when the subsequent touch "compatibility click" event fires because the tap event also installs a click handler. Are you experiencing double fires on touch events where you're using on-tap with the preventDefault commented?
I'm not really familiar with zurb or recent jq, but does the touch.zf.trigger not subscribe the requisite touchstart, etc events? I would expect the touch events to still bubble up because propagation shouldn't be stopped.
It does not seem to fire a double event, but I haven't done extensive testing just yet. I was also mistaken in my copy/paste - it does not have the touch listener in the Foundation code (I added that in for testing) - edited the original post to avoid confusion. But even with that, the preventDefault still stifled it, and I wasn't getting double as far as I could tell.
I am using ractive on a page to render some dynamic content; this page has a bunch of other plugins, including custom ones, jQuery, and Zurb Foundation Sites. The trouble is, many plugins, including Foundation, have a "live listener" - like this one:
This event is never fired on elements that have an
on-tap
attribute because of this line:Not sure what the best solution is if there are compatibility issues (would be interested in understanding what exactly those were). For my project, I'm simply commenting it out.
The text was updated successfully, but these errors were encountered: