300ms click delay

Discontinued products DHTMLX Touch
#1

Does dhtmlx touch automatically remove the 300ms click delay for the components and controls?

#2

Could you explain what delay did you mean ?

#3

It looks like the 300ms click delay is not a problem when using the meta tags dhtmlx suggest.

This meta tag takes care of the problem:

<meta name = "viewport" content = "initial-scale = 1.0, maximum-scale = 1.0, user-scalable = no">

Without the tag, the browser waits 300ms before rendering the click event because it is waiting to see if the user is performing a double tap.

So this is a false alarm.

#4

Here’s a link explaining the problem:
developers.google.com/mobile/ar … s?hl=de-DE

This was the popular way of removing the 300ms wait:
github.com/ftlabs/fastclick

This last link says that correct viewport meta tag, the browser removes the 300ms delay on desktop browsers.

I’ve tested with and without the viewport tag on chorme and safari on an iPad and I am not able to see any differences.

#5

Hello,

Thank you for provided links.

I’ve tested with and without the viewport tag on chorme and safari on an iPad and I am not able to see any differences.

Probably you are using fullScreen method in your app:

dhx.ui.fullScreen();

This method automatically includes “viewport” meta tag.