[Dropdown] Height variation

[exoego]

Description

This PR adds height variation to dropdown module so that more items can be glanced at once.
This is helpful if dropdown have tons of items (e.g. Countries, States/Providences, Divisions, something like that).

This is usable if every items can be shown at once within the height of window without scroll bar.
If there are so many items that requires scroll bar, user can consider columnar variation proposed in #586.

Screenshot (when possible)

Closes

Closes #545

[lubber-de]

LGTM

[prudho]

Just a semantic note here: hasn't taller more sense that higher ?

[lubber-de]

Higher/ highest or taller/tallest... I am fine with both 😀 what does our native speaker @hammy2899 say?

[y0hami]

IMHO taller doesn't make much sense without more context. The word tall is an adjective so is used to describe something. In this case tall dropdown means that the dropdown is taller then the default height because its describing the height of the dropdown so the user assumes the height will be taller then what it is originally. When using taller dropdown it doesn't have any context of what it is taller than. A good example to this is you don't say "That person is taller" you would say "That person is tall" but with some context you could say "That person is taller than that building" which would make sense.

I think adding words for height will have just as much of a problem as the size modifiers. In FUI we have mini, tiny, small, medium, large, big, huge, massive (in order from smallest to largest) and even English speaking users have problems with deciding which is largest or smaller than the other. Take big and large for example, personally I would argue large should be larger then big but it isn't. This is even more of a problem when none English speaking users try to distinguish them.

I think we need to think more about the terminology we use before we add anything to the framework so we can prevent breaking changes in the future.

[prudho]

And what about long and very long, which are already used by the Placeholder component ?

[y0hami]

@prudho That's a good point and that would also be reusing current terminology.

ref: https://fomantic-ui.com/elements/placeholder.html#line-length

[prudho]

@exoego could you please replace higher and highest classes by long and very long to reuse our current terminology. Thanks !

[exoego]

Changed to long and very long in 5921029

[prudho]

LGTM

[y0hami]

We should also add short and very short so it stays consistent.

[exoego]

I don't think shorter dropdown make sense in terms of end-user readability (showing less items).
But it may be useful if combining with columnar like short columnar dropdown.

If you think consitency is more important, what factors should be for very short and short ?
Is it ok for 0.5 for very short and 0.75 for short?

	very short	short	standard	long	very log
factor	0.5x	0.75x	1x	2x	3x
"@selectionMobileMaxItems"	1.5	2.25	3	6	9
"@selectionTabletMaxItems"	2	3	4	8	12
"@selectionComputerMaxItems"	3	4.5	6	12	18
"@selectionWidescreenMaxItems"	4	6	8	16	24

(unit: items)

[lubber-de]

We should also add short and very short so it stays consistent.

🤔 How should it behave then? So which max-height setting should be set when using short or very short.... i would leave the PR as it is now

[lubber-de]

LGTM

[y0hami]

I think the table @exoego shows is perfect, I would agree that short and very short will not be used much but its best to keep the consistency especially when its a simple change.

[lubber-de]

LGTM

[y0hami]

LGTM