You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
On an iro color picker with a custom layout containing red / green / blue and alpha sliders, on sliding the alpha slider first, then sliding any of the red/green/blue sliders resets the alpha value to 1.
This behaviour only occurs on rgb/kelvin sliders in combination with alpha slider.
Minimal reproduction:
Consider the following pen: RGBA Slider Example
Create a color Picker with the following properties:
Next, slide the alpha slider to a value below 1.
Then slide the red slider to any value.
Output: on sliding the red slider, alpha value gets reset to 1.
rgbaString also shows an alpha value of 1.
In the pen, we see that alpha value is preserved sliding the hue slider, but not while sliding the red slider.
I don't know if this is in fact intended behaviour, but for functionality I would prefer the active Color keep its alpha value in this case!
The text was updated successfully, but these errors were encountered:
Version: 5.5.2
Description:
On an iro color picker with a custom layout containing red / green / blue and alpha sliders, on sliding the alpha slider first, then sliding any of the red/green/blue sliders resets the alpha value to 1.
This behaviour only occurs on rgb/kelvin sliders in combination with alpha slider.
Minimal reproduction:
Consider the following pen: RGBA Slider Example
Create a color Picker with the following properties:
Next, slide the alpha slider to a value below 1.
Then slide the red slider to any value.
Output: on sliding the red slider, alpha value gets reset to 1.
rgbaString also shows an alpha value of 1.
In the pen, we see that alpha value is preserved sliding the hue slider, but not while sliding the red slider.
I don't know if this is in fact intended behaviour, but for functionality I would prefer the active Color keep its alpha value in this case!
The text was updated successfully, but these errors were encountered: