When a user adds a multiselect field, they add choices in order. This order is preserved throughout the app and not editable. This is not ideal and is discussed here: https://github.com/OpenTreeMap/otm-core/issues/2480
The android UI violates this preservation by allowing the user to modify the order in which choices are included in the field.
For example, If I add field choicez with choices 'A', 'B', 'C', the webapp will allow values:
ABC
AB
AC
A
BC
B
C
the android all will allow unordered values, for example:
BAC
When a user adds a multiselect field, they add choices in order. This order is preserved throughout the app and not editable. This is not ideal and is discussed here: https://github.com/OpenTreeMap/otm-core/issues/2480
The android UI violates this preservation by allowing the user to modify the order in which choices are included in the field.
For example, If I add field
choicez
with choices'A', 'B', 'C'
, the webapp will allow values: ABC AB AC A BC B Cthe android all will allow unordered values, for example: BAC