...

• Creating a link will be handled on server side. Client side will make a request to create link and the server will respond to that with a link.
• Links are stored in HTML formatted rich text as they were stored in Magnolia 4. Client side plugin is necessary to render the appearance.

Dialogs

...

Editor with Magnolia link button

...

Image Removed

Choose

...

link dialog

...

CKEditors default link

...

chose dialog (as a reference)

Extensions

It is possible to extend the underlying CKEditor with custom plugins. Normal CKEditor API is extended to enable communications with server side.

...

For developing CKEditor plugins please refer to it's tutorials at http://docs.cksource.com/CKEditor_3.x/Tutorials

Know issues

Problem with iOS and rich-text editing.

CK Editor allows for editing HTML in a WYSIWYG fashion and thus needs a sandbox for it. The standard way of doing such operations is to use an iFrame. Unfortunately, iFrame support in Mobile Safari is far from being ideal. In case of text editing  (any <input> tag is affected) within an iFrame - text selection and sometimes text editing is damaged. For instance, selecting the text block in the middle of a paragraph might be problematic - the cursor jumps to either en end or a beginning of the line. The problem appears when there is an 'ontouchstart' listener in the DOM hierarchy above or on the same level as an iFrame. In our case - this is inevitable.

However, the workaround exists - if the user triggers the magnifier glass to appear, it is possible to select the desire text blocks.

SO discussion links:

http://stackoverflow.com/questions/6876706/text-selection-bug-in-mobile-safari-with-iframes-and-ontouchstart
http://stackoverflow.com/questions/6175455/ipad-input-in-iframe

Apple issue report reference:

http://openradar.appspot.com/12967017