Dedicated Browser Hacks

This website contains links to software which is either no longer maintained or will be supported only until the end of 2019 (CKFinder 2). For the latest documentation about current CKSource projects, including software like CKEditor 4/CKEditor 5, CKFinder 3, Cloud Services, Letters, Accessibility Checker, please visit the new documentation website.

If you look for an information about very old versions of CKEditor, FCKeditor and CKFinder check also the CKEditor forum, which was closed in 2015. If not, please head to StackOverflow for support.

(Created page with "{{#CUSTOMTITLE:Dedicated Browser Hacks}} Skins are basically CSS styling on the DOM structure that represents the editor. Fortunately the world is going into a direction where...")
 
(No difference)

Latest revision as of 17:16, 26 July 2012

Skins are basically CSS styling on the DOM structure that represents the editor. Fortunately the world is going into a direction where browsers are aligning their CSS features to standards, which makes it easier to design CSS that works everywhere.

But still the world is not perfect and we have small differences on CSS among browsers. Additionally, CKEditor must support ancient browsers, which are more limited and buggy.

To make it easier to maintain the skin CSS, CKEditor makes it possible to define browser specific files, which hold all "hacks" necessary for them. For example, a skin can contain the editor_ie.css file with all IE hacks or dialog_opera.css for Opera specific stuff.

A skin must instruct CKEditor to load, for example, editor_ie.css instead of editor.css on IE browsers. This must be done by setting the CKEDITOR.skin.ua_editor value to the list of "browser files" available. The same can be done for dialog.css. Check out the skin.js file of the Kama skin for a real example.

This page was last edited on 26 July 2012, at 17:16.