Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Different ways to deal with excluded elements... #54

Closed
flynx opened this issue Jan 24, 2013 · 1 comment
Closed

Different ways to deal with excluded elements... #54

flynx opened this issue Jan 24, 2013 · 1 comment

Comments

@flynx
Copy link

flynx commented Jan 24, 2013

Here is something I'd like to control, a usecase:

  • tap/click a link and it behaves like a link
  • touch and swipe a link and I get a swipe event instead of the link behavior

I do see a way around this -- I can register a touchSwipe click event on a non-excluded element, but this is less natural than just adding an A element, plus the approach will require allot of jumping through hoops to get dynamic content wired up and working correctly...

I'm thinking of something like a threshold (speed or distance) for specific elements, before you pass it, you get default behavior, go over, and it's a swipe... this will also make things like selecting text and focusing input elements more natural.

Note, this does not cancel out the need of completely excluded elements, so it's a slightly different category, not yet sure of a natural and simple way to deal with this, still thinking...

P.S. right now, for instance, if I remove A from excludedElements I get both a swipe and a link action and can't find a way to control this from the handlers...

@mattbryson
Copy link
Owner

Does not just adding the jQ click event to the item work?

Or using the click method of TouchSwipe and then checking the source?

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants