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
For these reasons, this package is (unfortunately) still useful in Dart SASS. No matter the deprecation phase, for now there’s no decent plan for hsl and hsla.
Currently, hsl.scss perfectly works both @import and @use, but its documentation should be improved to reflect the current state of hsl/hsla in SASS.
My initial plan for this package was to not upgrade it to Dart SASS. But unfortunately,
hsl
andhsla
remain global (despite the existence of a namespacedcolor
module withcolor.hue()
,color.saturate()
andcolor.lightness()
) and their behavior is still chaotic.Current algorithm and examples
Basically, the current result of using
hsl
andhsla
seems to follow this decision tree:hsl
/hsla
, it’s left untouched by SASS;deg
to the hue;turn
orrad
, it replaces it bydeg
without converting;%
in saturation and lightness;hsl
with alpha channel, replaceshsl
byhsla
;hsla
without alpha channel, replaceshsla
byhsl
.This matches phase 1 of 3 (or 2 of 3 for the hue) in the deprecation plan for color units, leading to these outputs:
For these reasons, this package is (unfortunately) still useful in Dart SASS. No matter the deprecation phase, for now there’s no decent plan for
hsl
andhsla
.Currently,
hsl.scss
perfectly works both@import
and@use
, but its documentation should be improved to reflect the current state ofhsl
/hsla
in SASS.Related tasks:
@debug
mode #4The text was updated successfully, but these errors were encountered: