| A static tree is described by the content of the tree macro, a nested list of nodes in wiki syntax. The macro declares this content as a plain string, so the WYSIWYG editor never edits it in place: the editor shows the list, which cannot be edited, and adding, renaming or moving a node needs the Edit Macro dialog, where the nodes are typed as a wiki syntax list. Right after the insertion from Quick Actions, the macro has no content area at all, so the text typed next goes outside the macro. The fix is done in Tree.xml:
- Declare the content as rich text, so that the editor edits the nodes in place as a nested list, with the list tools of the editor to indent and outdent them.
- Keep a content area to type in when the tree is empty, so that the cursor can be put there after the insertion, see XWIKI-25569.
KOs covered
| Macro |
Criterion |
Problem |
| tree |
E6 inplace |
For a static tree, the content is not edited in place: the list shows in the editor but cannot be edited, and the content can only be changed in the plain text area of the Edit Macro dialog, in wiki syntax. |
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-25569, so that the cursor can be put in the content of the tree after the insertion. |
