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

Fix/improve visibility delete icon in chip autocomplete pfr 737 #3266

Conversation

RobD-tech
Copy link
Collaborator

When the chips in the autocomplete have a dark background color, the delete icon is not (clearly) visible.

If the background color is dark, you will apply a light color to the text within the chip and the icon should behave the same. By default, the background color of the chip is set to Light (from the theme builder). The default Material UI color for the delete icon is fine then, but as soon as the background color of the chip is changed the icon color should be the same as the text color. This was a finding when working with the design system from the police. The UI was agreed upon with UX.

@stefan-betty
Copy link
Collaborator

Before we merge this to edge, could you merge acceptance into your branch?

stefan-betty
stefan-betty previously approved these changes Oct 25, 2023
@RobD-tech RobD-tech dismissed stefan-betty’s stale review October 25, 2023 13:10

The merge-base changed after approval.

@RobD-tech RobD-tech dismissed ingmar-stipriaan’s stale review October 31, 2023 13:06

The merge-base changed after approval.

@ingmar-stipriaan ingmar-stipriaan merged commit e4a74dc into edge Oct 31, 2023
2 checks passed
@ingmar-stipriaan ingmar-stipriaan deleted the fix/improve-visibility-delete-icon-in-chip-autocomplete-PFR-737 branch November 1, 2023 07:39
@bettyblocks-release-bot
Copy link
Collaborator

🎉 This PR is included in version 2.165.1 🎉

The release is available on GitHub release

Your semantic-release bot 📦🚀

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

Successfully merging this pull request may close these issues.

8 participants