Some problem arised after new-sdk was implemented. I am speaking about very weird tap behaviour. Before that 1.8.7 update the tap (on iOS or android) was working like a charm, but now user needs to tap like 0.25 ms longer to actually tap on object.
I found this line in vg.mapviewer.web.js:
Changing the number 250 to 0 of time param fixes this problem with tap behaviour. May I know what’s the purpose of tap delay (time) and will it break anything else if I change time to zero?
Thanks in advance!
The line you mention belongs to an external library that we use for managing touch interactions. This library was not updated for 1.8.7.
However, as mentioned in the changelog, we did fix an issue that prevented some developers to detect tap events when integrating VisioWeb through a cross-platform framework. If 1.8.6 works for you, I would recommend reverting to that version, because 1.8.7 only brought that particular fix.
Of course, if you can provide us with more details about your context (phone model, OS version, browser version), it would help us reproducing the issue and making sure it works in the upcoming (1.8.8) release.
Thanks in advance
Can you give VisioWeb 1.8.8 a try ? We tried to reproduce what you described and included a potential fix for this issue in the version we just released for VisioWeb.
On new SDK 1.8.8 everything works fine for now. Good job, thanks!