WIP: Hsla color not supported in new color manager

Browser: Chrome 110
OS: macOS / Windows / Linux / etc.
URL: Link to a page that illustrates this issue
Video: video

hsla color not supported in new color manager and it is the most powerful color unit.

1- color palette preview doesnt render hsla properly
2- when trying to use hsla from color palette it just doesnt work at all

1 Like

Hi @sinanisler,

lately, there is no need to use hsla, because hsl supports alpha as well :slight_smile:

The reason why it’s not working in your case, it’s because the syntax is wrong. Here is a screenshot from your video. Do you notice what is wrong? :wink:
CleanShot 2025-12-20 at 22.12.28@2x

There are two ways to support alpha channel.

  1. The default, “older” way, with commas: hsl(H, S, L[, A]), which would be something like this: hsl(120, 64% ,43%, .2)
  2. The “new” syntax that I suppose you wanted to use - without commas: hsl(H S L[ / A]), which would be something like this: hsl(120 64% 43% / .2)

Please note that both examples above work with hsla(...) as well.

Because of this, I’m marking this as a no-bug :slight_smile:

Thank you,
Matej

1 Like

Note: The hsla() functional notation is an alias for hsl(). They are exactly equivalent. It is recommended to use hsl().

I am so used to using hsla, ok I learned something :slight_smile:

but the color palette issue I think still valid
html form color input is defaulting down to hsla not the hsl when I try to add alpha to any color coming from variables.

and when I click to any variable and try to add alpha it just selects the wrong hsl value color picker doesnt read correct value from the variable for some reason I dont know if it is just unit mismatch or just not reading it

if we can make the color system working with that drop icon/color picker the workflow will be more seamless

Hmm, can you record that? I’m not sure if I understand. How should I replicate it?

Matej

easy

color picker default value should be coming from the selected variable but it is not happening

Hi @sinanisler,

yeah, that makes sense. I’ve added it to our local bug tracker.

Thank you for reporting.
Matej