Hi Michael,

We are not able to reproduce any issue with the DatePicker on Mobiles.

For example, i just recorded a Video of my Android Screen, how it looks when i visit one of our Tables on the Demo Sandbox, this Front-End SQL Table 1.

If i load it on my Mobile, and try to edit any Date Field, the Date Picker does load, we just need to scroll up or down a bit in order to reveal it fully.

At first, it loads like this, for example, a bit "cut off", but if I scroll vertically on the screen, then it brings the DatePicker nicely into view.

I am attaching the Video of my Mobile screen here.

- Can you tell me, what happens if you try to scroll vertically to bring the DatePicker fully into view, does it show on your Mobile, or does the issue still happen even after scrolling, you still can't see the DatePicker fully?

If the issue still happens even after you try to scroll up or down, and the Picker still does not properly show,

can you please send me the front-end URL of this Page, so we can visit it from our Mobiles?

- And if you can send us back-end Access, too.

Please provide me a temporary WP-admin (administrator) user for your site where this happens, so we could log in and take a look ‘from the inside’ as that’s the most efficient way to see and resolve the issue. 

We do not interfere with any data or anything else except for the plugin (in case that’s a production version of the site), and of course, we do not provide login data to third parties. 

You can write credentials here just check PRIVATE Reply so nobody can see them except us.

- Also, can you please try to reproduce the same behaviour on our Sandbox Demo Table 1, when you visit from your phone, to determine if the issue is only isolated on your Site, or is it the same on our Demo?

Thank you.

Hi Michael,

Just a small follow-up.

You're welcome, I will keep following up and going to do our best to somehow help you debug /isolate the issue.

As you can see, we are unable to reproduce it and we tried several Android models and different keyboards.

Until we isolate the issue to 'catch it in the act' we won't be able to help resolve it, unfortunately.

So let me know if you can try to isolate it on your end further/ how it goes, if you can reproduce it, you can send us more Video(s) and screenshots/ and more details about a specific device/ specific keyboard, which browser is used/browser version, etc;

so then our QA Team can try again to reproduce it.

No problem, we will close the ticket for now - but please don't hesitate to open a new one if you find new details we should take a look at.

Thank you again for all your patience and cooperation.