Use number fields and lists of values for the parameters of the attachment picker macros

The attachment picker macros take sizes, file types and class properties in plain text fields of the Edit Macro dialog, so the user has to know the expected values and a wrong one is accepted silently.

The macros to change, with the file where most of the fix is done:

• attachmentSelector: AttachmentSelector.xml.
• attachmentGalleryPicker: AttachmentGalleryPickerMacroParameters.java.

The main problems:

• The width and height of attachmentSelector are numbers of pixels declared as strings.
• The filters take file extensions or media types typed by hand, while the common ones could be offered, keeping any other value possible.
• The property of attachmentSelector is a property of the class chosen in classname, so its list of values depends on that field.

Depends on

Most of these fields cannot be offered before these generic changes, each giving the macro the means to declare the expected value:

• XWIKI-25182, which gives a number input to the parameters of a numeric type.
• XWIKI-25197, which lets a wiki macro parameter declare its minimum and maximum.
• XWIKI-23045, which lets a parameter get its values from a provider, with or without custom values.
• XWIKI-25180, which lets a parameter depend on another one, whose value its list of values follows.

KOs covered

Impact found on macro fluidity

These 5 KOs come from the WYSIWYG usability audit of the macros, under the criterion C4 input-assistance 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 declaration of the parameters in the macro definitions.