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
{{ message }}
This repository has been archived by the owner on Apr 12, 2024. It is now read-only.
The ngMobile module provides a special ng-click directive that does a lot of work to figure out when exactly a ng-click handler should execute when running in a mobile environment.
However, for developers writing directives it's not possible to target this special click event as it is not raised on the element. While it is very common to write directives that bind click handler to elements, it's currently not possible to bind to this special click event. In your directives you are left with binding to the regular click event which unfortunately is the browsers default "slow" click implementation.
The text was updated successfully, but these errors were encountered:
cburgdorf
added a commit
to cburgdorf/angular.js
that referenced
this issue
Jul 13, 2013
With this patch, people can bind to the 'ngClick'
event in directives so that they can run code
on the non native mobile tap/click event which
is controlled by the click directive from the
ngMobile module.
Fixesangular#3218
The
ngMobile
module provides a specialng-click
directive that does a lot of work to figure out when exactly ang-click
handler should execute when running in a mobile environment.However, for developers writing directives it's not possible to target this special click event as it is not raised on the element. While it is very common to write directives that bind click handler to elements, it's currently not possible to bind to this special
click
event. In your directives you are left with binding to the regularclick
event which unfortunately is the browsers default "slow" click implementation.The text was updated successfully, but these errors were encountered: