Steps To Reproduce

1. Open HSV color picker
2. Reset HEX to #000000
3. Update H value to 200
4. Update S value to 20
5. Update V value to 20

Expected behavior

This should result in the HEX value updating at each change to reflect the values found in the H, S, and V fields, which according to DuckDuckGo's built in color converter would result in #282f33.

Actual behavior

Once the V value is updated to 20, both the H and S values reset to 0.

Screenshots or video

Penpot
https://github.com/penpot/penpot/assets/16119136/ba3dcb11-b77b-4f86-8235-6b25e96d261b

Affinity Designer
https://github.com/penpot/penpot/assets/16119136/1308af0f-7543-4c40-9910-4d11c62fed03

Desktop (please complete the following information)

macOS 12.6.3
Safari 16.3

Smartphone (please complete the following information)

No response

Environment (please complete the following information)

Local instance
Debian 11
Docker version 24.0.2, build cb74dfc

Frontend Stack Trace

No response

Backend Stack Trace

No response

Additional context

It would be great if when editing in HSV, those values are untouched by the application, and instead the HEX value was a reflection of the HSV values. It, instead, appears that whenever a HSV value is changed, the HEX is recalculated, and then the HSV values are recalculated based on the newly recalculated HEX value.

It would be really nice if when HSV is used to pick a color, the actual values for H,S, and V are saved for the object, and then the HEX value is calculated dynamically. This would allow me, the user, to pick up where I left off on a design, and see the HSV values I entered previously, instead of the calculated HSV values based on the calculated HEX value.