-
Type: Clean up
-
Status: Open
-
Priority: Minor
-
Resolution: Unresolved
-
Affects Version/s: None
-
Fix Version/s: None
-
Component/s: Selectivity
-
Tags:
-
Team:UI
Currently, <nuxeo-selectivity> specifies templates for single a multiple selection templates that are hugely different. Not only these templates use different CSS classes, it is almost impossible to properly map equivalents between the two.
CSS classes in single selection:
- selectivity-single-select
- selectivity-single-select-input
- selectivity-single-result-container
CSS classes in multiple selection:
- selectivity-multiple-input-container
- selectivity-multiple-input
- selectivity-placeholder
- selectivity-clearfix
The goal would be to propose a unification of these templates (as much as possible), making it so that both can share a base template and styles.
Advantages:
- Improved consistency between single and multiple selection UI/UX.
- Improved readability and maintainability.
- Avoids issues like
ELEMENTS-1181andELEMENTS-1189.
Disadvantages:
- Backports (to 10.10 and older) will be less straightforward.
- Can introduce regressions (specially on edge cases) if not handled and tested thoroughly.
- is related to
-
ELEMENTS-1181 Fix dropdown for multivalued directory field in Web UI
- Resolved
-
ELEMENTS-1189 Fix offset arrow down icon in nuxeo-selectivity when using a label
- Resolved