All of a sudden my form will not render on an android mobile Chrome window.

  • HighWheelerTrainShow
    Asked on February 22, 2016 at 10:07 PM

     I started getting a 403 forbidden message. Looking at Chrome options I found "request a desktop site." Then it renders? How do my users get to the form without manual intervention? The entire site is mobile responsive. What do I need to change to allow the form to open?

    Main site: http://www.highwheelertrainshow.com/

    Bread crumbs: Admission > Click for a kid's free pass > Click for a kid's free pass

    Form page: https://form.jotform.com/52026912444955

    Thanks,  Jim Osborn

  • Ashwin JotForm Support
    Replied on February 23, 2016 at 5:02 AM

    Hello Jim,

    I did check your website in chrome browser of my android mobile device and it seems to display the form correctly when we click on the "Click for Kids' FREE Passes" > "Click for a kid's free pass" (If displays a direct link to JotForm".

    I am unable to see any "Bread crumbs" text anywhere in the site. I am also not able to see if there is any mobile specific site as unable to see the link "Request a desktop site".

    I would suggest you to please share a screenshot of the link "Bread crumbs" and we will take a look.

    We will wait for your response.

    Thank you!

  • HighWheelerTrainShow
    Replied on February 23, 2016 at 8:32 AM

    The issue is that the Chrome browser on a mobile has an option at the bottom of its pull-down menu that is "Request Desktop Site". Once I clicked on that the form rendered -- and continues to render okay with subsequent visits and refreshes.  

    This is something I have never seen before so I suspect it came with a recent update? My question is what can be done with the form to make sure other users visiting the form page for the first time do not get the "Forbidden 403" blank page error?  With the Forbidden 403 error showing, if you click on the Chrome  "Request a Desktop Site" pull down menu option the form renders okay - and continues to do so.

    I have tried clicking the Request a Desktop site option on other pages (not my site)  that are not mobile responsive and I get a larger view of the page - so I suspect it has to do with Google's attempt to enlarge non-mobile responsive pages with a scroll bar at the bottom?

    Forget about my bread crumbs comment - I was just trying to lead you to the form page. Should have used "path" or something like that.

    Jim

  • Kiran Support Team Lead
    Replied on February 23, 2016 at 11:56 AM

    I've checked your website using an Android emulator (Samsung S4) and see that the web pages are displayed normally and without any issue. I also see that the form is not embedded on your web page and linked directly to load on a different tab. The JotForm linked is also loading normally on a mobile without any issues on my first visit itself. Please see the screenshot below:

    All of a sudden my form will not render on an android mobile Chrome window Screenshot 20

    Could you try checking the form in a private/incognito window or using a different mobile to see if that works for you? Please get back to us if the issue still persists. We will be happy to assist you further. 

  • HighWheelerTrainShow
    Replied on February 23, 2016 at 5:06 PM

    Thank you for your efforts. I am only guessing but it may have to do with opening a new tab that is not mobile responsive - so I have removed the blank target attribute associated with the link. I have 2 android phones of different ilk and the situation occurred on both. Once the "Request Desktop site" option has been selected, I have not seen the error page again on either phone. This was not a issue with any Apple product or prior versions of Androids. Unless someone has any specific knowledge of this Chrome function, I think we can close the question for now. On the positive side, I have not received any user complaints so far. Thanks again for your assistance. 

    Jim Osborn

  • Ashwin JotForm Support
    Replied on February 23, 2016 at 9:29 PM

    Hello Jim,

    On behalf of my colleague, you are welcome.

    We will further check this chrome behaviour on Android and get back to you if I have some relevant information.

    Thank you!