[Gabe] Q: how is the default height of the Dropdown determined?
Is it determined by maximum number of visible dropdown items? More nuanced, e.g. never taller than the viewport?
[Vlad] Should this be responsive? E.g., 5 items for mobile-sized viewport; 10 items for desktop.
Might be worth testing in mobile specifically.
[Brian] Screen width can be large while having a narrow height. Our breakpoints are width-only.
[Ben]: narrow height probably not as big of a concern.
Should we simplify to just pick a constant number?
[Adam] What about responsiveness based on the container the Dropdown is rendered in? Rendered container width !== always equal viewport responsiveness.
[Brian] Are there existing use cases of Dropdown in platform today we could draw from as prior art?
[Ben] semantic ui provides decent Dropdown examples to compare against our Bootstrap-based Dropdown.
See screenshots on the GitHub issue from semantic-ui's handling of Dropdown responsiveness.
[Mahdiye] Are there alternative UI paradigms to consider here?
Q: Is there a search box within Dropdown?
Yes? Actually, no. Some consumers extend Dropdown to include a custom search, but this is not upstream in Paragon itself.
How does this relate to usage guidelines around Form.Autosuggest? Should the “max number of items displayed” consideration apply to Form.Autosuggest as well.
Tenative decision: reduce number of items displayed in Dropdown based on responsiveness. Details TBD.