[REACT] pinch zoom on iOS

[calendardeveloper]

Hi there,

I know this is an ongoing issue and it's one which is causing us lots of headache (and frustration) now, as we can't seem to pinpoint what is causing it. I've finally been able to sit down and create a sample app which can hopefully demonstrate the issue.

Steps to follow :-

1. Unzip the attached zip file and run 'npm install' in the folder.
2. You will see that in the App.js, I have got some code which generates random resources/events.
3. You will need to run this app and test on your iPhone. You should be able to do this locally as well, by using the public IP of your computer directly on your phone. e.g. I am using http://192.168.1.203:3000 directly on my phone.
4. Bow start playing with the number of rows on line number 20 in App.js const generator = DataGenerator.generate(500);
5. I have already done Widget.convertPinchToMousewheel = false
6. What you''ll notice is that if I have only 5 or 10 rows, there is no crash on the pinch zoom on phone. However, if I increase that number to 100, the page starts crashing about 1 out of 5 pinch zoom. If I set that number to anything close to 500 or more, it crashes almost every time I do pinch zoom.

I hope I have reliably demonstrated with this example what the issue we are facing. This sample has no custom renderers, and the very bare minimum configuration.

I am really hoping that you can come up with a solution to this, given this example.

[Animal]

Some bugs are in there, as now, in the 6.0 branch it doesn’t ever get converted to mouse wheel, and you can’t pinch-zoom a scheduler or calendar.

So that needs to be addressed. And we should probably be able to tell the GlobalEvents class to just not add touchmove listeners at all.

[calendardeveloper]

Hmm, have you tried my example yet? When can we expect these known bugs to be fixed?

[mats]

Extremely hard to debug a browser crash I'm afraid. Have you tried with latest 6.0 beta 2?

[calendardeveloper]

I tried with beta 1, same issues. Can try with beta 2 later.
However, when can I expect a version where the GlobalEvents.touchMove is completely not done, like Animal commented above?
I am hopeful that might make a difference.

[alex.l]

Hi there,

We fixed few issues regarding to touch events in Beta 2 and hopefully, it will be working better for you in that release.

However, when can I expect a version where the GlobalEvents.touchMove is completely not done, like Animal commented above?

Full refactoring will take a while and can't be expected before the end of year or so, I am afraid, but we are working on bug fixing with touch events in parallel with cases that we found and can debug. I hope the bug you mentioned is fixed in Beta 2, if no, please let us know and we will continue investigation.

[calendardeveloper]

I will try beta 2 for sure, but I have spent a lot of time in setting up this example. You've been asking for an reproducible example for so long. Has anyone tried it yet? Can you confirm you are able to see similar results as I did?

[alex.l]

Hi,

I tested your app, I don't see any errors on my iPad. I cannot confirm I am able to reproduce it. But I was able to reproduce this problem before, in very beginning, before last fixes.

[calendardeveloper]

You must try on your iPhone. I have mentioned this several times now, that I am testing this on iPhone 15 PRO MAX. Safari.

[alex.l]

I've attached video from iPhone, tested in Chrome and in Safari. It worked without problems.
Let us know what else we need to do to reproduce that. As you mentioned, 500 rows generated.