You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
In this issue, a user was not aware of additional options or the ability to scroll. I propose 2 options here.
The simple/quick option
We adopt a design principle for this component around applying max heights that include a peaking option. So perhaps the component is smart enough to know the height of options and self assign a max height that is something like true max minus half of one option. Or we simply state that this should be the desired outcome and the implementation assigns the max height that allows for a peeking option.
The over-engineered option
When options go higher than the max height of the container we add a scroll indicator:
Here you see a gradient overlay and two arrows indicating there is more to see. We'd need to clear this indicator any time a scroll event takes place. There's likely some subtlety to play with here around mouse over events, maybe the indicator slowly fades away.
The text was updated successfully, but these errors were encountered:
In this issue, a user was not aware of additional options or the ability to scroll. I propose 2 options here.
The simple/quick option
We adopt a design principle for this component around applying max heights that include a peaking option. So perhaps the component is smart enough to know the height of options and self assign a max height that is something like
true max minus half of one option
. Or we simply state that this should be the desired outcome and the implementation assigns the max height that allows for a peeking option.The over-engineered option
When options go higher than the max height of the container we add a scroll indicator:
![image](https://private-user-images.githubusercontent.com/6776415/239980414-eb770d9e-8576-4a22-a0e8-895cc1b217c2.png?jwt=eyJhbGciOiJIUzI1NiIsInR5cCI6IkpXVCJ9.eyJpc3MiOiJnaXRodWIuY29tIiwiYXVkIjoicmF3LmdpdGh1YnVzZXJjb250ZW50LmNvbSIsImtleSI6ImtleTUiLCJleHAiOjE3Mzk2OTUyODEsIm5iZiI6MTczOTY5NDk4MSwicGF0aCI6Ii82Nzc2NDE1LzIzOTk4MDQxNC1lYjc3MGQ5ZS04NTc2LTRhMjItYTBlOC04OTVjYzFiMjE3YzIucG5nP1gtQW16LUFsZ29yaXRobT1BV1M0LUhNQUMtU0hBMjU2JlgtQW16LUNyZWRlbnRpYWw9QUtJQVZDT0RZTFNBNTNQUUs0WkElMkYyMDI1MDIxNiUyRnVzLWVhc3QtMSUyRnMzJTJGYXdzNF9yZXF1ZXN0JlgtQW16LURhdGU9MjAyNTAyMTZUMDgzNjIxWiZYLUFtei1FeHBpcmVzPTMwMCZYLUFtei1TaWduYXR1cmU9MjU2MDJiYjA1NmEyNmMyNjJjNzgyMWJlMzIwNDdlZDI3NDU2MmIyYjA1YTgzMGQwZjg2MGJjYTFkYTJkNjQ5MSZYLUFtei1TaWduZWRIZWFkZXJzPWhvc3QifQ.37wULj4ZKWWIMaP50wTPY1o9qz5VhZGfYHjrhN3ibMY)
Here you see a gradient overlay and two arrows indicating there is more to see. We'd need to clear this indicator any time a scroll event takes place. There's likely some subtlety to play with here around mouse over events, maybe the indicator slowly fades away.
The text was updated successfully, but these errors were encountered: