This issue has been created
There is 1 update.
 
 
XWiki Platform / cid:jira-generated-image-avatar-0ed7cb84-8921-42f8-b66e-d3014fc9ac69 XWIKI-25433 Open

Use the iframe-less CKEditor in the standalone WYSIWYG edit mode

 
View issue   ยท   Add comment
 

Issue created

 
cid:jira-generated-image-avatar-5c2b6c91-42fa-406c-a545-ec49db228615 Manuel Leduc created this issue on 21/Oct/26 11:14
 
Summary: Use the iframe-less CKEditor in the standalone WYSIWYG edit mode
Issue Type: cid:jira-generated-image-avatar-0ed7cb84-8921-42f8-b66e-d3014fc9ac69 Improvement
Affects Versions: 17.10.14
Assignee: Unassigned
Components: CKEditor
Created: 21/Oct/26 11:14
Priority: cid:jira-generated-image-static-major-000aeff3-6cd3-47c0-bd60-21b513d74022 Major
Reporter: Manuel Leduc
Description:

The standalone WYSIWYG edit mode (edit action, page creation, TextArea properties, comments) uses an iframe-based CKEditor, while the in-place edit mode uses an iframe-less one. The iframe causes several usability issues:

  • Macros that rely on JavaScript, such as Live Data, are not rendered properly and are not interactive while editing.
  • The edited content does not look and behave like in view mode or in in-place edit mode.
  • Enabling the "Load JavaScript Skin Extensions" configuration only partially helps and can even prevent the editor from loading (XWIKI-23338).

Proposal

Use the iframe-less CKEditor in the standalone WYSIWYG edit mode too, as in in-place edit mode. The edited content then gets the same styles and scripts as in view mode. This is also a step towards dropping the standalone WYSIWYG edit mode entirely. BlockNote already works this way in both edit modes.

The "Load JavaScript Skin Extensions" configuration becomes useless once this is done (see XWIKI-22781).

 
 

1 update

 
cid:jira-generated-image-avatar-5c2b6c91-42fa-406c-a545-ec49db228615 Changes by Manuel Leduc on 21/Oct/26 11:14
 
Assignee: Manuel Leduc