-
iMatterAsked on September 14, 2016 at 10:55 AM
Is there a problem with the Next button working reliably on certain platforms? I had a knowledgeable user of my form having problems with the next buttons not working (meaning pressing them and nothing happening). I didn't see the issue myself - but I watched him have the issue over a video call. Eventually it worked for him - but it took awhile.
Here are the platforms that he tried it on:
PC(Windows 10)-Google Chrome Stable Channel
PC(Windows 10)-Microsoft Edge
Chromebook(ChromeOS)-Google Chrome Beta Channel
Chromebook(Linux via crouton)-Google Chrome Stable Channel
Page URL: https://form.jotform.com/52046858986169 -
BJoannaReplied on September 14, 2016 at 12:37 PM
I have tested your form on Windows 10 in Google Chrome and Microsoft Edge, but I was not able to replicate mentioned issue. Next and Back buttons are working properly.
Were you able to replicate mentioned issue? Also did your other users reported same issue?
Maybe it was a temporary issue.
In case that your form is embedded and mentioned issue occurred on embedded form, please provide us URL of your webpage, so that we can test your form there.
Let us know if you need further assistance.
-
iMatterReplied on September 16, 2016 at 7:00 PM
It is embedded here:
http://www.imatteryouth.org/report-card-start/
Though it starts as a separate jotform that links to the one in question
-
BJoannaReplied on September 16, 2016 at 8:21 PM
Form that is embedded on webpage you provided is not same as the form you are having issues with. I have tested your embedded form and when I submitted that form I go redirected to your other form, but again I was not able to replicate mentioned issue. Next and back buttons are working properly on my end.
If only one user reported this issue and if you are also not able to replicate it, then most likely this issue is related to browser or device of that particular user. You sad that eventually that user was also able to submit the form. Maybe it was a temporary issue.
Did other users reported same issue? Were you able to replicate it?
Looking forward to your reply.