Ionic version:
[x] 4.4
Current behavior:
I notice with the release of iOS 13, the rate at which you can trigger (click) events is reduced.
For instance, setup a simple click handler:
<div (click)="handleClick()">
</div>
export class ClickHandlerComponent {
public count = 0
handleClick() {
this.count += 1
console.log('count', this.count)
}
}
Just run it, and try tapping the <div>. Try tapping it once per second. It will fire, and you'll see count 1, count 2 etc in the log, as you would expect.
Now, increase the rate at which you are tapping it. Try tapping every 0.5 seconds. Or less. On iOS 12 it could keep up - as fast as you could tap it, you would see the count 1, count 2 etc.
But on iOS 13, it seems to drop click events. It doesn't seem to go much faster than once per half-second on my device. If you go faster, it seems to skip some. It's like there is a min-window after a click event, after which you cannot fire a new one.
Maybe this isn't anything to do with Ionic, and is a bug in iOS 13 safari/webkit... but I thought I would report it anyway.
Expected behavior:
I would expect that the (click) events would fire as fast as I could trigger them.
Steps to reproduce:
(as above)
Related code:
(as above)
Other information:
I can't seem to find any other mention of click events being slow on iOS 13...
Ionic info:
Ionic:
Ionic CLI : 5.4.2 (/Users/asgeo1/.node/lib/node_modules/ionic)
Ionic Framework : @ionic/angular 4.4.2
@angular-devkit/build-angular : 0.12.4
@angular-devkit/schematics : 7.2.4
@angular/cli : 7.2.4
@ionic/angular-toolkit : 1.5.1
Cordova:
Cordova CLI : 9.0.0 ([email protected])
Cordova Platforms : android 8.1.0, ios 5.0.1
Cordova Plugins : cordova-plugin-ionic-keyboard 2.2.0, cordova-plugin-ionic-webview 4.1.1, (and 20 other plugins)
Utility:
cordova-res : 0.8.0
native-run : 0.2.8
System:
Android SDK Tools : 26.1.1 (/Users/asgeo1/Development/Android/sdk)
ios-deploy : 1.9.4
ios-sim : 8.0.2
NodeJS : v10.10.0 (/usr/local/bin/node)
npm : 6.9.0
OS : macOS Mojave
Xcode : Xcode 11.1 Build version 11A1027
Is anyone else able to replicate this issue?
Hi @asgeo1, this is a WebKit bug that seems to have been fixed for a coming iOS version (probably 13.2): https://trac.webkit.org/changeset/250447/webkit
As foreshadowed by the ancient VCS gods, this issue has been fixed in iOS 13.2 馃帄
Thanks for the issue! This issue is being locked to prevent comments that are not relevant to the original issue. If this is still an issue with the latest version of Ionic, please create a new issue and ensure the template is fully filled out.
Most helpful comment
As foreshadowed by the ancient VCS gods, this issue has been fixed in iOS 13.2 馃帄