Incorrect ordering / Inconsistent css rule merging

[altmind]

Using standalone cleancss-cli 2.1.7.

Processing

.nav-item-link {
    height: 7rem; /* DECLARED FIRST */
}

.nav-item-link-product {
    height: auto; /* DECLARED SECOND */
}

.nav-item-link {
    line-height: 7rem; /* BREAKS ORDERING*/
    color: red;
}

results in

.nav-item-link-product{height:auto}
.nav-item-link{height:7rem;line-height:7rem;color:red}

which is semantically wrong - now .nav-item-link will overwrite height for html element with class="nav-item-link-product nav-item-link". Clear problem with css rule priorities.

I'm puzzled, as when we remove "line-height: 7rem;" from 3rd rule, we get correct result css. See:

.nav-item-link {
    height: 7rem; /* DECLARED FIRST */
}

.nav-item-link-product {
    height: auto; /* DECLARED SECOND */
}

.nav-item-link {
    color: red;
}

generates

.nav-item-link{height:7rem}
.nav-item-link-product{height:auto}
.nav-item-link{color:red}

So it seems that 'color' does not cause .nav-item-link rules merge, whereas 'line-height' property does cause rules merge.

When using option "noAdvanced" clean-css generates correct result.

This problem was observed on production and is real, practical, issue

[GoalSmashers]

Seems like an edge case in our selectors merging. Thanks for detailed report, fix is coming!

[GoalSmashers]

The fix is not as straightforward as I thought, so, if possible, use noAdvanced until we fix it later today.

[GoalSmashers]

@altmind 2.1.8 is out with the fix!

[altmind]

👍