- MikeAsked on January 11, 2016 at 10:42 AM
- BenAnswered on January 11, 2016 at 11:00 AM
JotForm does support Chrome. The reason why I did not mention Chrome is that I personally love FireFox and it is more up to standards than Chrome as well as fully open source, while Chrome contains closed off code above the open source browser Chromium.
Technically any browser can be used to open the forms and use them as well as to use the Form Builder. Internet Explorer being the weakest on the market is supported (version 10 and above for builder and 8 and above for forms), so even the old versions of Chrome run forms and form builder in a nice manner.
You can notice sometimes someone only mentioning IE (Internet Explorer) since that is the browser to test things on, while all others work without much trouble and are often "considered" as working and not mentioned.
I hope that this helps Mike, but please do let us know if you have any further questions and we would be happy to assist with the same :)
- Mike McLoughlinAnswered on January 11, 2016 at 11:09 AM
Thanks for the clarification. However, your devs might want to test version beta 48 using any Chromebook and they should see that drag/drop features do not work (that is without any extensions enabled). This is why I went looking for system requirements in the first place and found your post.
I wonder if there is a flash or Java requirement over and above the browsers mentioned? Chromebooks cannot run Java, of course.
- JotForm SupportBDAVIDAnswered on January 11, 2016 at 01:21 PM
Please try disabling Touch Events: http://ccm.net/faq/40811-google-chrome-how-to-disable-touch-input
That should allow you to drag and drop. Let us know if you need more help.
- Mike McLoughlinAnswered on January 12, 2016 at 03:43 AM
Ah, so Jotforms is switching to touch because it is sensing a touch-enabled device (a Chromebook Pixel). I would suggest your devs consider an alternative method,
Thanks for the tip though.
- CarinaAnswered on January 12, 2016 at 08:33 AM
"so Jotforms is switching to touch because it is sensing a touch-enabled device "
This is something that happens by default inside of the browser when the device has a touchscreen, so it is a browser "limitation" and it can be easily solved by following the suggestion of BDavid.
If you need further assistance please let us know.