| The content of the cache macro is rich text, but the WYSIWYG editor never edits it in place, not even right after the insertion: the editor shows the rendered content as a read-only widget, and changing it needs the Edit Macro dialog, where it is a plain text area in the syntax of the page. Its sibling, the async macro, has its content edited in place right after the insertion. The fix is done in CacheMacro.java: mark the output of the content as editable in place, as the macros whose content is edited in place do, so that the editor can edit it, also after the page is saved and reopened. KOs covered
| Macro |
Criterion |
Problem |
| cache |
E6 inplace |
The content is never edited in place, not even right after the insertion: the editor shows the rendered content, and changing it needs the Edit Macro dialog, where it is a plain text area in the syntax of the page. |
Impact found on macro fluidity This KO comes from the WYSIWYG usability audit of the macros, under the criterion E6 inplace of its usability criteria, which asks that the content is edited in place, with an editing experience suited to its data, not in a text area of the Edit Macro dialog. The page of the macro, linked in the table, has the full notes and the steps to reproduce. It is also needed by XWIKI-25563, so that the Quick Action can insert the macro without the Edit Macro dialog. |
