Skip to content

Select component implementations inconsistently render selection styles in dropdown #21768

Closed
@sync-by-unito

Description

@sync-by-unito

Summary

Our Select component is used in a few places:

Most do not show the current value as selected in the dropdown with the visible checkmark and other styling, with the exception of the "Front-end Framework" dropdown in SelectFwOrBundler. However, it seems like they all should show these selection styles.

The Select currently expects the selected options to be provided with an isSelected property, which is not uniformly provided today. It seems like we could use the inner TabList's selection APIs to keep this synchronized better.

Acceptance Criteria

  • Select implementations within these files should consistently show their selected items as selected in the dropdown
  • Percy snapshots should be added for these scenarios

Screen Shot 2022-03-17 at 5 00 09 PM
Screen Shot 2022-03-17 at 5 17 04 PM
Screen Shot 2022-03-17 at 5 07 38 PM
Screen Shot 2022-03-17 at 5 07 22 PM
Screen Shot 2022-03-17 at 5 00 25 PM

┆Issue is synchronized with this Jira Bug by Unito
┆Attachments: Screen Shot 2022-03-17 at 5.00.09 PM.png | Screen Shot 2022-03-17 at 5.00.25 PM.png | Screen Shot 2022-03-17 at 5.07.22 PM.png | Screen Shot 2022-03-17 at 5.07.38 PM.png | Screen Shot 2022-03-17 at 5.17.04 PM.png
┆author: Tyler Biethman
┆epic: UI/UX Improvements
┆friendlyId: UNIFY-1375
┆priority: Low
┆sprint: Backlog
┆taskType: Bug

Metadata

Metadata

Assignees

No one assigned

    Labels

    Type

    No type

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions