Open nsaunders opened 2 years ago
Considering current widespread support, are the prefixes still needed anyway?
Yes, I think it would be ok to remove them.
It's still interesting to understand how this error comes across: The trouble is in the Semigroup
instance of Value
, which boils down to:
When you do <>
on values, and one of them has prefixes like the browsers, the prefixes will move to the outside. Spoiler alert: padding
is defined using <>
. Not sure what would be the cleanest solution, if not removing the browser prefixes for calc
.
It looks like browser prefixes aren't properly applied to complex values that include
calc
expressions.Considering current widespread support, are the prefixes still needed anyway?
Given:
Expected:
Actual: