Google Chrome Browser

[mmorse]

John just had an extra 'ZimbraWebClient/WebRoot' tacked on there - call it switching between dev & compiled binaries mindset I do that by mistake all the time.

The path in source:
BRANCH/ZimbraWebClient/WebRoot/public/launchZCS.jsp
On your machine becomes:
/opt/zimbra/jetty/webapps/zimbra/public/launchZCS.jsp

We've got a speed test up at: Lets Talk Speed, Chrome, and WebKit » Zimbra :: Blog

[dionrowney]

I noticed the WYSIWYG editor is not used in Chrome. Does it not work correctly and is disabled? or just not tested so not displayed?

anyone tested this with Chrome?

Can it be enabled and work correctly?

D

[gys]

You can make it work in Chrome by turning html mode off and then on again under Options in the compose window. I do notice a stray <br> in a new message body.

[Kallisti]

This gets a bit annoying when replying. I've reverted to FF when replying!

[SGIA]

Hello,
I have made the changes as prescribed here, and CHROME does come up in full AJAX glory, however a few anomalies have surfaced:

• Upon new message composition, the composition field reverts to plain text even though HTML is selected as default.
• Changing the identity does not automatically update the Signature in the composition field.

Seems that maybe there is a slight incompatibility there. For Plain text users I don't think there is an issue through and I haven't found anything else that poses an problem.

The web client is very, very fast in CHROME.

Thanks,
SG

[mmorse]

Please make sure those are filed in bugzilla.