I encountered this while using the .justify-content mixin, but it applies to the other flexbox mixins with legacy syntax support.
The result for .justify-content is (in practice and in the docs):
// Result
div {
-webkit-box-pack: flex-start;
-moz-box-pack: start;
-webkit-justify-content: start;
-ms-flex-pack: flex-start;
justify-content: flex-start;
}
However, the -webkit-box-pack also takes start as value, not flex-start (same as the -moz- prefix).
The current implementation causes Safari 5.1.7 on Windows (which only has legacy flexbox support) to ignore the -webkit-box-pack property, but with start it works as designed.
I think this applies (but I did not test it) to the other box- flexbox properties, like align-items (box-align).
EDIT: On a second look, I think the values for -webkit-box-pack and -webkit-justify-content are just mixed up.
I encountered this while using the .justify-content mixin, but it applies to the other flexbox mixins with legacy syntax support.
The result for .justify-content is (in practice and in the docs):
However, the
-webkit-box-pack
also takesstart
as value, notflex-start
(same as the-moz-
prefix).The current implementation causes Safari 5.1.7 on Windows (which only has legacy flexbox support) to ignore the
-webkit-box-pack
property, but withstart
it works as designed.I think this applies (but I did not test it) to the other
box-
flexbox properties, likealign-items
(box-align
).EDIT: On a second look, I think the values for
-webkit-box-pack
and-webkit-justify-content
are just mixed up.