Changes between Version 2 and Version 3 of Ticket #12387, comment 11
- Timestamp:
- Jan 12, 2015, 12:14:20 PM (9 years ago)
Legend:
- Unmodified
- Added
- Removed
- Modified
-
Ticket #12387, comment 11
v2 v3 1 No skin is set up in CKEditor until you create the first editor instance. When the first skin is loaded, all CSS files are loaded as well. If you wanted to create a new editor instance with a diffrent skin, you should unload the CSS files which are connected with the first skin. At the moment no such mechanism exists for CKEditor, though. This solution might also break the previous CKEditor instance.1 No skin is set up in CKEditor until the first editor instance is created. When the first skin is loaded, all CSS files are loaded as well. If next editor instance is created with a diffrent skin, to make it work, previous CSS files, which are connected with the first skin, should be unloaded. At the moment no such mechanism exists for CKEditor, though. This solution might also break the previous CKEditor instance. 2 2 3 I you create the '''first''' editor instance with a custom skin, everything should work well because nothing is set up yet.3 If you create the '''first''' editor instance with a custom skin, everything should work well because nothing is set up yet. 4 4 5 If you have an existing instance on the page and want to create a new instance with a custom skin, the only solution se ms to be to create an instance in the scope i.e. in an iframe.5 If you have an existing instance on the page and want to create a new instance with a custom skin, the only solution seems to be to create an instance in the scope i.e. in an iframe.
