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
According to issue #362 this was reported and fixed in an earlier version of CSSO. However, it looks like this is (partially) broken again.
The main work-around listed on Flexbugs (using 0% as a value, see https://github.com/philipwalton/flexbugs#4-flex-shorthand-declarations-with-unitless-flex-basis-values-are-ignored ) is actually not working with the current version (4.0.2). We should aim to fix this, as the work-around is probably well-known by now and because it is suggested it is the first thing developers will try to prevent the problem. A value of 0px is working as you'd expect (i.e. the unit is not removed). Also, the discussion in the original issue concludes:
Decision: we should remove unit removal for -ms-flex only
Which is not happening, the behaviour is the same for both flex and -ms-flex. In the example below, I actually expect that the output would be the same as the input, or at least for the -ms-flex uses.
According to issue #362 this was reported and fixed in an earlier version of CSSO. However, it looks like this is (partially) broken again.
The main work-around listed on Flexbugs (using 0% as a value, see https://github.com/philipwalton/flexbugs#4-flex-shorthand-declarations-with-unitless-flex-basis-values-are-ignored ) is actually not working with the current version (4.0.2). We should aim to fix this, as the work-around is probably well-known by now and because it is suggested it is the first thing developers will try to prevent the problem. A value of
0px
is working as you'd expect (i.e. the unit is not removed). Also, the discussion in the original issue concludes:Which is not happening, the behaviour is the same for both
flex
and-ms-flex
. In the example below, I actually expect that the output would be the same as the input, or at least for the -ms-flex uses.Given the following input:
I get the following output:
Originally posted by @Didel in #362 (comment)
The text was updated successfully, but these errors were encountered: