New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Research: Inactive Dropdown Options Mistaken For Disabled #2530
Comments
@bstifle can you take a look at this one |
This is tricky since there are only two options.
I recommend option 2 since it is the most clear and requires less clicks |
@andrewctate were you able to take a look at those solutions? |
Hi @bstifle. Thanks for your solutions comment. I did see it, but assumed it was directed at the Calcite Components team. We fixed the problem on our end by overriding the text color. I opened this issue just to share the feedback we received in case your team found it useful in considering any changes to this styling in Thanks for your time in researching this for me, and I apologize that I wasn't more clear. |
@andrewctate can you share a screenshot on your solution? Thanks! |
Closing in favor of a similar request on |
Background
We recently used dropdown Calcite components in the Hub application and got feedback from users that the lighter, inactive text color that shows on the
calcite-dropdown-item
sometimes led to dropdown options being mistaken for being disabled when they were really just not active.Desired Outcome
See if it might be worth denoting inactive options in a way that isn't easily confused with a disabled state.
The text was updated successfully, but these errors were encountered: