Open jelledijkstra97 opened 3 years ago
Unfortunately this is still a problem...
wtf
So I stumbled upon this problem; It got me stumped for a while. Last Thursday I provided a possible solution but it seems like this was not a viable solution after all.
The real source of the problem was that I was wrapping touch events on higher level elements in my template.
I am unsure of the reason why this is not supported in ios but removing my @touch event resolved it.
Please, provide the details below:
Tell us about the problem
Please, ensure your title is less than 63 characters long and starts with a capital letter.
Which platform(s) does your issue occur on?
iOS (not tested on Android)
Please provide the following version numbers that your issue occurs with:
Please tell us how to recreate the issue in as much detail as possible.
Is there code involved? If so, please share the minimal amount of code needed to recreate the problem.
I've located the problem in line 833 of ui-listview.ios.js. There you find the following code fragment
if (currentIndexPath && touchEvent.tapCount === 1) { if (owner.hasListeners(commonModule.RadListView.itemTapEvent)) { var args = { ios: touches, eventName: commonModule.RadListView.itemTapEvent, object: owner, view: this.myContentView, index: owner._getIndexForIndexPath(currentIndexPath), groupIndex: currentIndexPath.section }; owner.notify(args); } }
As you can see the event is only fired when tapCount equals 1. What is the idea behind this line? If there is none, can it be removed?