Summary

Some teams on Cloud have adopted a practice that may not be represented within the Carbon docs. We believe this may be universal:

UX guidance on drop-downs (selects) with only one option

• Leave the dropdown enabled, so users are not puzzled about the reason why it is disabled.
• Offer only this one option. No default/empty option (“Please choose…“) in addition (to avoid unnecessary clicks just to change from empty to the one, obvious choice).

We would love to know Carbon's thoughts on this and whether this guidance should only exist within our PAL. We believe this may be universal as other teams may encounter the same issue. Please note the business justification.

–——

Request inspired by the comment found here by Tim Reiser:
https://ibm-cloudplatform.slack.com/archives/CG2NXH9RU/p1657617241830099

–——

Justification

While we attempt to avoid using dropdowns for scenarios where there is only one available option, sometimes our dropdown experiences are variable and depend on a user's account type or chosen settings. Because of this, we often encounter a scenario where there is only one dropdown option available for users.

Since dropdown is in Carbon's domain, we wonder if Carbon could provide some documentation with this use case in mind.

Screenshots

Potential guidance update:

Your team

Cloud PAL (https://ibm-cloudplatform.slack.com/archives/CGFD1CV4J)

Available extra resources

We are open to chatting about this effort and updating the documentation if the request is approved!

Code of Conduct

• I agree to follow this project's Code of Conduct