I gather that it reorders the CSS statements somehow, but I'm not clear about exactly how it reorders them or why this is important.
I gather that it reorders the CSS statements somehow, but I'm not clear about exactly how it reorders them or why this is important.
I'm starting to think of something that might be good advice in general - 10 lines of actual working example code is worth 1000 lines of abstract documentation. (I've also been working with Twisted recently, getting frustrated with documentation that's full of recursive jargon...)
$default_sort_order = '[
"position",
"top",
"right",
"bottom",
"left",
"z-index",
"display",
"visibility",
"-webkit-flex-direction",
"-moz-flex-direction",
"-ms-flex-direction",
"-o-flex-direction" [...]
defined in https://github.com/csscomb/csscomb-for-vim/blob/master/plugi..., so I guess that's what CSSComb uses, although it says one can define custom orderings.
I guess it's useful if you write lots of CSS and don't want to bother with thinking about the ordering at code-time?
This is probably most effective if you tend to specify the same values for the properties as well, so that a run can extend from one property name through its value and to the next property name.
Clustering properties with identical prefixes will provide some improvement by itself, as it can keep the 'backward distance' values used in a small consistent range, but I expect that's going to be a much smaller effect.