Lightness value in ChromePicker when set to 0% leads to setting of Saturation value to 0%.

1) Add 0% for lightness in HSL component in the ChromePicker.
2) The saturation value always sets to 0% even after changing the values for saturation.


Start by locating the ChromePicker HSL component and reproduce the behavior described in the issue: setting lightness to 0% causes saturation to become 0%. Confirm that changing saturation afterward preserves the entered value, then add or update coverage if the project provides a relevant test entry point.

Written by the indexing model from the issue text.