You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Hi, I'm using this control in a booking-like project and I see that on mobile devices (or in mobile simulator in browsers like firefox and chrome) the date we set as disabled are shown as enabled. Why?
So I inspect the javascript code ad I found two lines like this:
....
if ( settings.dateDisabled != undefined && 'ontouchstart' in window === false ) {
.....
So I ask myself "why it does not sohw disabled dates on mobile????". I put the part "&& 'ontouchstart' in window === false" in a comment and upload modified javascript.
The question is: why do you insert this code? What would go wrong without "&& 'ontouchstart' in window === false"? I test my form with edited js and it seems to work like befors, with the advantage that now works correctly also on moblile visualization.
Some comments about this?
Thank you!
Fabio
The text was updated successfully, but these errors were encountered:
rampo83
changed the title
Date disablet not work on mobile
Date disabled not work on mobile
Dec 17, 2019
Hi, I'm using this control in a booking-like project and I see that on mobile devices (or in mobile simulator in browsers like firefox and chrome) the date we set as disabled are shown as enabled. Why?
So I inspect the javascript code ad I found two lines like this:
....
if ( settings.dateDisabled != undefined && 'ontouchstart' in window === false ) {
.....
So I ask myself "why it does not sohw disabled dates on mobile????". I put the part "&& 'ontouchstart' in window === false" in a comment and upload modified javascript.
The question is: why do you insert this code? What would go wrong without "&& 'ontouchstart' in window === false"? I test my form with edited js and it seems to work like befors, with the advantage that now works correctly also on moblile visualization.
Some comments about this?
Thank you!
Fabio
The text was updated successfully, but these errors were encountered: