Changes for page Customization

Last modified by Vincent Massol on 2024/03/27 13:33

<
From version < 5.1 >
edited by Marius Dumitru Florea
on 2018/11/21 11:34
To version < 6.1 >
edited by Marius Dumitru Florea
on 2018/11/21 11:40
>
Change comment: There is no comment for this version

Summary

Details

Page properties
Content
... ... @@ -145,11 +145,11 @@
145 145  {{/code}}
146 146  )))
147 147  
148 -== Load the JavaScript code inside the editing area (XWiki 10.10+) ==
148 +== Execute JavaScript code inside the editing area (XWiki 10.10+) ==
149 149  
150 -The sheet (##CKEditor.ContentSheet##) used to render the content of the edited page inside the editing area doesn't load, by default, the JavaScript code required by the edited content. This means, for instance, that if the edited content is using a macro that requires some JavaScript code in order to be displayed properly then that JavaScript code is not loaded and thus the macro output doesn't look good inside the editing area. There are multiple reasons for this behavior:
150 +The sheet (##CKEditor.ContentSheet##) used to render the content of the edited page inside the editing area doesn't load, by default, the JavaScript code required by the edited content. This means, for instance, that if the edited content is using a macro that requires some JavaScript code in order to be displayed properly then that JavaScript code is not executed and thus the macro output doesn't look good inside the editing area. There are multiple reasons for this behavior:
151 151  
152 -* loading the JavaScript code slows down the editor
152 +* loading and executing the JavaScript code slows down the editor
153 153  * the JavaScript code could modify the edited content (outside of the protected macro output) and these changes would be saved
154 154  * the JavaScript code could throw exceptions or interfere with the CKEditor code thus breaking the editor which may lead to content loss
155 155  * executing the JavaScript code opens the door to XSS attacks

Get Connected