Hello Jon,

Thank you for reaching out to us.

Could you please provide us with the URL of that booking page so we can perform checks and provide you with an update on this issue?

Looking forward to your reply.

Hi, Jon 

Sorry for the waiting time.

Thank you for the access to the page, we can see what you mean, and we are able to replicate the same behaviour on our Demo site booking page.

For example - if i take my android phone ( XiaoMi Redmi 9)

, in Google Chrome it works perfectly same as on desktop > if there is only one time slot, it is automatically selected, and i can press Continue right away;

but if i use the same phone on Mozilla Firefox,  the time slot is not selected, and has to be picked in order to press "Continue".

Here are my phone screen recordings, first one is Chrome,  second one Mozilla

-

I have passed this to our QA Testing team , just to be sure - we will report back as quickly as possible with more information on the issue.

Thank you for reporting this, and for your patience.

Hi, Jon 

Thanks again for reporting this issue.

We have confirmed it, replicated on Test sites -  and we have added it to the list of tasks for our developers.

They will do their best to fix/correct it, we are confident that they should be able to make the fix for one of the next future updates,

but we can't guarantee an exact ETA, since sometimes certain development or a fix can be postponed due to unpredictable variables/factors.

You can certainly follow our changeLog page if you'd like, where we state any changes/new features/bug fixes during updates;

and our newsletter, so you're informed about new features, bug fixes, freebies, etc.

Hi, Jon 

Sorry for the waiting time.

I absolutely understand that.  We should launch another update, i believe in couple of days, but not sure if the devs are going to implement a correction for this.

We will see after the update comes out.

Of course - you can always double-check during updates, to make a separate Test page, to test out the New Form again, and see how it behaves.

I am sure they will fix this soon.

Let us know if you have any further questions. Thank you

Hi, Jon 

Sorry for the delay

-

At this time, we did not solve this issue yet,

but a task has been made for our developers,  and they are working on fixing it, first of all for Mozilla on phones,

and they will also do their best to check all other browsers and several phone/device types to see if we can resolve it for all devices and hopefully all browsers, or at least the majority of them ( the ones that our users use)

-

I can't promise an exact ETA, but we are optimistic that it should be fixed in one of the next updates.

You can certainly follow our changeLog page if you'd like, where we state any changes/new features/bug fixes during updates;

and our newsletter, so you're informed about new features, bug fixes, freebies, etc.

Hi, Jon 

You're welcome, i am happy to be of any assistance, in this case unfortunately it is still not finished,

but i can certainly confirm that we have this task on the list for the developers.

They are going through all their tasks as fast as possible and we are confident that they should be able to resolve this very soon.

Thank you for your patience, and understanding.