Load JavaScript skin extensions in standalone WYSIWYG editor by default

Issue created

Marius Dumitru Florea created this issue on 14/Jan/25 11:16

Summary:	Load JavaScript skin extensions in standalone WYSIWYG editor by default
Issue Type:	Improvement
Affects Versions:	16.10.2
Assignee:	Unassigned
Components:	CKEditor, Flamingo Skin
Created:	14/Jan/25 11:16
Priority:	Major
Reporter:	Marius Dumitru Florea
Description:	We have an inconsistency between the standalone WYSIWYG edit mode (currently used when creating a new page and for TextArea properties) and the in-place WYSIWYG edit mode: the JavaScript code is loaded when editing in-place, but not when editing standalone. We have a configuration to enable JavaScript, but it affects only the standalone WYSIWYG edit mode. See also https://forum.xwiki.org/t/load-javascript-skin-extensions-in-standalone-wysiwyg-editor-by-default/16246 . I propose we load JavaScript by default in standalone WYSIWYG edit mode, to be consistent with the in-place edit mode.

Changes by Marius Dumitru Florea on 14/Jan/25 11:16

Fix Version:	17.0.0-rc-1
Assignee:	Marius Dumitru Florea

Marius Dumitru Florea on 14/Jan/25 11:19

FTR, the loadJavaScriptSkinExtensions configuration is used in 3 places:

to decide whether to include the javascript.vm template in the CKEditor content sheet
to decide whether to unprotect scripts tags that are by default protected (neutralized) by CKEditor
to decide whether to allow script tags in the advanced content filter

This message was sent by Atlassian Jira (v9.3.0#930000-sha1:287aeb6)

If image attachments aren't displayed, see this article.