Details
-
Improvement
-
Resolution: Unresolved
-
Major
-
17.10.14
-
None
-
Unknown
-
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).
Attachments
Issue Links
- blocks
-
XWIKI-25434 Deprecate the Load JavaScript Skin Extensions configuration of the CKEditor
-
- Open
-
- relates to
-
XWIKI-23338 The Standalone WYSIWYG editor doesn't load in Firefox after enabling the "Load JavaScript Skin Extensions" configuration
-
- Open
-
-
XWIKI-22781 Load JavaScript skin extensions in standalone WYSIWYG editor by default
-
- Closed
-