Skip to content
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

[Dropdown] Redundant item text in dropdowns #5237

Open
designosis opened this issue Apr 4, 2017 · 6 comments
Open

[Dropdown] Redundant item text in dropdowns #5237

designosis opened this issue Apr 4, 2017 · 6 comments

Comments

@designosis
Copy link

Currently (via docs), a simple selection dropdown looks like this:

dropdown_unopened

Once clicked, it opens with this:

dropdown_opened

No matter how you look at it, that's 3 options. The user is forced to read the extra line, spending between 30-3000ms (depending on factors like competence, blood sugar, etc.) before recognizing that there are 2 options, not 3. It confuses things, and actively biases the selection. Even a simple "Yes / No" dropdown will read as "Yes Yes No" or "No Yes No". The extra duplicated repeating redundancy is detrimental to UX.

Searching dropdowns obviously must retain the selection. But I'd suggest that in most other cases, the following is vastly preferable:

dropdown_preferable

I'd also suggest that no matter how many items are in the dropdown, upon clicking a dropdown with an existing selection, the dropdown should open with the mouse hovering over the current selection. (In other words, if a dropdown with options 1,2,3,4,5 has option 3 selected, and I click it, I'd suggest the options 1+2 appear above the dropdown, and 4+5 appear below, with the mouse still hovering over 3).

@designosis
Copy link
Author

designosis commented Jul 20, 2017

I'm surprised no-one else has voiced in on this topic. I'm regularly blasted with complaints about this from clients for whom I've implemented Semantic UI solutions. Am I missing something?

@stale
Copy link

stale bot commented Feb 23, 2018

This issue has been automatically marked as stale because it has not had recent activity. It will be closed in 30 days if no further activity occurs. Thank you for your contributions.

@stale stale bot added the stale label Feb 23, 2018
@designosis
Copy link
Author

Both this issue and #6173 are UX blights, deserving of non-stalebotness and further action.

@stale stale bot removed the stale label Feb 23, 2018
@stale
Copy link

stale bot commented May 24, 2018

This issue has been automatically marked as stale because it has not had recent activity. It will be closed in 30 days if no further activity occurs. Thank you for your contributions.

@stale stale bot added the stale label May 24, 2018
@brody4hire
Copy link

??

@stale stale bot removed the stale label May 24, 2018
@lubber-de

This comment was marked as spam.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

4 participants