The simple use of "touchstart click" solve this issue. Im using Angular, so U can create a directive like...
app.directive("ngMobileClick", [function () {
return function (scope, elem, attrs) {
elem.bind("touchstart click", function (e) {
e.preventDefault();
e.stopPropagation();
scope.$apply(attrs["ngMobileClick"]);
});
}
}])
HTML call: ng-mobile-click="myScopeFunction()"
Hi,
Another way is set the css property like this (it works for me):
button:active { opacity: 1; !important }
Something pretty stupid that I could not understand, but I think it is something related to Apple posted in:
https://support.apple.com/en-us/HT205030
"Impact: A malicious website can make a tap event produce a synthetic click on another page Description: An issue existed in how synthetic clicks are generated from tap events that could cause clicks to target other pages. The issue was addressed through restricted click propagation."
So I suppose if the button on the active state on onsen is set to the lower opacity than 1, Apple should consider that this is a synthetic click .