Problem in Google Chrome reply message

[joeld]

I have a issue when i try to reply or forward a HTML message in Zimbra Web Client.

When I click "Reply" button and start to type the text of the message, the cursor focus get outside the body, and automaticaly go to Search Field.

I can just write a reply when a change the original message to "Text Only" in the options.

I use Zimbra 6.0.6 and web cliente 20100505 version.

[phoenix]

Does sending a reply in FF work correctly? If it does I'd suggest you check Bugzilla Main Page - Zimbra for this problem and if there isn't one then file a bug report with full steps to reproduce (including the Chrome version) the problem.

[joeld]

Yes, in FF it's work perfect.

[Athanasius]

Any update on this problem?

FF, IE work OK.

Opera and Chrome, not so much.

Zimbra developers have issues with Chrome??

[bdial]

seeing this as well, happened when I updated to latest version 7.0.517.41

[boskabouter]

Same here: I can confirm that this behavior started after auto-updating to Chrome 7. Use web client 5.0.18 build 20090707. A few additions:

1. If you've set your preferences to compose email in HTML, this problem also occurs when you compose a new email (not just when replying).

2. There's a ticket for this problem in the Chromium project since Oct 1: Issue 57566 - chromium - Zimbra compose is broken - Project Hosting on Google Code. The more Chrome users star this issue, the higher its priority.

3. There's a workaround. If you change the status of the signature back and forward, you can type in the message field.

Needless to say it is a serious problem, because it makes the use of the web client in Chrome very difficult.

[bdial]

strangely i only had this problem for like the first day after the update, and i don't have any issues anymore on either linux or windows with chrome 7 & zcs 6.0.8

[mcenkner]

I hope this can get fixed because I prefer Chrome.

[chower]

I'm following the google code bug in boskabouter's post. I suggest you all star it to get a little more oomph behind it. I see there is some activity, so I'm keeping my fingers crossed

[sampowers]

Is there a zimbra bug for this yet so I can vote for it? If you chase this down to the WebKit bug they're talking about, it looks like Zimbra is trying to work around a bug that doesn't exist anymore, and needs to send webkit down the gecko codepath in this case.

I don't think the fix is going to come from the browser end.

See https://bugs.webkit.org/show_bug.cgi?id=48201