That’s not a bug @weedor. Wouldn’t even consider that as an inconsistency.
As you can see, the slider range goes from 0 to 3 (in decimal increments), so it suggests to the user that a unitless value is applied.
For example, 2 is equal to 200%. You can find more info here.
Thank you @Marius
I changed according to your reply.
The issue goes on.
Here is the code created by Cwicly:
brightness(.92)contrast(87%)hue-rotate(122deg)invert(97%)saturate(577%)sepia(6%)
→ doesn’t work
I changed the order of parameters
I moved “invert” and “sepia” to the beginning of the line.
Here is the new order:
invert(97%)sepia(6%)brightness(.92)contrast(87%)hue-rotate(122deg)saturate(577%)
→ does work fine
Do you know if exist a solution to reorder parameters?
Normally, the color to reach must be #C4DFDB
With the filter Cwicly code, the color is #EDEBE7
With the filter code reordered, the color is #C4DFDB
You can check it at https://bros.ai/ at the very bottom (on the right).
There is a “big” image “bros.ai”
On hover, the color is #EDEBE7
If you reorder the filter according to my previous post, on hover, the color becomes #C4DFDB
While I understand that you’re trying to apply the filters in a different order to achieve a specific result, this behaviour cannot be considered a bug as the filters are applying correctly, albeit not in the order you specifically require.
@Araminta
You are right, this can’t be considered as ²a bug. This is why I created a Feature Request.
As usually, @Marius is helpful precious.
Thank you both.