Hitting Return in Safari Moves Cursor to Top

Problem reported by Jason Cross - 9/29/2014 at 9:06 AM

Resolved

Hello. We are running Smartermail 12.4.5364. When a Safari user (Mac) is composing an email using webmail, every time they hit enter, the cursor jumps back to the top of the editor.

13 Replies

Reply to Thread

Employee Replied

9/29/2014 at 12:16 PM

Employee Post

This was a bug with the CKEditor. They have recently published a fix for the bug that we have integrated into SmarterMail and that we are currently testing. The fix will be included in the next minor update.

A workaround, you can press SHIFT-ENTER or if the cursor is placed before the last character, then CR/LF works "properly."

k 123 Replied

10/6/2014 at 2:19 PM

That has been driving me crazy for the past week or so too! Thanks for the post, now I know it's not something I accidentally changed in my computer settings or Smartermail settings.

I hope it get fixed soon, it's so annoying.

Michael Schuler Replied

10/21/2014 at 1:01 PM

Robert,

Do you have a timeline on the next minor release?

I've been seeing this issue in Safari 8 myself and now that OS X Yosemite is out and going, we might be getting more people having trouble with this.

Thanks!

Mike

Leo Novelli Replied

10/21/2014 at 2:02 PM

Same problem here. Thanks Robert Emmett for giving us the SHIFT-ENTER workaround!

Employee Replied

10/21/2014 at 2:25 PM

Employee Post

We are aiming for a Thursday, 23 October, minor release (subject to change). The fix will be include in that release.

Michael Schuler Replied

10/21/2014 at 2:31 PM

Sounds good. I'll watch out for it then or a bit after if there's last minute changes. Thanks!

hankeg Replied

4/1/2015 at 6:56 PM

Has this issue ever been resolved. It is present on Safari 7.1.4

Steve Reid Replied

4/2/2015 at 5:51 AM

This thread clearly states it has been resolved. Have you updated your installation of smartermail?

hankeg Replied

4/2/2015 at 7:18 AM

Updated four days ago.

Steve Reid Replied

4/2/2015 at 7:32 AM

what version did you update to? Because if it's newer than last October the fix is supposed to be in there. Since this is obviously a bug if you open a ticket it should be refunded.