Saturation Pointer doesn't move after hsva is updated elsewhere

[zaytri]

This is specifically using the Saturation component.

I've noticed this bug also happens on the React Color website, on the main page with all the components, so it's an issue with the Saturation component itself rather than my own setup.

This only happens after having used the mouse to move around the color in Saturation.

Once that's been done, then when hsva is updated by any other means, even though the gradient is correct and the color in the Pointer is correct, the Pointer does not move even when it should.

To reproduce:

1. Go to https://uiwjs.github.io/react-color/ and drag around the Pointer in one of the Saturation components using your mouse.
2. Use any other color control to change color, easiest way to notice the bug is by moving around the Pointer in a different Saturation component.
3. The pointer that was moved previously does not move, even though the others that haven't been mouse controlled do move.

[jaywcjlove]

@zaytri Thank you for your feedback! However, I'm not quite sure I understand your issue. Could you please clarify? You mentioned that the pointer doesn't move after hsva is updated when using the mouse to move it, is that correct? Any additional details or specific examples would be really helpful.

[zaytri]

@jaywcjlove I've attached a video showing the issue.
First I changed the color using the color wheel, which moved 3 of the saturation pointers.
Then I moved around the first saturation pointer with my mouse, everything working as expected.
However, when I moved around the second saturation pointer with my mouse, the first saturation pointer does not move.
I try moving the first saturation pointer again, and now the second saturation pointer does not move.
Then I move the third saturation pointer, and both the first and second saturation pointers do not move.
Finally, I change the color using the color wheel again, and none of the saturation pointers move.

chrome_2025-05-05_10-08-20.mp4

[grimmwerks]

Has this been corrected? Just noticed this as well in my app:

ScreenFlow.mp4

[zaytri]

@grimmwerks it looks to be fixed in the latest version! (v2.5.4) Working correctly in my project after updating.