1.1.4 and ngMobile

[Jeff Knight]

I pulled down the latest unstable 1.1.4 release to start playing around with the new ngMobile module, but it doesn't appear to be part of the release. Looking through the source, there doesn't seem to be any reference to touch events. Is there something I'm missing?

[Pawel Kozlowski]

I guess you are missing this one:
http://code.angularjs.org/1.1.4/angular-mobile.js

Full distribution here: http://code.angularjs.org/1.1.4/

Cheers,
Pawel

> --
> You received this message because you are subscribed to the Google Groups
> "AngularJS" group.
> To unsubscribe from this group and stop receiving emails from it, send an
> email to angular+u...@googlegroups.com.
> To post to this group, send email to ang...@googlegroups.com.
> Visit this group at http://groups.google.com/group/angular?hl=en-US.
> For more options, visit https://groups.google.com/groups/opt_out.
>
>



--
AngularJS book:
http://www.packtpub.com/angularjs-web-application-development/book
Looking for bootstrap-based widget library for AngularJS?
http://angular-ui.github.com/bootstrap/

[Jeff Knight]

That's what I was missing, thanks for the heads up.

Jeff

[Erez Lirov]

It looks like there may be a conflict with JQuery.  

http://plnkr.co/edit/fnJCUMn2fMZy9cIunfFj

If we leave the jquery include commented out, the ng-click responds quickly on my ipad.

If we add the jquery include back in, then the click seems to revert back to the slow click behavior.

[刘泉]

how to use ngmobile? need to add ng-tap?

[Erez Lirov]

Is anyone else running into this, or is this just a problem on my ipad? :)

[Jeff Knight]

I'm not running into that issue, but I am running into another issue. It seems that the FastClick code is not preventing ghost clicks. I'm having issues where when I tap on an element, if that tap triggers a route change and the new view has a form on it, then the form element at around the same position as the element I tapped receives focus. This is a consistent behavior. 

[Erez Lirov]

I'm getting the same effect as well.  But also the conflict with j query.  Did you try the plnkr on an ipad?

You received this message because you are subscribed to a topic in the Google Groups "AngularJS" group.
To unsubscribe from this topic, visit https://groups.google.com/d/topic/angular/NpgXfFh7nA0/unsubscribe?hl=en-US.
To unsubscribe from this group and all its topics, send an email to angular+u...@googlegroups.com.

[Jeff Knight]

I can verify that uncommenting out the jQuery include seems to break the FastClick behavior. 

[levyuk]

Is there any documentation on using ngMobile or is it just what's in the js file?

[Jeff Knight]

There's some basic documentation at http://code.angularjs.org/1.1.4/docs/api/ngMobile.directive:ngTap

[Jeff Knight]

Following up on this, adding an event.preventDefault on the touchend event fixes the issue I am experiencing in angular-mobile.js

[levyuk]

Do you know if when I use ng-tap it also fires ng-click? Or do I need to specify ng-tap and ng-click?

[Tyler Renelle]

Same problem as everyone else. Angular 1.1.5. Tried 1.2rc1 as well (which replaces ngMobile with ngTouch, and has a lot of ghost-click prevention code) - but no cigar. I'm going to try removing jQuery later, as seems to be the common workaround. 

@levyuk - note ngTap was removed, and wrapped up back into ngClick.

[Levi Morales]

Integrating this commit fixed the issue for me. Seems to be an issue with how jQuery wraps events. This checks to see if the original event is present and uses that instead.

https://github.com/jasonals/angular.js/commit/662934f083a5796c96a6c33c232f9531e88132fa