Skip to content

Conversation

@ilyabrower
Copy link
Contributor

@ilyabrower ilyabrower commented Oct 22, 2025

Motivation and Context

Fixed UIK-3526, UIK-3527 and UIK-2865

How has this been tested?

Manually

Screenshots (if appropriate):

Types of changes

  • Bug fix (non-breaking change which fixes an issue).
  • New feature (non-breaking change which adds functionality).
  • Breaking change (fix or feature that would cause existing functionality to not work as expected).
  • Nice improve.

Checklist:

  • I have updated the documentation accordingly.
  • I have added changelog note to corresponding CHANGELOG.md file with planned publish date.
  • I have added new tests on added of fixed functionality.

Copy link
Member

@j-mnizhek j-mnizhek left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Overall everything is good. But I have a proposal for the 2 case based on the correct UX behaviour.

FFFFFF hex is actually valid, but why the input shows that it's not because of the validation rules in this particular example. It maybe with a 99% contrintuitive for the user.

So the question is: can we set different validation rules or at least add a tooltip that explains why the value that I've entered is invalid?

image

@Valeria-Zimnitskaya Valeria-Zimnitskaya merged commit 76a0d31 into release/v16 Oct 31, 2025
7 checks passed
@Valeria-Zimnitskaya Valeria-Zimnitskaya deleted the UIK-3527/color-picker-issues branch October 31, 2025 16:00
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.

5 participants