Web-enabled forms on "Google Chrome"

[ConvertFromOldNGs]

by Rich >> Wed, 3 Sep 2008 11:38:22 GMT

Hi,

Today Google released their new web browser called "Chrome" (at least, they did on the UK homepage). Due to the inevitable popularity of this browser i thought it was important to ensure all of our web services functionality exist on it. However, we have found that the web-enabled forms do not work at all! Or at least, very little of them do.

The web-enabled forms are made up of usual controls such as text boxes, labels and buttons, none of which are displaying properly. Also, we are using pictures mapped to the buttons which also do not display. We were aware that our browser did not work fully as intended on Mozilla Firefox but have always had a much larger amount of traffic using IE so didn't feel the need at the time. We are concerned that Google Chrome may prove to be much more popular and so would like to be ahead of the game this time.

Does anybody have any experience making web-enabled forms work over Mozilla Firefox? Maybe somebody already has used Google Chrome with their services?

Any help will be appreciated.

Regards,

Rich

[ConvertFromOldNGs]

by Dean Cooper >> Wed, 3 Sep 2008 12:29:33 GMT

You could try enabling Cross Browser Compatibility for your web application (on the Web Options sheet of the Define Application dialog). Be aware that this may change the IE behaviour you currently have though.

Dean.

[ConvertFromOldNGs]

by Dean Cooper >> Thu, 4 Sep 2008 20:51:26 GMT

You could also try leaving the Cross Browser Compatibility setting unchanged and setting this in the [WebOptions] section of the ini file:

UseHTML4ForNetscape=true

This from the JadeIni.pdf manual: The UseHTML4ForNetscape parameter specifies whether HTML generation for Netscape and Mozilla browsers is similar to that for Internet Explorer. The default value is false.

Dean.

[ConvertFromOldNGs]

by Rich >> Fri, 5 Sep 2008 14:05:23 GMT

Hi Dean,

Thanks for your suggestions. I have tried both and they both improve the situation a great deal, however, there is still one thing that does not work with either...

Rather than using normal Jade buttons, we are using WebEventMapping's in the forms load method to map a buttons click method onto a picture - therefore making it more user friendly. It seems that although everything else now works, including buttons without picture mappings, the buttons that do have them cannot be used.

Do you know any way that we can still have workable picture mappings of our buttons on Mozilla browsers?

Thanks again

Rich