id summary reporter owner description type status priority milestone component version resolution keywords cc 10208 Need ability to override a value in CKEDITOR.skins.icons[] Zac Morris "Currently there is no way to override a value that has already been registered in CKEDITOR.skins.icon[] via CKEDITOR.skins.addIcon. I propose adding an additional parameter (after the parameter changes I proposed in Ticket #10206[https://dev.ckeditor.com/ticket/10206]) that would allow a call to addIcon to override any existing value. This would allow ""post build"" changes of a skin (via skin.js of the skin), by the end user, without having to rebuild the skin to see the change. As it stands today, if a user wants to change even just a single icon they basically need to create a new skin from source, and either run that skin ""unbuilt"", or ""build"" the new skin to regenerate a new icons.png for the new skin. That may be the desired ""way"" but I don't think it gives end-users enough flexibility in those situations where their corporate UI guidelines may require a certain look-and-feel that requires using pre-provided image files. Adding the additional override parameter, provides the following example option: I could edit the ""built"" version of the kama skin, and add the following to the top of its skin.js CKEDITOR.skin.addIcon('Underline','{path to my corporate provided sprites file.png}',-52,-128,true); such that when I init CKEDITOR this line would override the ""default' kama icon to use my own. Yes, that may seem ""unoptimized"", but in most cases the page that I'm using CKEditor on, has already loaded this image file for other elements, meaning it's just as optimized as using the build generated icons.png." New Feature closed Normal UI : Skins 4.0 Beta wontfix Skins