CKEditor Buggy on Safari

[CaelanStewart]

Hi All,

On Safari 7.1+, the CKEditor version shipped with ProcessWire is so buggy it's unusable.

For instance, if I type a line of text and press enter, it moves the caret to the start of the line. The expected behaviour would be to create a new paragraph and move the caret into it.

The version of CKEditor shipped with ProcessWire is 4.4.3, the issue was fixed in 4.4.5. See changelog entry for 4.4.5:

Fixed Issues:

* [#12423](http://dev.ckeditor.com/ticket/12423): [Safari7.1+] Fixed: *Enter* key moved cursor to a strange position.

I saved a backup, and then overwrote the original 4.4.3 files with the files from 4.4.5 barring some config files with no issue. Anything above that and the instance would not be created.

The question is, is ProcessWire going to be upgrading this in their next version? I'd be silly not to.

FYI, The latest CKEditor version is 4.4.7.

[pwired]

Is the client going to use the editor when the website is finished ?

If not, why bother, you only need it for entering text, not editing.

You edit all you want in your css.

it moves the caret to the start of the line.

Check if you don't have too many processes running in the background on your pc,

one of them might have focus on the editor window and cause interference.

[CaelanStewart]

Is the client going to use the editor when the website is finished ?

If not, why bother, you only need it for entering text, not editing.

You edit all you want in your css.

Yes, the CMS will be used by clients.

Even when entering text, and then making a quick edit, you can't. As soon as you enter a new line, it messes stuff up. CKEditor (≤ 4.4.4) is unusable on Safari 7.1+. There is no reason I can see that it shouldn't be upgraded. Would that not be a naive decision to leave this unfixed? Especially since this is an easy fix, and it causes the editor to be unusable?

This problem was even more of an issue because we installed the ProcessWire blog module, which used the version of CKEditor pre-packed with ProcessWire. You couldn't edit text, or write new text at all, unless you switched browser. But we can't say to the client, you can't use Safari because the editor doesn't work on that. They won't have it. The client's knowledge is limited, and the client just wants to edit the way he/she normally edits stuff. No faff.

Obviously I can just do what I've already done each time we use ProcessWire, but surely it shouldn't be up to the user to fix bugs just so they can use ProcessWire?

[totoff]

Hi Caelan,

did you file a bug report? https://github.com/ryancramerdesign/ProcessWire/issues

You may want to do so.

[pwired]

Are you editing online on the server, or local ?

Check if the same problem is there when editing locally and online.

Check what happens with another browser.

I have read somewhere that you can re-install TinyMCE so that would

be an easy option. (if ckeditor really is the problem)

There's more of them:

http://modules.processwire.com/modules/fredi/

http://modules.processwire.com/modules/inputfield-ace-editor/

[CaelanStewart]

Hi Caelan,

did you file a bug report? https://github.com/ryancramerdesign/ProcessWire/issues

You may want to do so.

I certainly shall do.

Are you editing online on the server, or local ?

Check if the same problem is there when editing locally and online.

Check what happens with another browser.

I have read somewhere that you can re-install TinyMCE so that would

be an easy option. (if ckeditor really is the problem)

There's more of them:

http://modules.processwire.com/modules/fredi/

http://modules.processwire.com/modules/inputfield-ace-editor/

It is not an issue that is causing us bother, it only took me 5 minutes to fix by upgrading the version of CKEditor that comes pre-packed with ProcessWire.

The issue is with CKEditor and Safari. Safari uses a version of webkit that introduced a serious bug in the use query selectors (still not fixed either). So CKEditor introduced a fix so that CKEditor would function on Safari. I reference the posts on this CKEditor support ticket:

http://dev.ckeditor.com/ticket/12423

[pwired]

Ok glad you fixed it, it's not easy is it to stay compatible with all those different browsers out there.

Had recently a problem my self with html5 audio and video tags.

Those html5 players all look different on different browsers.

[WillyC]

try.dev branche it user.4.4.6 for.monthes

[Pierre-Luc]

I submit a patch to Ryan a few weeks ago who applied it, it's live in dev but if you want it in stable just download the latest ckeditor full package and overwrite the current one. No need to send a bug report.

[creativejay]

Oh thanks for this!

I've also noticed similar behavior in WYSIWYG editors (assuming based on, if not exactly CKEditor) such as the editor in Blogger. Glad I can update this and remove the warning for Safari users!