-
Notifications
You must be signed in to change notification settings - Fork 570
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
[2] Dropdown Improvements #2149
Comments
@startailcoon to be honest I'm not following the idea... can you clarify please? Do you mean that currently selected item has the same background as hovered items? |
Please check that you can also select with keyboard (up and down moves the selection, enter confirms it) |
@wmbutler, could you clarify your thoughts on this matter? |
I'll claim this. |
Here is my proposed change. I think what was most confusing was the hover color. Typically, I'd expect a higher contrast for the selected item. The midnight view makes higher contrast virtually impossible with a background color, so I updated the style guide to reflect only a blue color for active/hover states on the text menu items. I think it looks pretty good. It took me two hours to hunt through all the variations. |
@wmbutler Unfortunately your changes will work but only till next update from my side, because you changed source file instead of config file which uses to build themes. There is instruction how to update styles on the right way - https://github.com/bitshares/bitshares-ui-style-guide/blob/master/INSTRUCTIONS.md#how-to-manage-styles-of-style-guide-components- I'll open new issue to fix it |
Oops. Sorry. I'll review. |
I just read your instructions and saw no mention of a |
@wmbutler There are few ways to get your task done.
@wmbutler Lets make it more faster - give me color you need, I'll update it and we will keep your hours and I'll put my hours and we finally will close this task. |
@wmbutler this is how it should be updated:
bitshares/bitshares-ui-style-guide@a244b09#diff-bd9e7d6072b9e6de78f2e08cd951e508 |
Issue extracted from #2020
By @wmbutler
The text was updated successfully, but these errors were encountered: