Details
-
Improvement
-
Resolution: Unresolved
-
Major
-
None
-
17.10.14, 18.8.0
-
None
-
Unknown
-
Description
The Edit Macro dialog of the Notifications macro shows its 14 fields in alphabetical order: the parameter that switches between the two uses of the macro comes 12th, below the fold, while display options that are rarely changed are shown with the main ones instead of as advanced parameters.
KOs covered
| Macro | Criterion | Parameters | Problem |
|---|---|---|---|
| notifications | C6 order | useUserPreferences | The switch between the two uses of the macro, the reader's own notifications or the activity of a part of the wiki, set by the third example of the documentation, is the 12th of the 14 fields and is only visible after scrolling. No order is declared, so the dialog sorts the fields by parameter ID. |
| notifications | C8 advanced | displaySystemEvents | Rarely used, since the events XWiki triggers itself, like extension updates, are of little use in a list of changes, and not marked as advanced. |
| notifications | C8 advanced | displayReadEvents | Rarely used, since the read marks are personal and mostly matter for the reader's own notifications, and not marked as advanced. |
| notifications | C8 advanced | displayReadStatus | Rarely used, a display detail, and not marked as advanced. |
Impact found on macro fluidity
These 4 KOs come from the WYSIWYG usability audit of the macros, under the criteria C6 order, C8 advanced of its usability criteria. The page of each macro, linked in the table, has the full notes and the steps to reproduce. Fixing them means changing the parameter declarations of the macros: their groups, order, default values, mandatory and advanced flags.