Problems with fields and scripts in Google Chrome

[Frederk]

Hello,

 

We've been using IWP for over a year now, we use it for daily reporting and inscriptions etc..

We've always insisted on people using internet explorer as their web browser because everything works (99% of the time) without issues.

Now with the latest developments and such, alot of our users use Google Chrome to access and update their data.

The one and serious problem we encounter with all these users is that they cannot access certain fields or cannot even use scripts which work perfectly fine while using IE.

 

For example on our inscription page, we have a radio button in which people indicate which language they speak, in IE you can click and change language at will, in Google Chrome you click and nothing happens, as if you cannot even access the field. And for scripts where the hand over cursor appears in IE, in Chrome the hand does not appear.

 

Users using Mac seems to be having the same issues as well, or even worse.

 

Do I have to change anything in settings to allow Chrome to function properly?

Has anyone encountered this problem before?

 

Any help anyone could give would be greatly appreciated since this tool is a vital part of our company's future.

 

Thank you,

Frederik

[Josh Ormond]

One of the main things I've seen that doesn't work well in IWP across various browsers is layered objects, where the button is under other objects...and/or there is transparency on one of the object.

 

The best thing to do is see what is different between the fields that work fine in Chrome, and the ones that don't. Radio buttons in general have always been wonky in IWP.  Because Chrome is slightly more standards compliant than IE, some things work in IE where they don't in other browsers. You may need to simplify or alter some of the UI elements to get around the limits of IWP. Perhaps using a dropbox box instead of a radio button set...or straight-up buttons that set the language.

[Frederk]

Hello,

 

Thank you very much for the info, it was indeed the issue that we have alot of layered objects.

I've removed all off the extra's and concentrated on the basics and everything seems to be working now sofar.