Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Regression: v3.4.15 hoists the linear-gradient background to the top #781

Closed
ngyikp opened this issue Jun 1, 2016 · 1 comment
Closed

Comments

@ngyikp
Copy link
Contributor

ngyikp commented Jun 1, 2016

Input:

.abc {
    background: #fff;
    background-image: url(a.png), -webkit-linear-gradient(top, #000, #111);
    background-image: url(a.png), -moz-linear-gradient(top, #000, #111);
    background-image: url(a.png), -o-linear-gradient(top, #000, #111);
    background-image: url(a.png), linear-gradient(to bottom, #000, #111);
}

3.4.14 is pretty much the same:

.abc {
    background: #fff;
    background-image: url(a.png), -webkit-linear-gradient(top, #000, #111);
    background-image: url(a.png), -moz-linear-gradient(top, #000, #111);
    background-image: url(a.png), -o-linear-gradient(top, #000, #111);
    background-image: url(a.png), linear-gradient(to bottom, #000, #111)
}

3.4.15 hoists the linear-gradient to the background shorthand, which doesn't work for browsers that don't support it:

.abc {
    background: url(a.png), linear-gradient(to bottom, #000, #111) #fff;
    background-image: url(a.png), -webkit-linear-gradient(top, #000, #111);
    background-image: url(a.png), -moz-linear-gradient(top, #000, #111);
    background-image: url(a.png), -o-linear-gradient(top, #000, #111)
}
jakubpawlowicz added a commit that referenced this issue Jun 2, 2016
Checking every combination of override clashes should not fall
back to same values in case of multiplex components.
@jakubpawlowicz
Copy link
Collaborator

It's released in 3.4.16.

silverwind pushed a commit to silverwind/clean-css that referenced this issue Sep 25, 2016
Checking every combination of override clashes should not fall
back to same values in case of multiplex components.
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants